AZ-400 Design and implement source control Practice Question
A development team uses Azure Repos Git. They need to ensure that every commit pushed to the main branch includes a valid work item link, but they do not want to block developers from pushing to feature branches. What should they configure?
⚠ Common exam trap
A common mix-up: candidates confuse approval-related policies such as minimum reviewers or required reviewers with the linked work items policy that specifically validates work item association.
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
✓
A branch policy on main that checks for linked work items.
The linked work items branch policy on main enforces that commits or pull requests targeting main are associated with at least one work item, while leaving feature branches unrestricted. Reviewer count, commit signing, and required reviewer policies address different concerns and do not enforce work item linkage.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
A required reviewer policy on main that assigns a specific team.
Why it's wrong here
A required reviewer policy forces designated reviewers to approve pull requests targeting main. It does not inspect commits for work item links, so a pull request without any linked work item could still be completed once the reviewers approve, failing the stated requirement.
- ✓
A branch policy on main that checks for linked work items.
Why this is correct
The linked work items policy on the main branch requires that every commit or pull request targeting main be associated with at least one Azure Boards work item. Feature branches remain unaffected because the policy is scoped only to main, so developers can push freely to feature branches while main stays compliant.
- ✗
A repository-level policy that requires all commits to be signed.
Why it's wrong here
Commit signing verifies the cryptographic identity of the author, not the presence of work item links. Enabling it would add signing requirements for all branches or the repository, which is unrelated to the work item association requirement and would not enforce the desired link on main.
- ✗
A branch policy on main that requires a minimum number of reviewers.
Why it's wrong here
A minimum reviewer count policy controls how many approvals a pull request needs, not whether commits contain work item links. It would not enforce the presence of linked work items on commits pushed to main, and it would not prevent direct pushes from bypassing the requirement if the policy is not combined with other controls.
Go deeper
Related to this question
Learn chapter
Implementing Work Item Management and Agile Planning
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.
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 696-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 →
JA
Written and reviewed by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
Last reviewed September 2026 · checked against the official Microsoft exam blueprint
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.