AZ-400 Practice Question: Design and implement build and release pipelines
Your release pipeline deploys to multiple environments (Dev, Test, Prod) using approval gates. Recently, the Prod deployment failed because a manual validation task timed out after 30 minutes. You need to ensure that if the manual validation is not approved within 15 minutes, the pipeline automatically rejects the deployment and sends a notification. What should you do?
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
✓
In the Manual Validation task, set 'Timeout' to 15 and 'On timeout' to 'Reject'.
The Manual Validation task has a 'Timeout' setting and an 'On timeout' option. Setting Timeout to 15 minutes and On timeout to 'Reject' will automatically reject the deployment if not approved within 15 minutes. Additionally, you can configure a notification using an Azure DevOps subscription or service hook for the rejection event. Option A is incorrect because the stage timeout does not specifically handle manual validation rejection. Option C is incorrect because, although pre-deployment approvals do have a timeout that can reject on timeout, they apply to the approval gate before the stage, not to a manual validation task within the stage. Option D is incorrect because adding a PowerShell task is unnecessary and less reliable than the built-in timeout behavior.
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 'Timeout in minutes' for the entire stage to 15.
Why it's wrong here
Setting the stage timeout to 15 minutes applies an overall deadline for the entire stage, so if any task (including pre-deployment or other post-deployment tasks) runs too long, the stage is cancelled. It does not specifically target the manual validation task, and when the timeout is hit the stage is cancelled rather than the deployment being explicitly rejected, so it fails to provide the intended 'reject on timeout' behavior.
- ✓
In the Manual Validation task, set 'Timeout' to 15 and 'On timeout' to 'Reject'.
Why this is correct
The Manual Validation task has a 'Timeout' property and an 'On timeout' action. By setting the timeout to 15 and 'On timeout' to 'Reject', if a user does not respond within 15 minutes, the task automatically rejects the deployment, which immediately stops the pipeline and marks the deployment as rejected. This is the only option that directly enforces the desired rejection on a per-validation basis.
- ✗
Configure a pre-deployment approval with a timeout of 15 minutes.
Why it's wrong here
Pre-deployment approvals in Azure DevOps have a timeout, but when the timeout expires the approval is merely expired—it is not automatically rejected. By default, an expired approval does not block the deployment; it simply removes the pending approval, which could actually allow the deployment to continue, defeating the requirement to reject within 15 minutes.
- ✗
Add a PowerShell task after the manual validation that checks the status and cancels the pipeline if not approved.
Why it's wrong here
A PowerShell task after the manual validation cannot 'cancel' the pipeline; at best it can throw an error to fail a single task. Moreover, because tasks run sequentially, the PowerShell task would only execute after the manual validation has already completed (either approved or rejected), so it cannot retroactively enforce a timeout on that validation nor replicate the built-in 'On timeout' rejection behavior.
Go deeper
Related to this question
Learn chapter
Introduction to DevOps and Azure DevOps
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 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.