HashiCorp Updated Terraform-Associate-004 Exam Questions and Answers by asa

Rationale for Correct Answer: A private registry in HCP Terraform is designed to publish and share modules within an organization (with org access controls), rather than publicly. That supports internal reuse while keeping module content and usage confined to authorized users in the org.

Analysis of Incorrect Options (Distractors):

B (False): Incorrect—confidential/internal distribution is a primary purpose of private registries.

Key Concept: Public vs private module registries and organizational access control.

All of the statements are true of Terraform providers. Terraform providers are plugins that enable Terraform to interact with various APIs and services1. Anyone can write a Terraform provider, either as an individual or as part of a community2. HashiCorp maintains some providers, such as the AWS, Azure, and Google Cloud providers3. Cloud providers and infrastructure vendors can also write, maintain, or collaborate on Terraform providers, such as the VMware, Oracle, and Alibaba Cloud providers. References =

•1: Providers - Configuration Language | Terraform | HashiCorp Developer

•2: Plugin Development - How Terraform Works With Plugins | Terraform | HashiCorp Developer

•3: Terraform Registry

•: Terraform Registry

Purpose of Refresh-Only Mode: Running Terraform inrefresh-only modeupdates Terraform ' s state file with the current state of resources in your infrastructure without making changes to the resources themselves.

Context of Terraform Import: When usingterraform import, you’re adding existing resources to the state file, and running Terraform in refresh-only mode before this operation can ensure that any initial configuration syncs precisely with the actual state.

For more on refresh-only mode in relation to terraform import, refer to Terraform ' s import documentation.

This is how Terraform chooses which version of the provider to use, when you add a new resource to an existing Terraform configuration, but do not update the version constraint in the configuration. The lock file records the exact version of each provider that was installed in your working directory, and ensures that Terraform will always use the same provider versions until you run terraform init -upgrade to update them.