AZ-400 Configure processes and communications Practice Question
A development team wants to ensure that all code changes are reviewed by at least two senior developers before merging into the main branch. They use Azure Repos. What should they configure?
⚠ Common exam trap
Many exam-takers confuse build validation policies (which ensure code compiles) with reviewer policies (which ensure human oversight), leading them to select option A instead of C.
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
✓
Configure a branch policy requiring a minimum number of reviewers.
Azure Repos branch policies allow you to enforce a minimum number of reviewers on pull requests. By setting the 'Minimum number of reviewers' policy to 2, the team ensures that at least two senior developers must approve any code change before it can be merged into the main branch. This directly meets the requirement without involving build validation, release pipelines, or external function calls.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Enable the build validation policy on the branch.
Why it's wrong here
Enabling build validation on a branch policy triggers a CI build for each pull request and blocks merge if the build fails, but it validates compilation and tests only; it does not enforce any human review or reviewer count requirement.
- ✗
Set up a release pipeline with gated deployments.
Why it's wrong here
A release pipeline with gated deployments controls when a build artifact is deployed to environments (e.g., waiting for manual approval or scheduled gates); it operates post-merge and cannot enforce pull request review policies on the source branch.
- ✓
Configure a branch policy requiring a minimum number of reviewers.
Why this is correct
Branch policies in Azure Repos can enforce a minimum number of reviewers on pull requests, blocking completion until the required number of approved reviews is met; this directly ensures that every code change receives the mandated human review before merging.
- ✗
Add a status check policy using Azure Functions.
Why it's wrong here
A status check policy using Azure Functions can call external services or custom logic to validate pull request metadata or external conditions, but it cannot natively enforce a specific reviewer count; branch policies already provide a built-in, supported setting for minimum reviewers.
Go deeper
Related to this question
Learn chapter
Introduction to DevOps and Azure DevOps
Key term
Azure Repos
Azure Repos is a set of version control tools that allow teams to manage their source code, track changes, and collaborate on software projects using Git or Team Foundation Version Control (TFVC) within the Microsoft Azure ecosystem.
Key term
Branch
A branch is a pointer to a specific commit in a version control system that allows you to work on features or fixes in isolation from the main codebase.
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.