AZ-400 Practice Question: Design and implement build and release pipelines
Which TWO of the following are benefits of using deployment slots in Azure App Service? (Select TWO.)
⚠ Common exam trap
Many exam-takers confuse the ability to swap slots with automatic rollback (A) or assume slots provide independent scaling (B), when in fact slots share the same plan and rollback requires manual intervention.
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
✓
Zero-downtime deployments.
Deployment slots enable zero-downtime deployments (C) by allowing you to swap a staging slot with the production slot. The swap operation warms up the target slot's application before routing traffic, ensuring no requests are dropped. This is a core feature of Azure App Service for safe, continuous delivery.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Automatic rollback on failure.
Why it's wrong here
Deployment slots do not provide automatic rollback on failure; if a deployment to a slot fails health checks, you must manually re-swap the previous slot back into production or redeploy the last known good build, since the slot swap mechanism does not include a built-in failure-triggered rollback.
- ✗
Independent scaling of each slot.
Why it's wrong here
All deployment slots in an App Service share the same underlying App Service plan, so they scale together as a single unit; you cannot independently scale resources like instance count or VM size for an individual slot without affecting the entire plan.
- ✓
Zero-downtime deployments.
Why this is correct
By deploying to a staging slot and then performing a swap, you can instantly redirect production traffic to the new version with no downtime, as the swap operation is atomic and warm-up can be handled before the slot receives production traffic.
- ✓
Validate changes in a staging environment before production.
Why this is correct
Deployment slots provide a staging environment that is identical to production, allowing you to validate changes, run integration tests, and verify configuration before swapping the slot into production, thereby reducing risk of deploying unreviewed changes to live traffic.
- ✗
Geographic redundancy.
Why it's wrong here
Deployment slots are all hosted within the same region as the production App Service, so they do not provide geographic redundancy; for multi-region failover you would need to deploy separate App Service instances in different regions.
Go deeper
Related to this question
Learn chapter
Introduction to DevOps and Azure DevOps
Key term
Continuous delivery
Continuous delivery is a software engineering practice where code changes are automatically built, tested, and prepared for a release to production, with every change being deployable at the push of a button.
Key term
Feature
A feature is a distinct unit of functionality that delivers value to the user, often managed and tracked throughout the software development lifecycle.
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.