- A
Configure sparse checkout so developers can clone only the directories they need.
Sparse checkout allows cloning a subset of files, dramatically reducing clone time and disk usage.
- B
Instruct developers to use a shallow clone with depth 1 to reduce clone time.
Why wrong: Shallow clone reduces history but still downloads all files, so the 5 GB download remains.
- C
Move all large binary files to Git LFS to reduce repository size.
Why wrong: Git LFS is already in use; this does not address the monorepo size for code files.
- D
Split the monorepo into multiple repositories and use submodules to aggregate them.
Why wrong: Submodules add overhead and complexity; developers would need to initialize submodules separately.
AZ-400 Design and implement source control Practice Question
This AZ-400 practice question tests your understanding of design and implement source control. 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 team manages a large monorepo in Azure Repos containing multiple projects. Developers frequently complain that cloning the entire repository takes too long and that they only need a subset of the code. The team uses Git LFS for large binary files. The repository currently has 50,000 commits and is 5 GB in size. You want to improve clone performance without sacrificing the ability to contribute to any part of the repo. What should you do?
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 sparse checkout so developers can clone only the directories they need.
Sparse checkout allows developers to clone only the specific directories they need from the monorepo, significantly reducing the amount of data transferred and stored locally. Since the team already uses Git LFS for large binaries, the primary bottleneck is the sheer size of the full commit history and working tree. Sparse checkout, combined with a shallow clone if needed, directly addresses the complaint without breaking the ability to contribute to any part of the repo.
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.
- ✓
Configure sparse checkout so developers can clone only the directories they need.
Why this is correct
Sparse checkout allows cloning a subset of files, dramatically reducing clone time and disk usage.
Related concept
Read the scenario before looking for a memorised answer.
- ✗
Instruct developers to use a shallow clone with depth 1 to reduce clone time.
Why it's wrong here
Shallow clone reduces history but still downloads all files, so the 5 GB download remains.
- ✗
Move all large binary files to Git LFS to reduce repository size.
Why it's wrong here
Git LFS is already in use; this does not address the monorepo size for code files.
- ✗
Split the monorepo into multiple repositories and use submodules to aggregate them.
Why it's wrong here
Submodules add overhead and complexity; developers would need to initialize submodules separately.
Common exam traps
Common exam trap: answer the scenario, not the keyword
The trap here is that candidates often confuse sparse checkout with shallow clone, thinking that reducing commit history alone solves the problem, when in fact the working tree size is the primary bottleneck for developers who only need a subset of code.
Detailed technical explanation
How to think about this question
Sparse checkout works by configuring Git to only populate the working tree with specified paths after the initial clone, but the full object database is still downloaded unless combined with a shallow clone or blobless partial clone (e.g., `git clone --filter=blob:none`). In a monorepo with 50,000 commits, using `git sparse-checkout init --cone` in Git 2.25+ can drastically reduce checkout time and disk usage by limiting the working tree to a set of top-level directories. A real-world scenario is Microsoft's own use of sparse checkout in their large Azure DevOps monorepo to enable efficient developer workflows.
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 source control — study guide chapter
Learn the concepts, then practise the questions
- →
Design and implement source control 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 source control — This question tests Design and implement source control — Read the scenario before looking for a memorised answer..
What is the correct answer to this question?
The correct answer is: Configure sparse checkout so developers can clone only the directories they need. — Sparse checkout allows developers to clone only the specific directories they need from the monorepo, significantly reducing the amount of data transferred and stored locally. Since the team already uses Git LFS for large binaries, the primary bottleneck is the sheer size of the full commit history and working tree. Sparse checkout, combined with a shallow clone if needed, directly addresses the complaint without breaking the ability to contribute to any part of the repo.
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 11, 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.