AZ-400 Manual approval before prod Practice Question
You have a release pipeline that deploys to multiple stages. You want to ensure that a manual approval is required before deploying to the production stage. Which approach should you use?
⚠ Common exam trap
A common mix-up: candidates confuse post-deployment approvals (which occur after a stage completes) with pre-deployment approvals (which occur before a stage starts), or they mistakenly think a manual intervention task inside a deployment gate can replace the native stage-level approval feature.
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
✓
Add a pre-deployment approval on the production stage.
Pre-deployment approvals in Azure Pipelines allow you to require manual sign-off before a release proceeds to a specific stage. By adding a pre-deployment approval on the production stage, the pipeline will pause and wait for designated approvers to approve the deployment, ensuring that no code reaches production without explicit authorization.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✓
Add a pre-deployment approval on the production stage.
Why this is correct
A pre-deployment approval on the production stage is the correct approach because it prevents the pipeline from starting the production deployment until a designated user or group explicitly approves the release, providing a manual control point before any changes reach the live environment.
- ✗
Add a post-deployment approval on the staging stage.
Why it's wrong here
A post-deployment approval on the staging stage is incorrect because it occurs after the staging deployment has already completed, meaning it cannot block or veto the subsequent production deployment; it only validates what has already happened, not what is about to happen in production.
- ✗
Configure a deployment gate with a manual intervention task.
Why it's wrong here
Configuring a deployment gate with a manual intervention task is not a substitute for stage-level approvals because gates are designed to continuously evaluate automatic health or quality signals, while the manual intervention task runs inside an agent job and does not provide the same pre-deployment sign-off control that gates approval on a stage.
- ✗
Use a pipeline decorator to inject approval step.
Why it's wrong here
Using a pipeline decorator to inject an approval step is incorrect because decorators are meant to automatically add tasks or steps into every pipeline run; they cannot enforce interactive, user-driven manual approvals, as approvals are a native pipeline feature tied to stages and environments, not a step that can be injected via a decorator.
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.
✓Add a pre-deployment approval on the production stage.Correct answer▾
Why this is correct
A pre-deployment approval on the production stage is the correct approach because it prevents the pipeline from starting the production deployment until a designated user or group explicitly approves the release, providing a manual control point before any changes reach the live environment.
✗Add a post-deployment approval on the staging stage.Wrong answer — click to see why▾
Why this is wrong here
Post-deployment happens after deployment, not before.
✗Configure a deployment gate with a manual intervention task.Wrong answer — click to see why▾
Why this is wrong here
Gates evaluate conditions, but manual approval is simpler and more direct.
✗Use a pipeline decorator to inject approval step.Wrong answer — click to see why▾
Why this is wrong here
Decorators are for injecting steps, not for approvals.
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
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
Pipeline
A pipeline is an automated series of steps that takes code from development to production, ensuring quality and speed.
About these practice questions
One of 823 original AZ-400 practice questions on Courseiva, each with a full explanation and wrong-answer analysis — not exam dumps or protected exam content. 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.