Monorepo vs Multi-Repo: Three Benefits Tested on AZ-400
Which THREE are benefits of using a monorepo with Azure Repos and CI/CD pipelines?
Quick Answer
A monorepo's biggest wins with Azure Repos and CI/CD are atomic commits across components — one commit can touch multiple services and land together — plus easier code sharing between teams without separate package feeds, and simplified dependency management since everything resolves against the same working tree instead of coordinating versions across repos.
⚠ Common exam trap
Watch out — candidates often confuse the benefits of a monorepo with those of a multi-repo setup, assuming that a monorepo inherently improves build times or permissions granularity, when in reality it often worsens both without specific pipeline optimizations like sparse checkout or path-based triggers.
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 across projects
Option C is correct because a monorepo places all projects in a single repository, so shared libraries, utilities, and interfaces can be referenced directly rather than published and consumed as versioned packages across multiple repos. Option D is correct because dependencies between components are resolved from one consistent source tree, avoiding version-skew and cross-repo package coordination that complicates dependency management. Option E is correct because a single commit can change multiple components together, so a cross-component change lands atomically and CI/CD can validate the whole change set in one pipeline run. Option A is not a benefit of a monorepo; granular repository-level permissions are actually harder because everything lives in one repo, and Azure Repos permissions are typically applied at repo, branch, or path level rather than per project. Option B is not a benefit either, since a monorepo is a larger codebase and builds are not inherently faster; faster builds usually require path filters, incremental builds, or pipeline caching rather than resulting from the monorepo itself.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Granular repository-level permissions
Why it's wrong here
Permissions in Azure Repos are granted at repository, branch, and path level, so a monorepo cannot isolate one team's code from another's within the same repository. It is tempting because granular access control is a genuine benefit of many small repositories, where each team owns a separate repo.
- ✗
Faster build times due to smaller codebase
Why it's wrong here
A monorepo holds every service's code together, so a full pipeline build compiles the entire repository rather than one project, making builds slower, not faster. It is tempting because splitting into many small repos does shrink each individual build; that benefit belongs to polyrepo setups, not monorepos.
- ✓
Easier code sharing across projects
Why this is correct
A monorepo lets several projects import shared libraries directly from one repository, so a change to a common module is immediately visible to every consumer. This satisfies the stem's code-sharing benefit, since Azure Pipelines can trigger builds across affected projects without cross-repository package publishing or version pinning.
- ✓
Simplified dependency management
Why this is correct
A monorepo centralises shared libraries, so a single version serves every project and pipeline, eliminating cross-repo version drift. This directly satisfies the dependency-management benefit: Azure Pipelines can build once and fan out, rather than reconciling duplicated package references across separate repositories.
- ✓
Atomic cross-component commits
Why this is correct
Atomic cross-component commits let a single pull request update several projects together, so the pipeline builds and validates them as one consistent revision. This satisfies the stem's monorepo benefit: interdependent components stay version-aligned, avoiding the broken-build and dependency-drift problems that split repositories introduce during coordinated changes.
Visual reference
Go deeper
Related to this question
Learn chapter
Managing Infrastructure as Code Using Azure
Key term
Pipeline
A pipeline is an automated series of steps that takes code from development to production, ensuring quality and speed.
Key term
Azure Repos
Azure Repos is a set of version control tools that allow teams to manage their source code, track changes, and collaborate on software projects using Git or Team Foundation Version Control (TFVC) within the Microsoft Azure ecosystem.
About these practice questions
One of 696 original AZ-400 practice questions on Courseiva, each with a full explanation and wrong-answer analysis — not exam dumps or protected exam content. Learn why practice questions differ from exam dumps →
Same concept, more angles
1 more way this is tested on AZ-400
These questions test the same concept from different angles. Work through them to make sure you can recognise it however the exam phrases it.
Variation 1. Which TWO are valid reasons to use a monorepo?
easy- A.Smaller clone size compared to multiple repositories.
- ✓ B.Simplifies code sharing and reuse across multiple projects.
- C.Allows independent CI/CD pipelines for each project.
- D.Improves security by isolating each project.
- ✓ E.Simplifies dependency management and versioning.
Why B: A monorepo centralizes all code in a single repository, making it straightforward to share common libraries, utilities, and components across multiple projects without needing separate package feeds or submodule references. Option E is correct because with all projects in one repo, dependency versions are unified and managed in a single set of manifest files (e.g., package.json, requirements.txt), eliminating cross-repo version drift and simplifying coordinated updates.
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.