AZ-400 Design and implement source control Practice Question
Which THREE are benefits of using a monorepo vs multiple repositories?
⚠ Common exam trap
Candidates often confuse 'reduced configuration drift' (Option B) with the benefits of centralized configuration management, but in a monorepo, configuration drift can still occur if teams modify shared files inconsistently, and the exam expects you to recognize that this is not an inherent benefit.
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
✓
Easier code sharing and refactoring across projects
A monorepo enables easier code sharing and refactoring across projects by allowing all code to reside in a single repository. This eliminates the need for cross-repository package publishing or versioning, as shared libraries can be directly referenced and refactored atomically across all dependent projects within the same commit.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✓
Easier code sharing and refactoring across projects
Why this is correct
Because all code resides in a single repository, projects can directly import shared libraries without separately publishing and versioning them. This enables large-scale refactoring, such as changing an API signature, to be done in one atomic change that immediately affects all consuming projects, greatly simplifying coordination.
- ✗
Reduced risk of configuration drift
Why it's wrong here
While a monorepo can centralize CI/CD configuration, it does not inherently prevent configuration drift since different projects may still need distinct tooling, versions, or pipeline definitions. Multiple repositories can also enforce configuration consistency through templates and policies, so this is not a guaranteed benefit of a monorepo.
- ✓
Simplified dependency management across projects
Why this is correct
In a monorepo, all projects share a single dependency tree or lockfile, making it easier to resolve cross-project dependencies and ensure that compatible versions are used everywhere. This removes the need to publish internal packages to a registry and manually update version references across separate repos, reducing version mismatch issues.
- ✗
Faster clone times due to smaller repository size
Why it's wrong here
Monorepos are typically much larger than individual repositories because they contain the history and files of all projects, so cloning them generally takes longer, not faster. Even with sparse checkout or shallow clone techniques, the default full clone is slower, making this statement incorrect.
- ✓
Atomic commits that span multiple components
Why this is correct
Because all components live in the same repository, a developer can make one commit that includes changes across multiple project boundaries, libraries, and configuration files simultaneously. This atomicity guarantees that a logically related set of changes is versioned and built together, avoiding the cross-repository coordination and multi-commit rollouts required with separate repos.
Go deeper
Related to this question
About these practice questions
Courseiva writes every AZ-400 question from scratch — 823 in total, each with an explanation and a wrong-answer breakdown. None are copied from real exams or dumps. Learn why practice questions differ from exam dumps →
JA
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.