- A
Set the main branch to require all merges to come from pull requests, and for develop, allow direct pushes.
Why wrong: This does not handle hotfix merges to both branches.
- B
Use branch policies on main and develop that allow only certain source branches to merge, using branch naming conventions.
Branch policies can restrict source branches via naming patterns.
- C
Configure a global policy that requires all branches to have a minimum number of reviewers.
Why wrong: Global policies are not granular enough.
- D
Use a build validation policy to check the branch name and reject merges that do not follow the pattern.
Why wrong: Build validation runs after merge attempt, not an ideal enforcement.
AZ-400 Practice Question: Design and implement a source control strategy
This AZ-400 practice question tests your understanding of design and implement a source control strategy. This is a configuration task: choose the command set that satisfies every stated requirement. Small differences — like 'secret' vs 'password' or 'transport input ssh' vs 'all' — change whether the answer is correct. After answering, compare your reasoning against the explanation and wrong-answer breakdown below. Once you have made your selection, read the full explanation to reinforce the concept and understand why each distractor is designed to mislead on exam day.
Your team is adopting GitFlow with a main and develop branch. You need to ensure that hotfix branches are merged into both main and develop, but feature branches only into develop. What branch policy configuration should you implement?
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
Use branch policies on main and develop that allow only certain source branches to merge, using branch naming conventions.
Option B is correct because Azure Repos branch policies allow you to restrict which source branches can merge into a target branch using branch naming conventions. By configuring policies on `main` and `develop` that only permit merges from specific source patterns (e.g., `hotfix/*` for `main` and `develop`, and `feature/*` only for `develop`), you enforce the GitFlow workflow without relying on manual oversight or build validation logic.
Key principle: Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
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 the main branch to require all merges to come from pull requests, and for develop, allow direct pushes.
Why it's wrong here
This does not handle hotfix merges to both branches.
- ✓
Use branch policies on main and develop that allow only certain source branches to merge, using branch naming conventions.
Why this is correct
Branch policies can restrict source branches via naming patterns.
Related concept
Read the scenario before looking for a memorised answer.
- ✗
Configure a global policy that requires all branches to have a minimum number of reviewers.
Why it's wrong here
Global policies are not granular enough.
- ✗
Use a build validation policy to check the branch name and reject merges that do not follow the pattern.
Why it's wrong here
Build validation runs after merge attempt, not an ideal enforcement.
Common exam traps
Common exam trap: answer the scenario, not the keyword
The trap here is that candidates confuse build validation policies (which run after PR creation) with branch-level source branch restrictions (which prevent PR creation entirely), leading them to choose Option D despite it being a reactive rather than proactive control.
Detailed technical explanation
How to think about this question
Azure Repos branch policies use the 'Allow only specific source branches to merge' setting under the branch policy configuration, which evaluates the source branch name against a set of glob patterns (e.g., `feature/*`, `hotfix/*`). This policy is enforced at pull request creation time, preventing unauthorized merges before any build or review process begins. In a real-world scenario, this ensures that a developer cannot accidentally merge a feature branch into `main` even if they create a pull request, maintaining the integrity of the release branch.
KKey Concepts to Remember
- Read the scenario before looking for a memorised answer.
- Find the constraint that changes the correct option.
- Eliminate answers that are true in general but not in this case.
TExam Day Tips
- Watch for words such as best, first, most likely and least administrative effort.
- Review why wrong options are wrong, not only why the correct option is correct.
Key takeaway
Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
Real-world example
How this comes up in practice
A cloud solutions architect for a retail company is evaluating services for a new workload. The correct answer here reflects best practice for the specific scenario described — not a general cloud recommendation. Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option. Cloud exam questions reward reading the constraint carefully: the same technology can be right or wrong depending on the use case.
What to study next
Got this wrong? Here's your next step.
Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.
- →
Design and implement a source control strategy — study guide chapter
Learn the concepts, then practise the questions
- →
Design and implement a source control strategy practice questions
Targeted practice on this topic area only
- →
All AZ-400 questions
913 questions across all exam domains
- →
Microsoft Azure DevOps Engineer Expert AZ-400 study guide
Full concept coverage aligned to exam objectives
- →
AZ-400 practice test guide
How to use practice tests most effectively before exam day
Related practice questions
Related AZ-400 practice-question pages
Use these pages to review the topic behind this question. This is how one missed question becomes focused revision.
Configure processes and communications practice questions
Practise AZ-400 questions linked to Configure processes and communications.
Design and implement source control practice questions
Practise AZ-400 questions linked to Design and implement source control.
Design and implement build and release pipelines practice questions
Practise AZ-400 questions linked to Design and implement build and release pipelines.
Develop a security and compliance plan practice questions
Practise AZ-400 questions linked to Develop a security and compliance plan.
Implement an instrumentation strategy practice questions
Practise AZ-400 questions linked to Implement an instrumentation strategy.
Design and implement a DevOps infrastructure practice questions
Practise AZ-400 questions linked to Design and implement a DevOps infrastructure.
Design and implement a source control strategy practice questions
Practise AZ-400 questions linked to Design and implement a source control strategy.
AZ-400 fundamentals practice questions
Practise AZ-400 questions linked to AZ-400 fundamentals.
AZ-400 scenario practice questions
Practise AZ-400 questions linked to AZ-400 scenario.
AZ-400 troubleshooting practice questions
Practise AZ-400 questions linked to AZ-400 troubleshooting.
Practice this exam
Start a free AZ-400 practice session
Short sessions build daily habit. Longer sessions build exam-day stamina. Try a timed session to simulate real conditions.
FAQ
Questions learners often ask
What does this AZ-400 question test?
Design and implement a source control strategy — This question tests Design and implement a source control strategy — Read the scenario before looking for a memorised answer..
What is the correct answer to this question?
The correct answer is: Use branch policies on main and develop that allow only certain source branches to merge, using branch naming conventions. — Option B is correct because Azure Repos branch policies allow you to restrict which source branches can merge into a target branch using branch naming conventions. By configuring policies on `main` and `develop` that only permit merges from specific source patterns (e.g., `hotfix/*` for `main` and `develop`, and `feature/*` only for `develop`), you enforce the GitFlow workflow without relying on manual oversight or build validation logic.
What should I do if I get this AZ-400 question wrong?
Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.
What is the key concept behind this question?
Read the scenario before looking for a memorised answer.
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.