What is a typical use-case for a private module registry in Terraform Cloud?

What is a typical use-case for a private module registry in Terraform Cloud?

• A. Store private modules for reuse within the organization
• B. Public modules only
• C. It is used for storing state
• D. It is used as a log storage

Answer: (A)

Private module registries in Terraform Cloud are for storing internal modules so teams can reuse them across projects. The typical use-case is to publish internal modules and maintain a centralized, versioned catalog that enables discovery, access control, and consistent infrastructure patterns across the organization. By using a private registry, you can share modules like networking, IAM configurations, or compliance patterns while ensuring teams pin to approved versions. This is different from public modules, which live in the public registry, and it is not used to store Terraform state or logs, which are kept in the backend and run history.

Private module registries in Terraform Cloud are for storing internal modules so teams can reuse them across projects. The typical use-case is to publish internal modules and maintain a centralized, versioned catalog that enables discovery, access control, and consistent infrastructure patterns across the organization. By using a private registry, you can share modules like networking, IAM configurations, or compliance patterns while ensuring teams pin to approved versions. This is different from public modules, which live in the public registry, and it is not used to store Terraform state or logs, which are kept in the backend and run history.