roadmap
- 01
- 02
- 03
- 04
- 05
- 06
- 07
- 08
Prepare for policy-as-code interview questions on turning security and compliance rules into checks. Covers Rego, OPA Gatekeeper, Kyverno, Kubernetes admission control, and IaC and pipeline gates.
363 of 363 questions in your plan: 0 known, 0 in progress, 0 due, 0 skipped, 363 new. 0 cut, outside your plan.
Questions on policy as code usually arrive partway through a platform, delivery or security discussion rather than in a slot of their own, and the discussion they arrive in decides what is asked. Platform and SRE loops stay in the cluster: what happens to deployments when the admission webhook times out and is set to fail closed, how a new rule reaches enforcement without breaking the workloads that already violate it, and why a team would pick Kyverno's YAML policies over Rego on Gatekeeper. Where the cluster runs Kyverno, Rego questions are rare, but what the webhook does when it is down is still asked. DevSecOps loops move the check earlier, into the pipeline: why a gate should evaluate the Terraform plan rather than the source files, who may override a failed gate, and what shows afterwards that the check ran. Security and compliance interviews start from the other end, a control in a standard, and ask how it becomes a check against live systems and how an exception gets an owner and an expiry date instead of lasting forever. Each of those loops asks far more than this tree. For the cluster and delivery questions around it, prepare with the [DevOps and SRE plan](/roadmaps/devops); for the pipeline it guards, the [DevSecOps Engineer roadmap](/roadmaps/devsecops); for the wider security ground a compliance conversation opens onto, the [Cyber Security Expert roadmap](/roadmaps/cyber-security).
Treat the questions as the work and the [hub's primer](/topics/sec-policy-as-code) as the reference you check answers against, especially an answer that leans on a term you could not define. A junior answer is judged on the [decision model and where it is enforced](/topics/sec-policy-as-code-fundamentals): an engine only answers a question about the input it is handed, and something else, an editor plugin, a pipeline step, an admission webhook or an audit that only reports, decides what that answer does. From middle level up, the follow-ups turn on [how a Rego rule resolves](/topics/sec-policy-as-code-rego-evaluation). Undefined is not false, so a deny rule that reads a misspelled field never fires and lets everything through; the answer interviewers want next is a unit test run with `opa test` that would have caught it. Seniority shows in [a rule's life after it merges](/topics/sec-policy-as-code-lifecycle-operations): shipping it in audit mode, reading what it would have blocked, then enforcing it, with exceptions kept owned and dated. Many senior conversations end on a gate that blocks a production fix at night, and on who may bypass it and what record the bypass leaves.
Questions on policy as code usually arrive partway through a platform, delivery or security discussion rather than in a slot of their own, and the discussion they arrive in decides what is asked. Platform and SRE loops stay in the cluster: what happens to deployments when the admission webhook times out and is set to fail closed, how a new rule reaches enforcement without breaking the workloads that already violate it, and why a team would pick Kyverno's YAML policies over Rego on Gatekeeper. Where the cluster runs Kyverno, Rego questions are rare, but what the webhook does when it is down is still asked.
DevSecOps loops move the check earlier, into the pipeline: why a gate should evaluate the Terraform plan rather than the source files, who may override a failed gate, and what shows afterwards that the check ran. Security and compliance interviews start from the other end, a control in a standard, and ask how it becomes a check against live systems and how an exception gets an owner and an expiry date instead of lasting forever.
Each of those loops asks far more than this tree. For the cluster and delivery questions around it, prepare with the DevOps and SRE plan; for the pipeline it guards, the DevSecOps Engineer roadmap; for the wider security ground a compliance conversation opens onto, the Cyber Security Expert roadmap.
Treat the questions as the work and the hub's primer as the reference you check answers against, especially an answer that leans on a term you could not define.
A junior answer is judged on the decision model and where it is enforced: an engine only answers a question about the input it is handed, and something else, an editor plugin, a pipeline step, an admission webhook or an audit that only reports, decides what that answer does.
From middle level up, the follow-ups turn on how a Rego rule resolves. Undefined is not false, so a deny rule that reads a misspelled field never fires and lets everything through; the answer interviewers want next is a unit test run with opa test that would have caught it.
Seniority shows in a rule's life after it merges: shipping it in audit mode, reading what it would have blocked, then enforcing it, with exceptions kept owned and dated. Many senior conversations end on a gate that blocks a production fix at night, and on who may bypass it and what record the bypass leaves.