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

Rationale for Correct Answer: Locals are evaluated as expressions, and one local can reference another using local. < name > . This supports building up derived values cleanly:

locals {

env = " prod "

app_name = " api-${local.env} "

}

Analysis of Incorrect Options (Distractors):

B (False): Incorrect—Terraform explicitly supports local-to-local references.

Key Concept: Local values (locals) and expression references.

The description argument for Terraform variables and outputs is purely for documentation purposes and isnotstored in the Terraform state file.

Terraform variables and outputs can have descriptions for readability and clarity in .tf files.

However, these descriptions are not retained in the Terraform state file.

The state file only stores actual values and references needed for resource management, not metadata such as descriptions.

Official Terraform Documentation Reference:

Terraform Variables - HashiCorp Documentation

Terraform Outputs - HashiCorp Documentation

Rationale for Correct Answer: Data sources are referenced with: data. < TYPE > . < NAME > . < ATTRIBUTE > .For a vSphere datacenter data source, the correct reference to its id is:data.vsphere_datacenter. < name > .id.✅ Given the options, only A follows the correct data-source addressing pattern and includes the .id attribute.

Analysis of Incorrect Options (Distractors):

B: Incorrect—missing the data. prefix, so it looks like a managed resource reference.

C: Incorrect—missing the attribute (.id).

D: Incorrect—missing the data source type and name.

Key Concept: Correct HCL reference syntax for data sources.

The " version " attribute is optional when referencing a module from the Terraform Registry. If not specified, the latest version will be used, but it is often recommended to specify a version to ensure consistency across environments.