You have an Azure DevOps project named Project1 and an Azure subscription named Sub1. You need to prevent releases from being deployed unless the releases comply with the Azure Policy rules assigned t

The correct answer is A. Add a deployment gate.. You can check policy compliance with gates. You can extend the approval process for the release by adding a gate. Gates allow you to configure automated calls to external services, where the results are used to approve or reject a You can use gates to ensure that the release meet

Submitted by daniela_cl· Mar 6, 2026Design and implement build and release pipelines

Question

You have an Azure DevOps project named Project1 and an Azure subscription named Sub1. You need to prevent releases from being deployed unless the releases comply with the Azure Policy rules assigned to Sub1. What should you do in the release pipeline of Project1?

Options

AAdd a deployment gate.
BModify the Deployment queue settings.
CConfigure a deployment trigger.
DCreate a pipeline variable.

How the community answered

(16 responses)

A
75% (12)
B
13% (2)
C
6% (1)
D
6% (1)

Explanation

You can check policy compliance with gates. You can extend the approval process for the release by adding a gate. Gates allow you to configure automated calls to external services, where the results are used to approve or reject a You can use gates to ensure that the release meets a wide range or criteria, without requiring user intervention. https://docs.microsoft.com/en-us/azure/devops/pipelines/release/deploy-using-approvals

Topics

#deployment gates#Azure Policy#release pipeline#compliance

Community Discussion

No community discussion yet for this question.

Full AZ-400 Practice