Monorepo vs multi-repo for Terraform - Practice Questions

Challenge - 5 Problems

❓ Architecture

intermediate

Benefits of a Monorepo for Terraform

Which of the following is a key benefit of using a monorepo approach for managing Terraform code?

A Easier to share and reuse modules across projects without duplication

B Complete isolation of environments with no shared state

C Allows each team to use different Terraform versions without conflict

D Simplifies access control by restricting repository permissions per environment

💡 Hint

Think about how code reuse and consistency are affected when all Terraform code is in one place.

A monorepo centralizes Terraform code, making it easier to share modules and maintain consistency. Options B, C, and D describe benefits more aligned with multi-repo setups.

✅ Best Practice

intermediate

Challenges of Multi-Repo Terraform Management

What is a common challenge when using a multi-repo strategy for Terraform code?

A Increased risk of accidental overwrites in a single shared state file

B Difficulty in coordinating changes across multiple repositories leading to drift

C Harder to enforce different access controls per environment

D Limited ability to use Terraform workspaces for environment separation

💡 Hint

Consider how managing many repositories affects synchronization and consistency.

Multi-repo setups can cause coordination issues because changes spread across repos may not be synchronized, causing configuration drift. Options A, B, and C are incorrect.

❓ security

advanced

Access Control in Monorepo vs Multi-Repo

Which statement best describes access control differences between monorepo and multi-repo Terraform setups?

A Multi-repo allows fine-grained access control per environment, while monorepo requires broader permissions

B Monorepo enforces stricter access control by default compared to multi-repo

C Both monorepo and multi-repo require identical access control configurations

D Monorepo prevents unauthorized changes by isolating state files per environment

💡 Hint

Think about how repository boundaries affect who can change what.

Multi-repo setups let teams restrict access to specific repositories, enabling environment-level control. Monorepos usually require broader permissions since all code is together. Options A, B, and D are incorrect or misleading.

❓ service_behavior

advanced

Terraform State Management in Monorepo vs Multi-Repo

How does Terraform state management typically differ between monorepo and multi-repo approaches?

A Multi-repo always uses a single shared state backend for all environments

B Multi-repo cannot use remote state backends

C Monorepo requires manual state file merging across environments

D Monorepo often uses a single shared state backend, while multi-repo uses separate state backends per repo

💡 Hint

Consider how state files are organized and shared in each approach.

Monorepos often centralize state management, using shared backends for easier coordination. Multi-repos typically isolate state per repo to avoid conflicts. Options A, C, and D are incorrect.

🧠 Conceptual

expert

Choosing Between Monorepo and Multi-Repo for Large Terraform Projects

For a large organization with multiple independent teams managing different cloud environments, which approach is generally more scalable and why?

A Monorepo, because it forces all teams to share the same codebase and state, reducing complexity

B Monorepo, because it eliminates the need for version control systems

C Multi-repo, because it allows teams to work independently with isolated codebases and tailored access controls

D Multi-repo, because it requires all teams to use the same Terraform version and modules

💡 Hint

Think about team independence, access control, and codebase isolation.

Multi-repo setups scale better for large organizations by isolating code and permissions per team, reducing conflicts. Monorepos can become complex and harder to manage at scale. Options B, C, and D are incorrect or misleading.