When organizing module sources, which statement best describes a private module registry in Terraform Cloud/Enterprise?

When organizing module sources, which statement best describes a private module registry in Terraform Cloud/Enterprise?

• 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 in Terraform Cloud/Enterprise is a built-in, centralized store within your organization that hosts and versions modules for repeatable reuse, with governance and access controls. It offers versioning, discoverability, and secure sharing across teams, which a generic git repository or a subfolder in a workspace does not provide. It’s also distinct from the public Terraform Module Registry, which is open to everyone and not restricted to your organization. Modules published to the private registry are referenced through the organization’s registry path, enabling consistent, versioned use across workspaces.

A private module registry in Terraform Cloud/Enterprise is a built-in, centralized store within your organization that hosts and versions modules for repeatable reuse, with governance and access controls. It offers versioning, discoverability, and secure sharing across teams, which a generic git repository or a subfolder in a workspace does not provide. It’s also distinct from the public Terraform Module Registry, which is open to everyone and not restricted to your organization. Modules published to the private registry are referenced through the organization’s registry path, enabling consistent, versioned use across workspaces.