AZ-400 Practice Question: Design and implement build and release pipelines
Your release pipeline deploys to multiple Azure regions. You need to ensure that if a deployment to one region fails, the pipeline continues deploying to other regions. Which deployment strategy should you use?
Answer choices
Why each option matters
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Rolling deployment
Rolling deployment updates instances gradually across regions. If a deployment to one region fails, the pipeline can continue deploying to other regions because each region is updated independently. Option A (immutable deployment) replaces all instances at once, so a failure would halt the entire deployment. Option C (blue-green) switches all traffic to a new environment; if that environment fails, the whole deployment fails. Option D (canary) routes a small percentage of traffic to a new version and rolls back if issues occur, but it does not ensure continued deployment to other regions upon failure.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Immutable deployment
Why it's wrong here
Immutable deployment creates a completely new set of instances for the new release and then swaps all traffic to them, meaning any failure in that new fleet halts the entire deployment with no old instances left to serve traffic; this makes it unsuitable for continuing across multiple Azure regions when one region fails.
- ✓
Rolling deployment
Why this is correct
Rolling deployment replaces instances incrementally across regions, keeping the previous version running in unaffected instances; if a region's batch fails health checks, Azure DevOps can stop that batch while other regions continue receiving updates, thereby tolerating regional failures and meeting the requirement to keep deploying.
- ✗
Blue-green deployment
Why it's wrong here
Blue-green deployment shifts all traffic at once from the blue (current) environment to the green (new) environment, so any defect becomes immediately visible to all users across every region; even though you can switch back, the failure interrupts the whole deployment and affects all regions simultaneously.
- ✗
Canary deployment
Why it's wrong here
Canary deployment releases the new version to a small subset of users or regions to validate it, and if the canary fails you roll back rather than continuing, so it cannot satisfy the requirement to keep deploying to other Azure regions after a regional failure; it is a validation strategy, not a full multi-region rollout strategy.
Go deeper
Related to this question
Learn chapter
Introduction to DevOps and Azure DevOps
Key term
Release pipeline
A Release pipeline is an automated sequence of steps that takes software from code commit to production deployment, ensuring quality and consistency.
Key term
Environment
An environment is a dedicated set of computing resources, configurations, and services used to develop, test, or host software applications in a controlled and repeatable way.
About these practice questions
This AZ-400 question is part of Courseiva's 823-question bank — original exam-style content with full explanations and wrong-answer analysis, never real exam questions or exam dumps. Learn why practice questions differ from exam dumps →
JA
Written by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
This AZ-400 practice question is part of Courseiva's free Microsoft certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the AZ-400 exam.