Checking for Azure Monitor Alerts Before Marking App Complete in the Production-A Stage

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.