Which method for sharing Terraform configurations keeps them confidential within your organization, supports Terraform's semantic version constraints, and provides a browsable directory?

• A. Generic git repository
• B. Terraform Cloud/Terraform Enterprise private module registry
• C. Public Terraform Module Registry
• D. Subfolder within a workspace

Answer: (B)

A private module registry inside Terraform Cloud or Terraform Enterprise lets you share modules securely within your organization while staying aligned with Terraform’s versioning and providing an easy-to-navigate catalog. Confidentiality is achieved through access controls, so only authorized teammates can publish, view, or use the modules. It also supports semantic version constraints because modules published to the registry come with explicit version tags, and you can specify constraints like ~> 1.2 or >= 2.0 in your module source, with Terraform selecting a compatible version automatically. The browsable directory means teams can browse available modules, read their documentation, and see version histories directly in the registry UI, making discovery and governance straightforward.

Generic git repositories can be private but don’t offer a centralized, versioned module catalog or built-in constraints enforced by Terraform’s module system, and their browsing experience isn’t integrated as a registry. The public Terraform Module Registry isn’t confidential and isn’t suitable for internal sharing. Subfolders within a workspace aren’t a registry and lack a centralized, versioned, browsable catalog with controlled access.