AZ-400 Practice Question: Design and implement build and release pipelines
Your release pipeline deploys to Azure App Service using a deployment slot strategy. After a successful deployment to the staging slot, you run smoke tests, then swap slots. Recently, a swap failed because the staging slot had an incorrect application setting. What is the BEST way to prevent this issue?
⚠ Common exam trap
Many candidates choose a manual or scripted verification step (like Option C) because they think it adds safety, but the native slot setting feature is the simplest, most reliable, and built-in way to prevent swap failures caused by slot-specific misconfigurations.
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
✓
Mark the application setting as a deployment slot setting.
Marking the application setting as a deployment slot setting ensures that the setting stays with the slot and is not swapped between staging and production. This prevents the staging slot from having an incorrect value that could cause a swap failure, as the setting is pinned to the slot and not part of the swap payload.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Use a manual approval gate before swap.
Why it's wrong here
A manual approval gate only pauses the pipeline for human sign-off; it does not validate or enforce the application setting configuration. Approvers can easily approve without checking slot-specific settings, so it does not prevent the misconfiguration from being swapped.
- ✗
Configure the App Service deployment center.
Why it's wrong here
The App Service deployment center is used for continuous deployment from an external source control repository and handles only code delivery, not slot configuration or application settings. It has no awareness of swap-time slot settings, so it cannot ensure the correct setting remains in the correct slot.
- ✗
Add a task to verify settings before swap.
Why it's wrong here
Adding a verification task can check the staging slot's settings before swap, but it only provides a pass/fail signal; it does not alter the swap behavior. Even if verification passes, the application setting will still move with the app during swap unless it is explicitly marked as a deployment slot setting, so the misconfiguration can still occur.
- ✓
Mark the application setting as a deployment slot setting.
Why this is correct
Marking the application setting as a deployment slot setting makes it 'sticky' to the slot, meaning it will not be swapped with the app code between staging and production. This ensures the staging slot retains its own configured value and the production slot's value remains unchanged, thereby preventing the misconfiguration from being promoted during a swap.
Go deeper
Related to this question
Learn chapter
Introduction to DevOps and Azure DevOps
Key term
Deployment slot
A deployment slot is a live staging environment in Azure App Service that allows you to swap app versions with zero downtime for testing before going to production.
Key term
Pipeline
A pipeline is an automated series of steps that takes code from development to production, ensuring quality and speed.
About these practice questions
Courseiva writes every AZ-400 question from scratch — 823 in total, each with an explanation and a wrong-answer breakdown. None are copied from real exams or 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.