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

You do not need to use different Terraform commands depending on the cloud provider you use. Terraform commands are consistent across different providers, as they operate on the Terraform configuration files and state files, not on the provider APIs directly.

From Terraform CLI Overview:

" Terraform provides a consistent CLI workflow regardless of which cloud or service you’re managing. "

Thesame Terraform commandswork across all providers via plugins.

Rationale for Correct Answer: A parent/root module can only read values from a child module if the child module exports them via an output block. The error indicates vnet_id is not an exported output from module.my_network. Defining output " vnet_id " { value = ... } inside the networking (child) module makes module.my_network.vnet_id valid.

Analysis of Incorrect Options (Distractors):

A: Incorrect—Terraform does not use module. < name > .outputs. < output > ; module outputs are referenced directly as module. < name > . < output > .

B: Incorrect—variables are inputs to a module, not values exported from it.

C: Incorrect—missing the module. prefix and still uses an invalid .outputs path.

Key Concept: Module outputs are the contract for exposing child module values to the root/parent.

Detailed Explanation:

Rationale for Correct Answer:In Terraform, an input variable is “optional” if it has a default value. Setting default = " " allows callers to omit the variable entirely, while still producing a known value (empty string) that you can conditionally include/exclude when building tags. This directly supports reusable module/config design: sensible defaults make variables optional.

Analysis of Incorrect Options (Distractors):

B: Incorrect. optional = true is not valid syntax for variable blocks in Terraform.

C: Incorrect. optional(string) is used for optional attributes in object type constraints, not as a top-level variable type declaration in this way for making a variable optional.

D: Incorrect. type = default is not valid Terraform syntax.

Key Concept:A variable becomes optional by providing a default value.

In Terraform, the correct way to reference a resource attribute is:

pgsql

CopyEdit

resource_type.resource_name.attribute

For example, if the resource block is:

hcl

CopyEdit

resource " kubernetes_namespace " " example " {

metadata {

name = " my-namespace "

}

}

To reference the name attribute, use:

pgsql

CopyEdit

kubernetes_namespace.example.name

Explanation of incorrect answers:

A (resource.kubernetes_namespace.example.name)– Incorrect. Terraform does not use the resource. prefix when referencing resources.

C (data.kubernetes.namespace.name)– Incorrect. This syntax is used fordata sources, not resources.

D (kubernetes_namespace.test.name)– Incorrect. The resource name is " example " , not " test " .

Official Terraform Documentation Reference:

Terraform Resource References