nerdexam
HashiCorp

TERRAFORM-ASSOCIATE-004 · Question #49

Which method for sharing Terraform configurations fulfills the following criteria: 1. Keeps the configurations confidential within your organization 2. Support Terraform's semantic version constrains

The correct answer is C. Terraform Cloud private registry. Terraform Cloud's private registry satisfies all three criteria: (1) it is private and accessible only to members of your organization, keeping configurations confidential; (2) it supports semantic versioning constraints (e.g., '~> 1.0'), so consumers can pin or constrain module

Submitted by carter_n· Apr 18, 2026Understand Terraform Cloud and Enterprise Capabilities

Question

Which method for sharing Terraform configurations fulfills the following criteria: 1. Keeps the configurations confidential within your organization 2. Support Terraform's semantic version constrains 3. Provides a browsable directory

Options

  • ASubfolder within a workspace
  • BGeneric git repository
  • CTerraform Cloud private registry
  • DPublic Terraform module registry

How the community answered

(24 responses)
  • A
    4% (1)
  • B
    4% (1)
  • C
    92% (22)

Explanation

Terraform Cloud's private registry satisfies all three criteria: (1) it is private and accessible only to members of your organization, keeping configurations confidential; (2) it supports semantic versioning constraints (e.g., '~> 1.0'), so consumers can pin or constrain module versions; and (3) it provides a browsable UI where team members can discover and explore available modules. A generic git repo (option B) supports versioning via tags but lacks a browsable directory and access controls. A subfolder in a workspace (option A) has none of these properties. The public registry (option D) is not confidential.

Topics

#Terraform Cloud#Private Registry#Module Sharing#Module Versioning

Community Discussion

No community discussion yet for this question.

Full TERRAFORM-ASSOCIATE-004 Practice