AZ-400 Practice Question: Design and implement build and release pipelines
Which TWO features can you use to enforce quality gates before a production deployment in Azure Pipelines?
⚠ Common exam trap
Test-takers frequently confuse pre-deployment quality checks (like branch policies or scheduled triggers) with the specific deployment-time gates and approvals that Azure Pipelines provides for production environments.
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
✓
Approval checks on environments
Approval checks on environments allow you to require manual sign-off before a release proceeds to a production stage. This enforces a quality gate by ensuring that a designated approver reviews and authorizes the deployment. Option E is correct because deployment gates evaluate health metrics (e.g., from Azure Monitor or Application Insights) automatically, blocking or allowing the deployment based on predefined conditions such as error rates or performance thresholds.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Scheduled triggers
Why it's wrong here
Scheduled triggers automatically start a pipeline at predefined times, such as nightly builds, but they do not evaluate any conditions or validate quality. They simply initiate the pipeline run and have no mechanism to block or gate deployment based on metrics or approvals.
- ✗
Branch policies on repositories
Why it's wrong here
Branch policies on repositories enforce requirements like pull request reviews and build validations before code can be merged, but they operate at the source control level. They do not directly control deployment pipelines or serve as quality gates just before deployment in Azure DevOps.
- ✗
Pipeline decorators
Why it's wrong here
Pipeline decorators inject additional steps into pipelines at runtime, allowing organizations to add required tasks like linting or security scans. However, they cannot pause and wait for external signals or evaluate health metrics before proceeding, so they do not act as deployment gates.
- ✓
Approval checks on environments
Why this is correct
Approval checks on environments are a valid quality gate feature in Azure Pipelines. They require designated users or groups to explicitly approve a deployment before it is released to that environment, providing manual sign-off as a gate.
- ✓
Deployment gates evaluating health metrics
Why this is correct
Deployment gates evaluate real-time health metrics from monitoring systems, such as Azure Monitor or Application Insights, before and after deployment. If the metrics do not meet configured thresholds, the deployment is paused or not initiated, enforcing an automated quality gate.
Visual reference
Go deeper
Related to this question
Learn chapter
Introduction to DevOps and Azure DevOps
Key term
Azure Pipelines
Azure Pipelines is a cloud-based CI/CD service from Microsoft that automatically builds, tests, and deploys code to any platform or cloud.
Key term
Application Insights
Application Insights is an Azure monitoring service that helps developers detect, diagnose, and understand issues in live web applications by collecting telemetry data like requests, exceptions, and performance counters.
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.