AZ-400 Practice Question: Design and implement build and release pipelines
You have an Azure DevOps pipeline that deploys to multiple environments. You need to ensure that approvals are required before production deployment. Which pipeline configuration should you use?
⚠ Common exam trap
Many candidates confuse branch policies (which control code merging) with deployment approvals (which control release execution), leading them to select option C instead of the environment-based approval mechanism.
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
✓
Define an environment with required approvers for the production stage
Azure DevOps environments allow you to define required approvers for a specific stage (e.g., production). When a pipeline deploys to that environment, it pauses and waits for manual approval before proceeding, ensuring that production deployments are gated by authorized personnel.
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 the pipeline trigger to 'Manual' only
Why it's wrong here
Setting the pipeline trigger to Manual only controls when the pipeline is scheduled to run, but it does not add any approval checkpoint. Any pipeline run triggered manually by a user with permission will start the production deployment without requiring a separate designated reviewer or approval step, so it fails to enforce the required human approval.
- ✗
Add a 'Manual Intervention' task in the pipeline
Why it's wrong here
Adding a Manual Intervention task pauses the pipeline until a user clicks Resume or Reject, but it is an inline pipeline task, not a formal environment approval gate. Unlike environment required approvers, it is not tied to a specific deployment environment, does not record explicit approval in the deployment history, and can be bypassed if the pipeline is edited.
- ✗
Configure branch policies on the main branch
Why it's wrong here
Branch policies on the main branch, such as required pull request reviews or status checks, only protect the source code from being merged without review. They do not execute as part of the pipeline deployment process and cannot block a build that already exists from being deployed to production, so they are irrelevant to enforcing deployment approvals.
- ✓
Define an environment with required approvers for the production stage
Why this is correct
Defining an environment with required approvers is the correct approach because Azure Pipelines environments provide pre-deployment approval checks that pause the pipeline before the production stage runs. Each deployment to that environment must be explicitly approved by the listed users or groups, creating an auditable, enforceable gate before any production release proceeds.
Go deeper
Related to this question
Learn chapter
Introduction to DevOps and Azure DevOps
Key term
Azure DevOps
Azure DevOps is a Microsoft service that provides development tools for planning, building, testing, and deploying software applications using automated pipelines and collaboration features.
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.