Question 283 of 823
AZ-400 Configure processes and communications Practice Question
Your organization uses Azure DevOps and has a strict compliance requirement: all changes to the main branch must be reviewed by at least two members of the 'ComplianceTeam' group. Additionally, a static code analysis tool must run and its results must be published to the pull request. The ComplianceTeam is a custom group defined in Azure DevOps, not a Microsoft Entra ID group. The team wants to enforce this using branch policies. You need to configure the minimum number of reviewers and also ensure that the code analysis results are visible to reviewers. What should you do?
⚠ Common exam trap
It's easy for candidates to confuse 'Automatically included reviewers' (which only adds reviewers but does not enforce approval) with 'Require a minimum number of reviewers' (which enforces the actual approval count), leading them to choose Option D instead of A.
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
✓
Add a branch policy 'Require a minimum number of reviewers' set to 2, and specify the ComplianceTeam as required reviewers. Additionally, add a build policy that runs the code analysis and publishes results as a build summary.
The 'Require a minimum number of reviewers' branch policy enforces that at least two members from the ComplianceTeam must approve the pull request. Adding a build policy that runs static code analysis and publishes results as a build summary ensures the analysis output is visible directly in the PR, meeting the compliance requirement for both reviewer count and code analysis visibility.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✓
Add a branch policy 'Require a minimum number of reviewers' set to 2, and specify the ComplianceTeam as required reviewers. Additionally, add a build policy that runs the code analysis and publishes results as a build summary.
Why this is correct
Setting 'Require a minimum number of reviewers' to 2 and specifying ComplianceTeam as required reviewers enforces exactly two approvals from that team before a pull request can be merged. Because required reviewers are mandatory, any approval from a team member counts toward the minimum, and the policy blocks the merge until both approvals are present. Adding a build policy that runs code analysis and publishes results as a build summary integrates the compliance gate directly into the PR, giving reviewers the evidence needed to approve confidently. This combination fully satisfies the strict compliance requirement.
- ✗
Add a branch policy 'Require code owner review' and define the ComplianceTeam as code owners in a CODEOWNERS file.
Why it's wrong here
The 'Require a minimum number of reviewers' policy is the only one that enforces a specific numeric approval count; 'Require code owner review' merely requires at least one owner of the modified files to approve, not two from the ComplianceTeam. Code ownership based on CODEOWNERS is file-scoped, so a single owner outside ComplianceTeam could satisfy the policy, leaving the compliance team without a mandatory sign-off. Thus, this option fails to enforce two approvals from the required team.
- ✗
Add a branch policy 'Comment resolution' and configure the ComplianceTeam to resolve comments.
Why it's wrong here
Enabling the 'Comment resolution' branch policy only blocks merges until all active comment threads are marked resolved; it imposes no requirement on the number of approvals or on who performs the review. Configuring the ComplianceTeam to resolve comments lets them clear threads, but that action is not a formal approval and does not guarantee they have performed the required compliance analysis. Code analysis visibility via a build summary is also absent, so this option does not meet the strict compliance mandate.
- ✗
Add a branch policy 'Automatically included reviewers' and set the ComplianceTeam to be automatically added to all PRs.
Why it's wrong here
The 'Automatically included reviewers' policy simply adds the ComplianceTeam to the reviewer list for every pull request; it does not enforce any minimum approval threshold, so the PR can still be merged even if none of them approve. While this improves visibility, it never blocks a merge based on the team's missing sign-off, because it is a notification mechanism rather than a gating control. Only combining an explicit minimum reviewer count with 'Required reviewers' enforces the necessary approvals.
About these practice questions
Courseiva creates original exam-style practice questions with explanations and wrong-answer analysis. It does not publish real exam questions, exam dumps, or protected exam content. Learn why practice questions differ from exam dumps →
Last reviewed: Jun 25, 2026
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.
Question Discussion
Share a tip, memory trick, or ask about the reasoning behind this question. Do not post real exam questions, leaked content, braindumps, or copyrighted exam material. Comments are moderated and may be removed without notice.
Sign in to join the discussion.