Pipeline1 deploys Azure resources defined by Bicep modules. To ensure all releases comply with Azure Policy before production deployment, what should you configure?

The correct option is to configure a deployment gate for Pipeline1 and include the Azure DevOps Security and compliance assessment task. This task is specifically designed to evaluate Azure Policy compliance for ARM templates and Bicep files within an Azure DevOps pipeline, making it ideal for pre-production checks. A deployment gate ensures this check occurs automatically before the production stage is entered, preventing non-compliant deployments. Adding a step to Pipeline1 for a What If deployment is a good practice for validating resource changes but doesn't directly assess Azure Policy compliance. Configuring a deployment gate with Azure Automation for a What If deployment is overly complex and less direct than using the built-in compliance assessment task. Creating an Azure DevOps build on pull request creation assesses code quality but doesn't directly evaluate the deployed resources against Azure Policy at the deployment stage.