You have an Azure pipeline that is used to deploy an app named App1. You need to ensure that new versions of App1 are released only if they exceed performance baselines. The solution must minimize adm

Question

Options

• Aan Azure Pipelines release artifact
• Ban Azure Repos branch policy
• Can Azure Monitor alert
• Dan Azure Pipelines deployment gate

• A
  5% (1)
• B
  5% (1)
• C
  14% (3)
• D
  76% (16)

Explanation

Azure Pipelines Deployment Gates

Option D is correct because deployment gates in Azure Pipelines allow you to define automated conditions that must be met before a release can proceed to the next stage - including querying Azure Monitor metrics to verify that performance baselines are satisfied. This is a built-in feature that requires minimal configuration and no custom scripting, directly minimizing administrative effort.

Why the distractors are wrong:

• A (Release Artifact): A release artifact is simply the packaged output (build files) used in a pipeline; it has no mechanism to evaluate performance conditions before deployment.
• B (Branch Policy): Branch policies in Azure Repos control code merging rules (e.g., requiring pull request reviews), not runtime performance validation during releases.
• C (Azure Monitor Alert): While Azure Monitor can detect performance issues and trigger notifications, it cannot natively block or gate a pipeline deployment on its own without additional configuration, increasing administrative overhead.

Memory Tip: Think of deployment gates as literal "gates" on a highway - traffic (your release) only passes through when conditions are met. If performance doesn't meet the baseline, the gate stays closed. Gates = conditions that guard your release pipeline.

No community discussion yet for this question.