Microsoft Certified: DevOps Engineer ExpertDesign and implement pipelinesMedium
A DevOps team is setting up a release pipeline for an application deployed to multiple Azure App Service instances across different regions. They need to ensure that the deployment to each region occurs sequentially, with a delay between regions to allow for monitoring and validation. Additionally, after each regional deployment, a manual approval from the regional operations lead is required before proceeding to the next region. Which combination of Azure Pipelines features should be used to implement this controlled rollout?
- AMulti-stage YAML pipeline with stage dependencies, delays, and pre-deployment approvals.
- BClassic release pipeline with parallel environments and post-deployment gates.
- CDeployment groups with pre-deployment approvals.
- DScheduled releases with deployment conditions and task groups.
Show answer & explanationAnswer & explanation
Correct answer: A. Multi-stage YAML pipeline with stage dependencies, delays, and pre-deployment approvals.
A multi-stage YAML pipeline allows defining separate stages for each regional deployment. Stage dependencies (`dependsOn`) enforce sequential execution. Delays can be configured between stages, and pre-deployment approvals can be added to each stage to require manual sign-off from regional operations leads before initiating deployment to that specific region.
Why the other options are wrong
- B. Classic release pipelines are being phased out. Parallel environments contradict the sequential requirement. Post-deployment gates are for automated checks, not manual approvals before a stage.
- C. Deployment groups are for VM deployments, not App Services. Pre-deployment approvals are correct, but this doesn't cover sequential regional deployment with delays.
- D. Scheduled releases control initial trigger, not sequential regional rollout. Deployment conditions are generic, and task groups organize tasks but don't orchestrate complex stage-level delays and approvals across regions.
Controlled Multi-Region Deployment
Multi-stage YAML pipelines with stage dependencies, delays, and pre-deployment approvals enable controlled, sequential rollouts to multiple regions with human intervention and monitoring time.
- Stages represent distinct regional deployments.
- Dependencies enforce sequential execution.
- Delays allow for monitoring time between regions.
- Pre-deployment approvals enable manual sign-off for each region.
Memory trick: Stages Stack, Delays Dwell, Approvals Allow.