A county wants policy-as-code checks in CI before Terraform apply to the elections support account. What control gate is that?
Select an answer to reveal the explanation.
Short Explanation
CI policy-as-code is the county's metal detector before Terraform walks into the elections account. Skipping checks for speed is how bad configs get sworn in. Gate the apply.
Full Explanation
Gating civic IaC applies with automated security policy-as-code checks in CI before Terraform reaches elections support accounts is the control gate a county should use. Policy-as-code evaluates proposed infrastructure changes for insecure configurations before they can affect elections-adjacent systems, failing the build when rules are violated. That gate keeps speed in the pipeline while preventing automated cost policy-as-code checks in CI from standing in for the automated security policy checks required before resources are provisioned to elections support accounts. Gating civic IaC applies with automated cost policy-as-code checks in CI before Terraform reaches elections support accounts fails by concept: cost policy checks evaluate projected spend rather than insecure configurations, and they do not fail the build when unsafe resources would reach elections-adjacent systems. Gating civic IaC applies with manual supervisory policy-as-code approvals in CI before Terraform reaches elections support accounts turns the gate into a manual approval step instead of automated policy enforcement, so insecure configurations can still ship whenever a supervisor approves without an automated policy violation failing the build. Gating civic IaC applies with automated security policy-as-code checks in CI after Terraform reaches elections support accounts fails by timing: post-apply checks run after resources are already deployed, and they do not act as a pre-apply control gate that blocks insecure infrastructure from reaching the elections account.
Exam caveat: policy packs must be kept current with elections account controls; outdated policies create either false confidence or noisy failures teams learn to ignore. Operational check: submit a deliberately noncompliant Terraform change in a non-prod elections-like pipeline and confirm CI blocks apply, then verify a compliant change proceeds only after policy-as-code and review pass.
Prefer to study offline? Printable PDF study book + test engine ($7.50, unofficial). These questions stay free here.