AZ-400 Design and implement source control Practice Question
A company has a policy that all code changes must be reviewed by at least two people. However, for urgent bug fixes, they want to allow a single reviewer. How should they configure the branch policy?
⚠ Common exam trap
Many candidates confuse 'policy override' with 'bypassing all policies' or think a build validation can count approvals, when in fact Azure Repos requires explicit permission-based override settings for urgent scenarios.
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
✓
Set minimum number of reviewers to 2, but allow policy override for urgent fixes
Azure Repos branch policies allow you to set a minimum number of reviewers (e.g., 2) and then enable the 'Allow policy override' setting for urgent fixes. This lets authorized users bypass the two-reviewer requirement for critical bug fixes while maintaining the default policy for normal changes.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Set minimum number of reviewers to 1 and require a separate approval from a manager
Why it's wrong here
This setting requires one reviewer and a separate manager approval, but the manager approval is not a code review and does not count toward the two-reviewer requirement, so the change could still be merged with only a single reviewer providing code feedback.
- ✗
Set minimum number of reviewers to 2 and allow resetting code review votes on new pushes
Why it's wrong here
Requiring two reviewers and resetting votes on new pushes enforces that the two selected reviewers must re-approve the latest changes, but it does not reduce the required number of distinct reviewers to one; it only ensures approvals are valid against the updated code.
- ✗
Configure a build validation policy that checks number of approvals
Why it's wrong here
A build validation policy runs a build as a pre-merge check, but it cannot inspect or enforce human approval counts; it has no access to the review/vote data and cannot block a PR based on the number of reviewers.
- ✓
Set minimum number of reviewers to 2, but allow policy override for urgent fixes
Why this is correct
This allows the two-reviewer policy to be applied normally, while still permitting urgent fixes to be merged without two approvals; the override requires a justification and is logged for audit, balancing policy enforcement with operational flexibility.
Go deeper
Related to this question
Learn chapter
Introduction to DevOps and Azure DevOps
Key term
Bug
A bug is an error, flaw, or fault in software that causes it to produce an incorrect or unexpected result, or to behave in unintended ways.
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
One of 823 original AZ-400 practice questions on Courseiva, each with a full explanation and wrong-answer analysis — not exam dumps or protected exam content. 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.