- A
Allow direct pushes to main branch for senior developers
Why wrong: Direct pushes skip reviews and can cause issues.
- B
Require a minimum number of reviewers and enforce a squash merge strategy
Squash merges keep history linear and reviews ensure quality.
- C
Create release branches for each production deployment
Why wrong: Release branches are not typical in trunk-based development.
- D
Require all merges to be fast-forward only
Why wrong: Fast-forward only can be restrictive and is not a core trunk-based practice.
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. Match the stated requirement to the specific cloud service, access model, or configuration option — many options are valid in isolation but not for this scenario. 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 organization is adopting a trunk-based development strategy with short-lived feature branches. Which branch policy should you enforce to ensure that code is integrated frequently and conflicts are minimized?
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
Require a minimum number of reviewers and enforce a squash merge strategy
In a trunk-based development strategy with short-lived feature branches, the goal is to integrate code frequently and minimize merge conflicts. Requiring a minimum number of reviewers ensures code quality and team awareness, while enforcing a squash merge strategy collapses all feature branch commits into a single commit on the main branch, keeping the history linear and clean. This approach reduces the risk of complex merge conflicts and supports continuous integration by encouraging small, frequent merges.
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.
- ✗
Allow direct pushes to main branch for senior developers
Why it's wrong here
Direct pushes skip reviews and can cause issues.
- ✓
Require a minimum number of reviewers and enforce a squash merge strategy
Why this is correct
Squash merges keep history linear and reviews ensure quality.
Related concept
Read the scenario before looking for a memorised answer.
- ✗
Create release branches for each production deployment
Why it's wrong here
Release branches are not typical in trunk-based development.
- ✗
Require all merges to be fast-forward only
Why it's wrong here
Fast-forward only can be restrictive and is not a core trunk-based practice.
Common exam traps
Common exam trap: answer the scenario, not the keyword
The trap here is that candidates often confuse trunk-based development with GitFlow and choose option C (release branches), or they mistakenly think fast-forward-only merges (option D) are required for trunk-based strategies, when in fact squash merges are the recommended approach to maintain a clean, linear history.
Detailed technical explanation
How to think about this question
Under the hood, a squash merge in Azure Repos or GitHub creates a new commit on the target branch that combines all changes from the source branch, effectively rewriting history to avoid a tangled graph. This is critical in trunk-based development because it keeps the main branch's commit history linear and easy to bisect for debugging, while still allowing developers to work with granular commits on their feature branches. In practice, this policy also prevents merge commits that can clutter the log and complicate rollbacks, especially when teams integrate multiple times per day.
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: Require a minimum number of reviewers and enforce a squash merge strategy — In a trunk-based development strategy with short-lived feature branches, the goal is to integrate code frequently and minimize merge conflicts. Requiring a minimum number of reviewers ensures code quality and team awareness, while enforcing a squash merge strategy collapses all feature branch commits into a single commit on the main branch, keeping the history linear and clean. This approach reduces the risk of complex merge conflicts and supports continuous integration by encouraging small, frequent merges.
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 →
Keep practising
More AZ-400 practice questions
- You have a multi-stage YAML pipeline that deploys to a Linux-based Azure App Service. The pipeline uses a 'Deploy to Azu…
- A development team uses a forking workflow in Azure Repos. They want to ensure that only specific users can create forks…
- A team is migrating from TFVC to Git. They have a large codebase with many branches. What is the recommended approach to…
- A development team is transitioning from a centralized version control system to Git in Azure Repos. The team lead wants…
- A team uses Azure Boards to manage work items. They want to automatically update the state of a work item when a related…
- Which THREE are benefits of using a monorepo vs multiple repositories?
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.