New releases must meet specified performance baselines in the staging environment before deployment to production. Which Azure Pipelines mechanism prevents deployment when staging performance baselines are not satisfied?

A Gate in Azure Pipelines is the correct mechanism because it allows you to automatically pause a pipeline and evaluate external conditions before proceeding. In this scenario, the gate would be configured to query a monitoring system for the staging environment's performance metrics. If the metrics do not meet the predefined baselines, the gate fails, preventing the deployment to production. Branch control checks are used to enforce policies on code branches, not to evaluate runtime performance. An Alert trigger initiates a pipeline based on an external event, but doesn't block a deployment based on conditions. An Approval check requires manual intervention and sign-off, which is not an automatic evaluation of performance baselines.