Ensuring Release Deployment Compliance with Performance Baseline Criteria in Azure Pipelines

C

Scenarios and use cases for gates include:

-> Quality validation. Query metrics from tests on the build artifacts such as pass rate or code coverage and deploy only if they are within required thresholds.

Use Quality Gates to integrate monitoring into your pre-deployment or post-deployment. This ensures that you are meeting the key health/performance metrics

(KPIs) as your applications move from dev to production and any differences in the infrastructure environment or scale is not negatively impacting your KPIs.

Note: Gates allow automatic collection of health signals from external services, and then promote the release when all the signals are successful at the same time or stop the deployment on timeout. Typically, gates are used in connection with incident management, problem management, change management, monitoring, and external approval systems.

https://docs.microsoft.com/en-us/azure/azure-monitor/continuous-monitoring https://docs.microsoft.com/en-us/azure/devops/pipelines/release/approvals/gates?view=azure-devops

The correct answer to this question is C. a gate.

In this scenario, the company is using Azure Pipelines for build and release management, and they want to ensure that new releases meet certain performance baseline criteria before being deployed to production. To achieve this, a gate can be used in Azure Pipelines to prevent the deployment of releases that fall below the performance baseline.

A gate is a deployment control in Azure Pipelines that blocks the deployment pipeline until pre-defined conditions are met. In this case, the gate will check whether the performance baseline criteria are met in the staging environment before allowing the release to be deployed to production.

To set up a gate, you can use the "Gate" task in Azure Pipelines. This task allows you to define the conditions that need to be met before the deployment pipeline can proceed. In this case, you would define the performance baseline criteria as the condition that needs to be met.

Once the gate is set up, it will be triggered as part of the deployment pipeline. If the performance baseline criteria are not met in the staging environment, the gate will block the deployment pipeline, preventing the release from being deployed to production.

In summary, a gate can be used in Azure Pipelines to prevent the deployment of releases that do not meet defined performance baseline criteria in the staging environment first.