Microsoft Certified: DevOps Engineer ExpertDesign and implement pipelinesHard
A large enterprise is implementing a phased rollout strategy for its critical business application. The application is deployed across multiple geographic regions. Before any deployment to a new region, a set of automated health checks and performance tests must pass. Additionally, after deployment, a manual approval from the regional operations manager is required before traffic is fully shifted to the new version in that region. Which Azure DevOps feature combination should be used to enforce this strategy?
- APre-deployment gates and Post-deployment approvals.
- BManual intervention tasks and Conditional tasks.
- CDeployment Groups and Release Gates.
- DPre-deployment approvals and Post-deployment gates.
Show answer & explanationAnswer & explanation
Correct answer: A. Pre-deployment gates and Post-deployment approvals.
Pre-deployment gates are ideal for automated health checks and performance tests that must pass *before* a deployment to a new region begins. Post-deployment approvals are then used to enforce the manual sign-off from the regional operations manager *after* the deployment (and its automated checks) has completed in that region, but before it's considered fully 'released' or traffic is shifted.
Why the other options are wrong
- B. Manual intervention tasks pause the pipeline during a stage, not for pre-stage automated checks or post-stage formal approvals. Conditional tasks control task execution, not stage-level gating or approval flow.
- C. Deployment Groups are for grouping deployment targets. Release Gates is a broader term, but the specific mechanisms (Pre/Post gates/approvals) are needed here, not just the general concept.
- D. Pre-deployment approvals are for manual sign-off before deployment, not automated checks. Post-deployment gates are for automated checks after deployment, but the requirement specifically asks for a *manual* approval after deployment.
Pre-deployment Gates & Post-deployment Approvals
Pre-deployment gates are automated checks run before a stage starts. Post-deployment approvals are manual sign-offs required after a stage completes, often before traffic shift or proceeding to the next stage.
- Gates automate quality checks; approvals enforce human oversight.
- Pre-gates ensure environment readiness and code quality.
- Post-approvals validate the deployed outcome before finalization.
Memory trick: Automated check BEFORE, human OK AFTER.