AZ-400 Practice Question: Design and implement build and release pipelines
Your Azure DevOps project uses Git for source control. You want to enforce that all code changes are reviewed before merging into the main branch. Which branch policy should you enable?
Answer choices
Why each option matters
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Require a minimum number of reviewers.
The 'Require a minimum number of reviewers' branch policy ensures that a specified number of reviewers must approve a pull request before it can be merged, directly enforcing code review. Option A is incorrect because 'Allow only comment resolution' pertains to how comments are resolved, not requiring approvals. Option B is incorrect because 'Require a successful build before merging' validates build status but does not enforce review. Option C is incorrect because 'Limit merge types to squash merge' controls the merge strategy, not the review process.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Allow only comment resolution.
Why it's wrong here
This branch policy only controls whether comment threads must be resolved before a merge, but it does not require any independent human approval. A developer could dismiss or resolve comments without the changes being reviewed by another person, so it fails to enforce a proper code review process.
- ✗
Require a successful build before merging.
Why it's wrong here
Build validation runs a CI pipeline and blocks a merge if the build or tests fail, but it only verifies code quality from an automated perspective. It does not require any human to review or approve the changes, so a successful build alone cannot enforce a code review before merging.
- ✗
Limit merge types to squash merge.
Why it's wrong here
Limiting merge types to squash merge only affects how commit history is collapsed into a single commit when the pull request is completed. This simplifies history but does not introduce any requirement for reviewers or approvals, so it does not enforce code review.
- ✓
Require a minimum number of reviewers.
Why this is correct
Setting a minimum number of reviewers is the branch policy that directly enforces code review: a pull request cannot be completed until the specified number of distinct users have explicitly approved it. This ensures that changes receive independent human verification before they are merged into the target branch.
Visual reference
Go deeper
Related to this question
Learn chapter
Introduction to DevOps and Azure DevOps
Key term
Code review
A code review is a systematic examination of source code by one or more developers to find defects, improve quality, and enforce coding standards before it is merged into the main codebase.
Key term
Branch policy
A branch policy is a set of rules and conditions enforced on a Git branch to control how code changes are proposed, reviewed, and merged, ensuring code quality and protecting critical branches.
About these practice questions
Courseiva writes every AZ-400 question from scratch — 823 in total, each with an explanation and a wrong-answer breakdown. None are copied from real exams or dumps. Learn why practice questions differ from exam dumps →
JA
Written by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
This AZ-400 practice question is part of Courseiva's free Microsoft certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the AZ-400 exam.