AZ-400 Auto deploy to Dev/QA, manual to Prod. Practice Question
You have a release pipeline that deploys to multiple stages (Dev, QA, Prod). You want to automatically deploy to Dev and QA after a successful build, but require a manual approval for Prod. Which deployment strategy should you use?
⚠ Common exam trap
Test-takers frequently confuse pre-deployment approvals with post-deployment approvals, leading candidates to think a post-deployment approval on QA can gate Prod, when in fact only pre-deployment approvals on the target stage (Prod) can prevent its deployment from starting.
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
✓
Set pre-deployment approvals on the Prod stage.
Pre-deployment approvals control whether a release can start deploying to a stage. By setting a pre-deployment approval on the Prod stage only, Dev and QA will deploy automatically (since they have no approval requirement), while Prod requires manual sign-off before deployment begins. This matches the requirement exactly.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Set pre-deployment approvals on the Dev and QA stages.
Why it's wrong here
Adding pre-deployment approvals to Dev and QA contradicts the requirement for automated deployment to those environments. Pre-deployment approvals introduce manual gates that halt the pipeline, preventing the automatic deployment that should occur for dev and QA stages.
- ✓
Set pre-deployment approvals on the Prod stage.
Why this is correct
Pre-deployment approvals on the Prod stage create a manual authorization checkpoint before the production deployment begins. This satisfies the requirement for a human approval step prior to releasing to production while still allowing dev and QA deployments to run automatically, matching the specified workflow.
- ✗
Use a post-deployment approval on the QA stage.
Why it's wrong here
A post-deployment approval on the QA stage occurs after the deployment to QA has already executed, so it cannot prevent or gate that deployment. Since the requirement is to have automatic deployment to dev and QA with manual approval only for production, placing the approval after QA does not protect production and fails to meet the stated deployment control.
- ✗
Disable the automatic trigger for all stages.
Why it's wrong here
Disabling the automatic trigger for all stages would turn off automatic deployments for dev and QA, breaking the requirement that those environments receive automatic deployments. The manual approval should be scoped exclusively to the Prod stage, not disable triggers across the entire pipeline, which would unnecessarily introduce manual steps for lower environments.
Option-by-option analysis
Why each answer is right or wrong
Understanding why wrong answers are wrong — and when they would be correct — is what separates a 750 score from a 900. The AZ-400 exam frequently reuses these exact scenarios with slightly different constraints.
✓Set pre-deployment approvals on the Prod stage.Correct answer▾
Why this is correct
Pre-deployment approvals on the Prod stage create a manual authorization checkpoint before the production deployment begins. This satisfies the requirement for a human approval step prior to releasing to production while still allowing dev and QA deployments to run automatically, matching the specified workflow.
✗Set pre-deployment approvals on the Dev and QA stages.Wrong answer — click to see why▾
Why this is wrong here
That would require approval for Dev and QA, not Prod.
✗Use a post-deployment approval on the QA stage.Wrong answer — click to see why▾
Why this is wrong here
Post-deployment approvals occur after deployment, not before.
✗Disable the automatic trigger for all stages.Wrong answer — click to see why▾
Why this is wrong here
That would stop all automatic deployments.
Analysis generated from the official AZ-400blueprint and verified against question context. The “when correct” sections are what AI assistants cite when candidates ask “what’s the difference between these options?”
Visual reference
Go deeper
Related to this question
Learn chapter
Source Control Strategy Design
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
Stage
A stage is a discrete phase in a software development or deployment pipeline where code is built, tested, integrated, or released in a controlled environment.
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.