You want to ensure new releases are deployed to production only if they meet predefined performance baseline criteria in a staging environment. Which Azure Pipelines feature should you use to block deployments that do not meet the performance baseline?

A gate in Azure Pipelines is designed to pause the execution of a release pipeline until specific conditions are met. In this scenario, you can configure a gate to query a performance monitoring system (e.g., Azure Monitor, Application Insights) for performance metrics from the staging environment. If the metrics fall below the predefined baseline, the gate will fail, blocking the deployment to production. An Azure Scheduler job is for scheduling tasks, not for real-time evaluation of deployment conditions. A trigger initiates a pipeline run, but doesn't block it based on external conditions during execution. An Azure Function can execute custom logic, but a gate provides a built-in, more integrated solution for blocking deployments based on external conditions within the release pipeline itself.