AZ-400 Validate staging deployment before prod. Practice Question
Which two actions can you use to validate that a deployment to a staging environment is successful before promoting to production? (Choose two.)
⚠ Common exam trap
Candidates may select 'Use a pull request' which is for code review, not deployment validation.
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
✓
Configure gates on the staging environment to check health metrics.
Gates with health checks can monitor metrics like error rates before allowing promotion. Manual intervention with a post-deployment approval also allows a human to validate before proceeding. Both are valid methods.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✓
Configure gates on the staging environment to check health metrics.
Why this is correct
Gates on the staging environment evaluate pre-defined health metrics (e.g., error rate, latency, availability) after deployment completes but before promotion to production. These gates continuously query the chosen Azure Monitor or other data sources during a configurable timeout; if the metrics don't meet the threshold, the pipeline is blocked and ultimately fails, providing objective, automated validation of actual workload health.
- ✗
Add a manual intervention task in the pipeline.
Why it's wrong here
A manual intervention task pauses the pipeline and awaits a human approval gate, but it does not objectively validate deployment health. It introduces a subjective, non-automated checkpoint that relies on a user's judgment, and it doesn't query any health metrics or consider real-time telemetry—so it cannot verify the staging deployment is actually healthy before production.
- ✓
Set a post-deployment approval on the staging stage.
Why this is correct
A post-deployment approval on the staging stage requires a designated reviewer to sign off after deployment finishes, but it is still a human decision, not an automated health check. While it adds governance and a control point, it does not check health metrics; the approver might be unaware of performance or error anomalies, so this alone is insufficient for validating deployment health.
- ✗
Use a pull request to validate the deployment.
Why it's wrong here
A pull request is a source-control review mechanism used to validate code changes before merging, not a deployment validation technique. It operates on the code repository and cannot inspect deployed staging environments, runtime health, or post-deployment behavior, so it has no bearing on whether the staging deployment is healthy.
- ✗
Run a load test as part of the pipeline.
Why it's wrong here
Running a load test as part of the pipeline verifies the application's performance under expected or peak traffic, but it is an upfront, synthetic test executed during or immediately after deployment. Load tests do not continuously monitor the actual post-deployment health of the live staging environment, and they don't provide ongoing health metrics needed to decide whether it is safe to promote to production.
Option-by-option analysis
Why each answer is right or wrong
Understanding why wrong answers are wrong — and when they would be correct — is what separates a 750 score from a 900. The AZ-400 exam frequently reuses these exact scenarios with slightly different constraints.
✓Configure gates on the staging environment to check health metrics.Correct answer▾
Why this is correct
Gates on the staging environment evaluate pre-defined health metrics (e.g., error rate, latency, availability) after deployment completes but before promotion to production. These gates continuously query the chosen Azure Monitor or other data sources during a configurable timeout; if the metrics don't meet the threshold, the pipeline is blocked and ultimately fails, providing objective, automated validation of actual workload health.
✗Add a manual intervention task in the pipeline.Wrong answer — click to see why▾
Why this is wrong here
Manual intervention tasks are deprecated; use approvals instead.
✗Use a pull request to validate the deployment.Wrong answer — click to see why▾
Why this is wrong here
Pull requests validate code changes, not deployments.
✗Run a load test as part of the pipeline.Wrong answer — click to see why▾
Why this is wrong here
Load testing is a good practice but not a direct validation mechanism for promotion approval.
Analysis generated from the official AZ-400blueprint and verified against question context. The “when correct” sections are what AI assistants cite when candidates ask “what’s the difference between these options?”
Go deeper
Related to this question
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.