Question 16 — AZ-104 Practice Exam 16
You’re leading a platform team that must prevent noncompliant resources before deployment, verify compliance after deployment, and reduce slow, manual approval gates—without hurting developer velocity. Your organization uses Azure DevOps for CI/CD. Which actions best meet these objectives? (Select two answers)
Integrate Azure Policy checks into Azure DevOps pipelines as pre-deployment and post-deployment stages.
Rely on manual, post-deployment audits to detect noncompliance during quarterly reviews.
Embed guardrails by assigning Azure Policy so platform rules are enforced by the Azure control plane instead of external approval boards.
Assign an initiative that blocks all deployments until a change advisory board (CAB) approves each release.
Scope all policies only at the resource group level to avoid pipeline changes.
Correct answers
Integrate Azure Policy checks into Azure DevOps pipelines as pre-deployment and post-deployment stages.
Embed guardrails by assigning Azure Policy so platform rules are enforced by the Azure control plane instead of external approval boards.
Explanations
Correct:
Integrate Azure Policy checks into Azure DevOps pipelines as pre-deployment and post-deployment stages. This provides automated gating before release and verification after release, aligning with the lesson’s emphasis on policy-driven governance and CI/CD integration.
Embed guardrails by assigning Azure Policy so platform rules are enforced by the Azure control plane instead of external approval boards. Embedding governance in the platform reduces reliance on external manual approvals and speeds delivery while maintaining control.
Wrong:
Rely on manual, post-deployment audits to detect noncompliance during quarterly reviews. Manual audits are slow, reactive, and don’t prevent noncompliant deployments.
Assign an initiative that blocks all deployments until a change advisory board (CAB) approves each release. This increases external approvals and harms velocity, contrary to the goal of balancing control with speed.
Scope all policies only at the resource group level to avoid pipeline changes. Arbitrary scoping doesn’t ensure prevention or verification across the estate and may miss organization-wide guardrails.