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.