AZ-400 Practice Question: Design and implement build and release pipelines
You are designing a release pipeline for a mission-critical application. The pipeline must deploy to multiple environments (dev, test, prod) in sequence, with manual approval required before production deployment. Which Azure Pipelines feature should you use?
⚠ Common exam trap
Many exam-takers confuse pre-deployment approvals with deployment gates, thinking both are manual checks, but deployment gates are automated and based on external signals, not human 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
✓
Pre-deployment approvals
Pre-deployment approvals are the correct feature because they allow you to require manual sign-off before a release proceeds to a specific stage. In this scenario, you need a manual approval gate before production deployment, which is exactly what pre-deployment approvals enforce—the release pauses at the production stage until an authorized user approves it.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✓
Pre-deployment approvals
Why this is correct
Pre-deployment approvals define mandatory manual sign-off by designated approvers before a release is deployed to a stage. They act as a compliance checkpoint in the release pipeline and are distinct from automated gates, ensuring human oversight for mission-critical environments.
- ✗
Variable groups
Why it's wrong here
Variable groups are reusable containers for variables, secrets, and certificates that can be linked to pipelines or the library, but they do not trigger manual approval steps. While they can supply values to release tasks, they have no mechanism to require human sign-off before deployment.
- ✗
Pipeline triggers
Why it's wrong here
Pipeline triggers are events or conditions that automatically start a pipeline run, such as continuous integration, scheduled schedules, or other pipeline completions. They control when execution begins but cannot add approval requirements or manual sign-off to a stage deployment.
- ✗
Deployment gates
Why it's wrong here
Deployment gates are automated health-check conditions, such as monitoring metrics, work-item queries, or Azure Function calls, that run before or after a deployment and can pause or fail the release if criteria aren't met. Unlike pre-deployment approvals, they are fully automatic and require no manual approval from a human.
Visual reference
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
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
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.