Microsoft Certified: DevOps Engineer ExpertDesign and implement pipelinesEasy
A DevOps team is implementing a new release strategy for a critical microservice. The team wants to ensure that a new version is only promoted to production if it has successfully passed all automated tests, has no open critical bugs in the bug tracking system, and has been approved by the security team. Which Azure DevOps feature should the team primarily use to enforce these conditions before deployment?
- AAgent pools
- BDeployment groups
- CTask groups
- DPre-deployment approvals and gates
Show answer & explanationAnswer & explanation
Correct answer: D. Pre-deployment approvals and gates
Pre-deployment approvals and gates in Azure DevOps are designed to enforce conditions and obtain sign-offs before a release proceeds to the next stage, directly addressing the requirements for automated tests, bug status, and security approval.
Why the other options are wrong
- A. Agent pools manage the compute resources that run pipeline jobs, not release conditions.
- B. Deployment groups are used to organize target machines for deployments, not to enforce conditions or approvals.
- C. Task groups are collections of tasks that can be reused in pipelines, not mechanisms for enforcing release conditions.
Release Gates
Release gates in Azure DevOps automatically check for health and success criteria from external services before allowing a release to proceed to the next stage or environment.
- Can be configured for pre-deployment or post-deployment stages.
- Continuously monitor conditions and delay deployment until all conditions are met.
- Integrate with various services like Azure Monitor, Work Items, and custom APIs.
Memory trick: Gates guard the path, ensuring all checks pass.