AZ-400 Practice Question: Design and implement build and release pipelines
Your Azure DevOps pipeline deploys to multiple environments (Dev, Test, Prod) using YAML multi-stage pipelines. The Prod deployment requires manual approval. However, the approval gate shows 'Pending' even after an authorized user approves. What is the most likely cause?
⚠ Common exam trap
The trap is that candidates assume an approval applies to the stage or environment indefinitely, rather than to a specific pipeline run/commit. A new commit generates a new run with a new pending approval.
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
✓
The approval gate is configured to require approval on the latest commit, but a newer commit was pushed after the approval.
In Azure DevOps, approvals are associated with a specific pipeline run and its commit. When a new commit is pushed after an approval, it triggers a new pipeline run. The new run has its own approval requirement, so it remains 'Pending' until approved. The previous approval does not carry over to the new run.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
The pipeline run was triggered by a PR merge, and the approval needs to be re-applied after the build completes.
Why it's wrong here
Wrong: Approval for an environment is tied to the specific pipeline run and its commit, so a PR merge does not retroactively invalidate an existing approval; the approval remains valid for the run that triggered it, and only a new run would need approval.
- ✗
The build pipeline includes a step that modifies the approval settings.
Why it's wrong here
Wrong: Azure Pipelines does not allow pipeline steps to modify environment approval settings, because approvals are configuration defined at the environment or pipeline level, not accessible via build tasks; attempting to do so would be outside the API scope of tasks.
- ✓
The approval gate is configured to require approval on the latest commit, but a newer commit was pushed after the approval.
Why this is correct
Correct: Environment approval gates are configured to evaluate the latest commit of the pipeline run; if a newer commit is pushed after the approval was granted, the gate detects the changed commit and requires re-approval before the deployment proceeds.
- ✗
The approver is not a member of the security group defined in the approval settings.
Why it's wrong here
Wrong: The scenario states the approver is authorized in the security group, so membership is not the issue; the re-approval is triggered by the commit changing, not by an authorization failure.
Go deeper
Related to this question
Learn chapter
Introduction to DevOps and Azure DevOps
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.
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.
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.