SC-100 · Question #157
Your company uses Azure Pipelines and Azure Repos to implement continuous integration and continuous deployment (CI/CD) workflows for the deployment of applications to Azure. You are updating the…
The correct answer is B. branch policies in Azure Repos. Branch policies in Azure Repos directly enforce the requirement that all code changes must go through pull requests before they can be merged and subsequently deployed by the CI/CD pipeline. You can configure branch policies on protected branches (e.g., main or release) to…
Question
Your company uses Azure Pipelines and Azure Repos to implement continuous integration and continuous deployment (CI/CD) workflows for the deployment of applications to Azure. You are updating the deployment process to align with DevSecOps controls guidance in the Microsoft Cloud Adoption Framework for Azure. You need to recommend a solution to ensure that all code changes are submitted by using pull requests before being deployed by the CI/CD workflow. What should you include in the recommendation?
Options
- Acustom roles in Azure Pipelines
- Bbranch policies in Azure Repos
- CAzure policies
- Dcustom Azure roles
How the community answered
(26 responses)- A4% (1)
- B85% (22)
- C4% (1)
- D8% (2)
Explanation
Branch policies in Azure Repos directly enforce the requirement that all code changes must go through pull requests before they can be merged and subsequently deployed by the CI/CD pipeline. You can configure branch policies on protected branches (e.g., main or release) to require a minimum number of reviewers, require linked work items, require passing build status checks, and-most importantly-block direct pushes entirely, forcing all changes through the pull request process. Option A (custom roles in Azure Pipelines) controls who can run pipelines, not how code is submitted. Option C (Azure Policy) governs Azure resource configurations, not source code workflows. Option D (custom Azure roles) applies to Azure resource access control. Branch policies are the native Azure DevOps mechanism for enforcing PR-based workflows aligned with DevSecOps controls.
Topics
Community Discussion
No community discussion yet for this question.