An application is deployed to Production-A and Production-B via Azure Pipelines. Before marking the application as complete and ready for release to Production-B, you must ensure there are no active Azure Monitor alerts in Production-A and minimize administrative effort. What should you add to the pipeline?

Adding a post-deployment gate to the Production-A environment stage that queries Azure Monitor is the correct solution. A post-deployment gate runs after deployment to Production-A but before the pipeline proceeds to subsequent stages (like Production-B). This ensures that Production-A is stable and free of active alerts before the application is considered ready for further release, directly addressing the requirement. Querying Azure Monitor within the gate allows for automated verification, minimizing administrative effort. Adding a pre-deployment gate to Production-B would check Production-A before deploying to Production-B, but it wouldn't be tied to the completion of the Production-A deployment itself. A post-deployment approval would require manual intervention, which doesn't minimize administrative effort. A pre-deployment gate in Production-A would run before deployment to Production-A, which is too early to check for post-deployment alerts.