Match each Azure Repos policy to its enforcement.
Drag a concept onto its matching description — or click a concept then click the description.
Ensures at least N reviewers approve
Requires PR to be associated with a work item
Requires all comments to be resolved before merge
Requires a successful pipeline run before merge
⚠ Common exam trap
Candidates often confuse the 'Require a minimum number of reviewers' policy with merge type restrictions, and 'Check for linked work items' with reviewer approval.
Answer choices
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: At least two reviewers must approve the pull request before it can be completed.
The correct matches are A, B, C, D. Policy A requires at least two reviewers. Policy B requires linked work items. Policy C requires a successful build. Policy D limits merge types. Policies E and F are incorrect because they swap the descriptions: E describes merge types but is labeled as reviewer count, and F describes reviewer count but is labeled as work item linking.
Answer analysis
For each option: why learners choose it and why it is or isn't the right answer here.
Require a minimum number of reviewers: At least two reviewers must approve the pull request before it can be completed.
Why this is correct
This policy enforces a minimum number of approved reviewers, not a merge-strategy constraint. In Azure Repos, you configure it under branch policies by setting 'Required reviewers' or 'Minimum number of reviewers' to a value of 2; the pull request remains locked and cannot be completed until that many distinct authorized reviewers approve it.
Check for linked work items: Pull requests must be linked to a work item associated with the commit.
Why this is correct
This policy ensures traceability by requiring each pull request to reference at least one linked work item that is associated with the commits being merged. Azure Repos blocks completion until a valid link exists, helping teams maintain audit trails and regulatory compliance for code changes.
Require successful build: A successful build in Azure Pipelines is required before the pull request can be completed.
Why this is correct
A successful build policy stops pull request completion until the latest source commit passes a specified Azure Pipelines build pipeline. You define the build pipeline in branch policies, and Azure Repos automatically queues and monitors the build; if it fails or is canceled, the pull request cannot be merged until a subsequent successful run.
Limit merge types: Specify which merge strategies are allowed, such as squash merge or rebase.
Why this is correct
This policy restricts which merge strategies developers may use when completing a pull request, such as allowing 'Squash merge' while disallowing 'Merge commit' or 'Rebase and merge'. It is configured in the 'Merge types' section of branch policies and enforces repository history conventions for all participants.
Require a minimum number of reviewers: Specify which merge strategies are allowed, such as squash merge or rebase.
Why it's wrong here
This statement is incorrect because it describes the 'Limit merge types' policy, which controls allowable merge strategies (e.g., squash merge or rebase), not the 'Require a minimum number of reviewers' policy. The latter deals solely with the number of required approvals before a pull request can be completed.
Check for linked work items: At least two reviewers must approve the pull request before it can be completed.
Why it's wrong here
This statement incorrectly attributes the reviewer-quorum rule to the 'Check for linked work items' policy. Requiring at least two approvals is enforced by the 'Minimum number of reviewers' branch policy, which blocks completion until the specified count of distinct authorized reviewers approve. By contrast, the 'Check for linked work items' policy mandates that the pull request reference a work item associated with the commits, ensuring traceability and compliance, and has no bearing on how many reviewers must approve.
Go deeper
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
Work item
A work item is a digital record in Azure DevOps that tracks a single unit of work, such as a task, bug, or user story, helping teams manage and monitor their progress.
About these practice questions
This AZ-400 question is part of Courseiva's 823-question bank — original exam-style content with full explanations and wrong-answer analysis, never real exam questions or exam dumps. Learn why practice questions differ from exam dumps →
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.