Gating an App1 Release on Performance Baselines with an Azure Pipelines Deployment Gate
You have an Azure pipeline that is used to deploy an app named App1. You need to ensure that new versions of App1 are released only if they exceed performance baselines. The solution must minimize administrative effort. What should you configure?
Community Votes
67% of anonymous learners picked answer D. Votes are pick records left by other test-takers — they are not the verified answer.
Community Insight
A deployment gate is the native mechanism that pauses a release until an external condition is satisfied, so gating on a query that returns the performance data lets the pipeline itself enforce the baseline instead of a person approving by hand.
An Azure pipeline deploys an app named App1, and a new version may only be released if it exceeds its performance baselines, with the minimum of administrative effort. The release must be held automatically until a measured condition is verified rather than relying on someone to remember to check.
Configuring an Azure Monitor alert instead. An alert only notifies someone that performance degraded, which still leaves a human in the loop and does not stop the release, whereas a gate is what actually blocks the deployment until the condition passes.
Community Discussion (8 comments)
Comments & Corrections
No comments yet — spotted an error or have a note? Share it below.
Expert Analysis
Why the Answer Is Correct
The requirement is conditional release: App1 advances only when it exceeds its performance baselines, and it must happen with minimal administrative effort. A deployment gate is the pipeline feature that pauses a release until a specified condition evaluates to satisfied, so a gate whose condition queries the performance data enforces the baseline automatically and hands the decision to the pipeline. The vote was 67 for D. FeriAZ described the mechanism directly, noting that deployment gates let you pause the release pipeline until specific conditions are met, which is exactly the required behavior. Approach_Belgium_SA made the complementary point that an Azure Monitor alert merely fires a notification when performance is negatively affected, which is not a release control.Why the Other Options Are Wrong
An Azure Monitor alert (C) is a notification mechanism, so it can tell a human that a threshold was breached but it does not hold the release, and a pipeline that keeps deploying on alerts is not enforcing the baseline. This distinction is what separates a gate from an alert. An Azure Pipelines release artifact (A) is the packaged output of a build or release, so configuring one adds no conditional logic and cannot evaluate a performance baseline. An Azure Repos branch policy (B) governs source control merges, so it could block a pull request from merging but it has no visibility into a deployment's runtime performance and therefore cannot gate a release.Community Comment Notes
The community favored D at 67 votes, and the two substantive comments for D both defended gates over alerts: FeriAZ explained that deployment gates pause the release until conditions are met, and Approach_Belgium_SA noted that an Azure Monitor alert only throws an alert when performance is negatively affected. Nian, the highest-liked commenter, raised a sharp objection that a deployment gate would need a query against Azure Monitor alerts, which suggests the real-world design needs both, and asked whether the question actually wanted two selections. Gooldmember answered the same concern by observing that if the question had said what to configure first, the answer would be the monitor side. d526b99's comment simply recorded that an AI tool gave the same answer, which is corroboration rather than reasoning.Official Reference
Related Analysis
Practice All AZ-400 Questions
Access 100 questions with complete answers and detailed explanations.
View Full AZ-400 Practice Test →