Microsoft Certified: DevOps Engineer ExpertDesign and implement pipelinesHard

A DevOps team is configuring a release pipeline in Azure DevOps for an application deployed to multiple environments (Dev, QA, Staging, Production). They want to ensure that the release automatically proceeds to the next environment only if all automated tests in the previous environment have passed, AND no new critical performance alerts have been triggered in Azure Monitor for a specified duration. This check should run continuously for a period before allowing the release to move forward. Which Azure DevOps feature should be used for this purpose?

  1. APre-deployment approvals
  2. BScheduled triggers
  3. CDeployment conditions
  4. DPost-deployment gates
Show answer & explanation

Correct answer: D. Post-deployment gates

Post-deployment gates are designed to continuously monitor external services (like Azure Monitor for critical alerts) after a deployment to an environment. They delay the progression to the next stage until all defined conditions (e.g., no critical alerts for X duration) are met, ensuring the stability and health of the deployed application before further rollout.

Why the other options are wrong

  • A. Pre-deployment approvals are for manual sign-offs before a stage starts, not for continuous automated monitoring after a deployment.
  • B. Scheduled triggers initiate releases at specific times, not based on continuous monitoring of post-deployment health.
  • C. Deployment conditions define when a stage should run (e.g., after a previous stage completes) but don't perform continuous monitoring for health metrics.

Post-deployment Gates (Azure DevOps)

Post-deployment gates in Azure DevOps are automated health and quality checks that run continuously after a stage completes successfully. They ensure that the application remains stable and healthy in that environment for a specified duration before the release can proceed to the next stage.

  • Monitors external services (e.g., Azure Monitor, Work Items, custom APIs).
  • Delays progression to the next stage until conditions are met.
  • Crucial for ensuring the stability of deployments across environments.

Memory trick: Post-gates guard the next step, ensuring the current is sound.

More Design and implement pipelines questions