Checking for Azure Monitor Alerts Before Marking App Complete in the Production-A Stage
Short answer
B A post-deployment gate on the Production-A stage queries Azure Monitor after the app runs there but before the stage completes, so alerts are checked first.
Question
Key Takeaways
The alert check must run against Production-A after the app has been deployed there but before the pipeline treats that stage as complete, which places it as a post-deployment gate on the Production-A stage rather than a pre-deployment gate on Production-B.
An app is deployed to two environments, Production-A and Production-B, by Azure Pipelines, and a release pipeline must mark the app complete and ready for Production-B. The requirement is that no active Azure Monitor alerts exist in Production-A before the app is marked complete, with minimal administrative effort, so the check has to be positioned relative to when Production-A finishes.
Common mistake: Adding a pre-deployment gate to the Production-B stage. That gate would run before deploying to Production-B, but the app has not yet been evaluated in Production-A at that point in a way that reflects its completed state, so the ordering relative to the completion decision is wrong.
Expert Analysis
Why the Answer Is Correct
The requirement ties the alert check to a specific moment: there must be no active Azure Monitor alerts in Production-A before the app is marked as complete. The app is marked complete at the end of the Production-A stage, so the check has to be attached to that stage and run after the deployment to Production-A but before the stage is treated as complete, which is precisely what a post-deployment gate on Production-A does. The vote was 59 for B. Mattt gave the clearest reading, pointing to the phrase before the app is marked as complete and concluding that Production-A must not be marked completed until the check passes, which is the signature of a post-deployment gate. danisancho added the supporting operational reason that Azure Monitor has to be queried once the app is actually running in Production-A, since an earlier query would see no meaningful alerts.
Why the Other Options Are Wrong
Adding a pre-deployment gate to the Production-B stage that queries Azure Monitor (A) places the check one stage too late. Dhibi_111 and Mo_alwaysjolling both favored this option reasoning that the gate prevents progressing to Production-B, and that reading is intuitive, but the requirement is about the completion of the app after Production-A, not about protecting the Production-B deployment, and the pre-deployment gate on B would let the Production-A stage complete and mark the app complete without ever having verified the alerts. Adding a post-deployment approval to the Production-A stage (C) inserts a manual sign-off rather than an automated alert query, so it fails both the minimize-administrative-effort requirement and the specific condition that the check query Azure Monitor.
Community Comment Notes
The community split 59 for B and 41 for A, and the two leading comments for A, Dhibi_111 with six likes and Mo_alwaysjolling with one, both reasoned that a pre-deployment gate on Production-B would check Production-A's alerts before proceeding, which captures the protect-the-next-stage intent but not the wording about marking the app complete. Mattt's comment carried equal weight with six likes and made the decisive observation that the requirement is about what happens before Production-A is marked complete. danisancho reinforced it with the observation that you can only query Azure Monitor meaningfully after the app is deployed to Production-A. The disagreement is about which stage the requirement anchors to, not about whether a gate is the right mechanism.
Official Reference
https://learn.microsoft.com/en-us/azure/devops/pipelines/process/checks?view=azure-devops
This link opens the official vendor documentation in a new tab.
Community Votes
59% of anonymous learners picked answer B. Votes are pick records left by other test-takers — they are not the verified answer.
Discussion 5 contributions
Compiled from public community threads and reader submissions, lightly edited for clarity. Handles and vote tallies are shown as recorded, and comments reflect the views of individual contributors.
From public community threads 5
-
Dhibi_111 👍 6 Answered ABy adding a pre-deployment gate in the Production-B environment stage that queries Azure Monitor, you ensure that the pipeline checks for any active Azure Monitor alerts in the Production-A environment before deploying to Production-B.
-
Mattt 👍 6 Answered BThe keyword is "before the app (Production-A) is marked as complete" It means Production-A shouldn't be marked as completed. So the option B is correct (post-deployment A)
-
danisancho 👍 4 Answered BI vote for B because you need to query Azure Monitor once the app is deployed to Production-A.
-
Mo_alwaysjolling 👍 1 Answered Aso you going b or a I'm going with A: To the Production-B environment stage, add a pre-deployment gate that will query Azure Monitor. This ensures that no active Azure Monitor alerts exist in the Production-A environment before proceeding with the deployment to Production-B, aligning with the requirement to check for alerts before marking the app as complete and minimizing administrative effort.
-
Sant25 👍 2A is correct
Reader comments & corrections
No reader corrections yet — spotted an error or have a note? Share it below.
Related Analysis
Practice All AZ-400 Questions
Access 100 questions with complete answers and detailed explanations.
View Full AZ-400 Practice Test →