Microsoft Certified: DevOps Engineer ExpertDesign and implement pipelinesHard
A DevOps team is developing a new application that will be deployed across multiple Azure regions for high availability and disaster recovery. They need a deployment strategy that allows them to roll out updates to one region at a time, validate the deployment in that region, and only then proceed to the next region. If an issue is detected, the rollout should halt, and the problematic region should be rolled back without affecting other regions. Which deployment strategy best fits this scenario?
- ARolling update
- BCanary deployment
- CBlue/Green deployment
- DPhased rollout (Multi-Region)
Show answer & explanationAnswer & explanation
Correct answer: D. Phased rollout (Multi-Region)
A phased rollout (multi-region) explicitly involves deploying to one region, validating, and then progressively deploying to subsequent regions. This allows for containing issues to a single region and performing targeted rollbacks, which matches the scenario's requirements.
Why the other options are wrong
- A. Rolling update updates instances within a single deployment or service incrementally, not across distinct geographical regions with inter-region validation steps.
- B. Canary deployment rolls out to a small subset of users or servers, typically within a single environment or region, before a full rollout. It's not specifically for sequential multi-region deployment with inter-region validation.
- C. Blue/Green deployment focuses on swapping traffic between two identical environments (blue and green) within a single region or deployment unit, not inherently designed for sequential multi-region rollouts with validation steps between regions.
Phased Rollout (Multi-Region)
A deployment strategy where application updates are released to one geographical region at a time, validated, and then progressively rolled out to subsequent regions, allowing for isolation and quick rollback of issues.
- Deploys to one region, validates, then moves to the next.
- Minimizes blast radius of issues to a single region.
- Enables region-specific testing and monitoring.
- Supports targeted rollback without affecting other regions.
Memory trick: Phased rollout is like crossing a bridge one section at a time, checking each part before moving on.