AZ-400 Practice Question: Design and implement build and release pipelines
You are designing a release pipeline that must deploy to multiple environments in sequence: Dev, Test, and Prod. Each environment requires manual approval before deployment. You want to minimize the number of approvals while ensuring that Prod is never deployed without approval. What should you do?
⚠ Common exam trap
The trap here is thinking that approvals must be applied to every environment to be safe, which unnecessarily increases manual steps.
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 only to the Prod environment.
Configuring a pre-deployment approval only on the Prod environment ensures that Prod deployments are gated by manual approval, while Dev and Test deploy automatically. This reduces the total number of approvals to one per release, meeting the requirement to minimize approvals and protect Prod. It is the most efficient approach for sequential environments.
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 single approval for all environments by adding an approval to the pipeline.
Why it's wrong here
Azure Pipelines does not support a pipeline-level approval that gates all environments. Approvals are configured per environment (or per stage in YAML). Adding a single approval is not possible in this manner. Even if it were, it would not ensure that Prod is specifically approved before deployment, as it would apply to all stages.
- ✓
Add a pre-deployment approval only to the Prod environment.
Why this is correct
Adding a pre-deployment approval only to Prod ensures that Prod deployments require manual approval, while Dev and Test can deploy automatically. This minimizes the number of approvals to just one per release, satisfying the requirement that Prod is never deployed without approval. It balances control and efficiency.
- ✗
Add a post-deployment approval to the Test environment.
Why it's wrong here
A post-deployment approval on Test would require approval after Test deployment, which does not prevent Prod from deploying without approval. It adds an unnecessary approval step and does not meet the requirement to control Prod deployment. Post-deployment approvals are for verifying after deployment, not for gating subsequent stages.
- ✗
Add a pre-deployment approval to each environment.
Why it's wrong here
Adding a pre-deployment approval to each environment would require separate approvals for Dev, Test, and Prod. This increases the number of approvals and manual effort, which contradicts the goal of minimizing approvals. While it ensures Prod is approved, it does not optimize the process as required.
Visual reference
Go deeper
Related to this question
Learn chapter
Implementing a Release Pipeline
Key term
Pipeline
A pipeline is an automated series of steps that takes code from development to production, ensuring quality and speed.
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.
About these practice questions
This AZ-400 question is part of Courseiva's 696-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 and reviewed by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
Last reviewed September 2026 · checked against the official Microsoft exam blueprint
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.