Monorepo vs multi-repo decision in Git - Practice Questions

Challenge - 5 Problems

🧠 Conceptual

intermediate

When to choose a monorepo over multiple repos?

Which scenario best justifies using a monorepo instead of multiple repositories?

A Several unrelated projects maintained by different teams with no shared dependencies.

B Multiple independent microservices that rarely change together.

C A large project with many small, tightly coupled components that share code frequently.

D A collection of open-source libraries maintained by different organizations.

💡 Hint

Think about how often code is shared and how closely components are related.

A monorepo works best when components are tightly coupled and share code often, making coordination easier.

🧠 Conceptual

intermediate

Main challenge of multi-repo approach

What is the biggest challenge when using multiple repositories for related projects?

A Managing consistent versioning and coordinating changes across repos.

B Having too many files in a single repository.

C Slower cloning times due to large repository size.

D Difficulty in isolating unrelated projects.

💡 Hint

Consider what happens when changes affect multiple repositories.

Multi-repos require careful coordination to keep versions compatible and changes synchronized.

🔀 Workflow

advanced

Git workflow complexity in monorepos

In a large monorepo, what is a common workflow challenge when multiple teams work on different components?

A Conflicts in shared files and longer integration times due to many simultaneous changes.

B Inability to create branches for individual features.

C No way to run tests on specific components only.

D Lack of support for pull requests.

💡 Hint

Think about what happens when many people edit the same repository at once.

Monorepos can cause merge conflicts and slow integration because many changes happen in one place.

❓ Troubleshoot

advanced

Troubleshooting dependency issues in multi-repos

You have multiple repositories with interdependent projects. After updating a shared library in one repo, dependent repos fail to build. What is the most likely cause?

A The dependent repos have too many branches.

B Dependent repos are not updated to use the new library version.

C Git hooks are disabled in dependent repos.

D The shared library was deleted from the main repo.

💡 Hint

Consider how dependencies are managed across repositories.

Dependent repos must update their references to the new library version to build successfully.

✅ Best Practice

expert

Best practice for scaling monorepos

What is a recommended best practice to keep a large monorepo manageable as it grows?

A Avoid using any branching strategy to keep history simple.

B Merge all branches into main without reviews to speed up development.

C Store all binaries and build artifacts directly in the monorepo.

D Use tools to run tests and builds only on changed components to save time.

💡 Hint

Think about how to reduce unnecessary work when many components exist.

Running tests and builds only on changed parts helps keep CI fast and efficient in large monorepos.

Practice

1. Which of the following best describes a monorepo in Git?

easy

A. A repository used only for backups

B. Multiple repositories each containing one project

C. A repository that only stores documentation

D. A single repository containing multiple projects together

Solution

1. Step 1: Understand the definition of monorepo

   A monorepo is a single repository that holds multiple projects or components together in one place.

2. Step 2: Compare with other options

   The other options describe different repository setups or uses, not monorepos.

3. Final Answer:

   A single repository containing multiple projects together -> Option D

4. Quick Check:

   Monorepo = single repo for many projects [OK]

Hint: Monorepo means one repo for many projects [OK]

Common Mistakes:

• Confusing monorepo with multi-repo
• Thinking monorepo is only for documentation
• Assuming monorepo means backup repo

2. Which Git command is commonly used to clone a multi-repo project?

easy

A. git merge

B. git clone

C. git init

D. git push

Solution

1. Step 1: Identify the command to copy a repository locally

   The git clone command copies a remote repository to your local machine.

2. Step 2: Check other commands for correctness

   git merge combines branches, git init creates a new repo, and git push uploads changes.

3. Final Answer:

   git clone <repo-url> -> Option B

4. Quick Check:

   Clone = copy repo locally [OK]

Hint: Clone to copy repo locally, not merge or push [OK]

Common Mistakes:

• Using git merge to copy repo
• Confusing git init with cloning
• Trying to push before cloning

3. You have a monorepo with two projects: frontend and backend. You run git status inside the frontend folder after changing a file in backend. What will you see?

medium

A. Error message about folder mismatch

B. No changes detected because you are inside frontend folder

C. Changes detected for the backend file because monorepo tracks all files

D. Only staged changes shown

Solution

1. Step 1: Understand monorepo file tracking

   In a monorepo, Git tracks all files in the single repository regardless of folder location.

2. Step 2: Effect of running git status in a subfolder

   Running git status anywhere in the repo shows changes in the entire repo, including backend files.

3. Final Answer:

   Changes detected for the backend file because monorepo tracks all files -> Option C

4. Quick Check:

   Monorepo tracks all files, status shows all changes [OK]

Hint: Monorepo status shows all changes, no matter folder [OK]

Common Mistakes:

• Thinking git status is folder-limited
• Expecting error when running git status in subfolder
• Confusing staged changes with all changes

4. A team using multi-repos notices frequent conflicts when updating shared libraries. What is a likely cause?

medium

A. Lack of centralized codebase causes version mismatches

B. Using monorepo causes conflicts

C. Git does not support multiple repositories

D. Developers forgot to commit changes

Solution

1. Step 1: Analyze multi-repo challenges

   Multi-repos separate projects, so shared libraries can have different versions causing conflicts.

2. Step 2: Eliminate incorrect options

   Monorepo is not used here, Git supports multiple repos, and forgetting commits is unrelated to shared library conflicts.

3. Final Answer:

   Lack of centralized codebase causes version mismatches -> Option A

4. Quick Check:

   Multi-repo can cause version conflicts without central code [OK]

Hint: Multi-repo can cause version conflicts without central code [OK]

Common Mistakes:

• Blaming monorepo for multi-repo issues
• Thinking Git can't handle multiple repos
• Ignoring version mismatch as cause

5. Your team has 5 small independent projects with different release schedules and teams. Which repo strategy fits best and why?

hard

A. Multi-repo, because it allows independent work and releases

B. Multi-repo, because it merges all projects into one

C. Monorepo, because it forces all teams to work together

D. Monorepo, because it simplifies dependency management

Solution

1. Step 1: Analyze project independence and release schedules

   Independent projects with different schedules benefit from separate repos to avoid interference.

2. Step 2: Match repo strategy to team needs

   Multi-repo allows teams to work independently and release on their own timelines.

3. Final Answer:

   Multi-repo, because it allows independent work and releases -> Option A

4. Quick Check:

   Independent projects = multi-repo best fit [OK]

Hint: Independent projects with different schedules use multi-repo [OK]

Common Mistakes:

• Choosing monorepo for independent projects
• Thinking monorepo forces independence
• Confusing multi-repo with merging projects