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

Adding a deployment gate is the correct solution because gates in Azure Pipelines are automated validations that run before or after a stage to ensure quality and compliance. A "Check Azure Policy compliance" gate can be configured to evaluate the resources deployed by the release against the Azure Policy rules in Sub1, preventing deployment if non-compliant. Modifying deployment queue settings primarily controls the order and concurrency of deployments, not policy compliance. Configuring a deployment trigger initiates a release based on events (e.g., code commit, schedule) but doesn't enforce policy. Creating a pipeline variable stores data for use within the pipeline but doesn't provide enforcement of external policies.