AZ400-Q: Human approval before production deployment
Q: A deployment stage targets an environment in Azure Pipelines, and a specific human must sign off before the release is deployed there. Which feature enforces this requirement?
- A) A deployment gate checking a health endpoint
- B) An environment approval (manual approval check) ✓
- C) A branch policy on the repo
- D) A service-connection validation test
Answer: B. Environment approvals are manual approval checks you configure on an Azure Pipelines environment; a designated approver must approve before deployment proceeds. Deployment gates are automated pass/fail checks. Service connections and branch policies handle access/CI, not stage-level sign-off.
Why it helps
Distinguishing manual approvals from automated gates, and where to configure them (environments), is a core “approvals & gates” AZ-400 objective.