AZ400-Q: Deployment gates before full rollout
Q: A release pipeline first deploys to a small subset of users/servers, waits, and automatically checks a health telemetry query (e.g., request failures) before promoting the release to the remaining deployment ring. Which two mechanisms are combined here?
- A) Canary deployment + deployment gate ✓
- B) Blue-green + manual approval
- C) Rolling + feature flag
- D) Shadow deployment + branch policy
Answer: A. Sending the new version to a small canary group first, then using an automated deployment gate (an Azure Monitor query, REST API call, or work-item check) to validate health before proceeding to later rings is the canonical canary-plus-gate rollout. Gates are automated pass/fail checks; manual approvals are separate human sign-offs.
Why it helps
Combining deployment rings with automated gates is core to “design a release strategy” and gates-and-rollback objectives.
Related
deployment-gate · deployment-ring · canary-deployment · release-strategy