AZ-400 Configure processes and communications Practice Question
Your team wants to include a manual validation step before deploying to production. Which Azure Pipelines feature should they use?
⚠ Common exam trap
Watch out — candidates often confuse environment checks (which may include both automated and manual checks) with the specific pre-deployment approval gate feature. Environment checks can include an 'Approvals' check, but the question asks for the feature that explicitly models the pre-deployment approval workflow, which is 'Pre-deployment conditions with approval gates'.
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
✓
Pre-deployment conditions with approval gates.
Pre-deployment conditions with approval gates allow you to require manual approval before a release is deployed to a specific stage, such as production. This is the correct feature because it explicitly pauses the pipeline before deployment and waits for designated approvers to validate the build, meeting the requirement for a manual validation step. Environment checks are a broader feature that can include both automated checks and manual approvals; however, the specific configuration for requiring manual approval in a release pipeline is pre-deployment conditions with approval gates.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Pipeline decorators.
Why it's wrong here
Pipeline decorators inject additional steps into pipeline runs at compile time, but they cannot enforce a manual validation gate because they lack the ability to pause execution and wait for human approval.
- ✗
Environment checks.
Why it's wrong here
Environment checks are automated evaluations (e.g., branch protection or resource availability) that run as part of the deployment, but they do not provide a manual approval step for a human to review and approve before the deployment begins.
- ✓
Pre-deployment conditions with approval gates.
Why this is correct
Pre-deployment conditions with approval gates define a manual approval step that must be completed by authorized reviewers before the deployment job is allowed to start, making it the correct way to include a manual validation step before deployment.
- ✗
Post-deployment gates.
Why it's wrong here
Post-deployment gates run after the deployment has already completed, so they can only approve or reject the outcome of a finished deployment and cannot block or validate the deployment before it starts.
Visual reference
Go deeper
Related to this question
Learn chapter
Introduction to DevOps and Azure DevOps
Key term
Environment
An environment is a dedicated set of computing resources, configurations, and services used to develop, test, or host software applications in a controlled and repeatable way.
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.