Courseiva
Configure processes and communicationshardMultiple SelectObjective-mapped

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

A monorepo enables easier code sharing across projects by allowing multiple teams to reference the same source files, libraries, and modules without needing separate package feeds or cross-repo synchronization. In Azure Repos, this means you can use common build artifacts and shared code directly within the same repository, reducing duplication and simplifying collaboration.

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

    Monorepos often have less granular permissions at the repo level.

  • Faster build times due to smaller codebase

    Why it's wrong here

    Monorepos are larger, so builds can be slower.

  • Easier code sharing across projects

    Why this is correct

    Shared libraries are in the same repo.

  • Simplified dependency management

    Why this is correct

    All dependencies are in one repo, making it easier to manage.

  • Atomic cross-component commits

    Why this is correct

    Changes to multiple components can be committed together.

Go deeper

Related to this question

About these practice questions

One of 823 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 →

How Courseiva writes practice questions · Editorial policy

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.