HashiCorp Terraform-Associate-004 Exam Dumps

Detailed

Rationale for Correct Answe r: The configuration uses a data block, not a resource block. In Terraform, a data block reads information about existing infrastructure from a provider. It does not create, update, or delete infrastructure. This data source searches for an existing AWS EC2 instance with the tag Name = web.

Analysis of Incorrect Options (Distractors):

A . True. Incorrect. A new AWS instance would be created using a resource block such as resource 'aws_instance' 'web' { ... }, not a data source.

Key Concept: Terraform data blocks are used to query existing infrastructure, while resource blocks manage infrastructure lifecycle.

This is the type of block that is used to construct a collection of nested configuration blocks, by using afor_eachargument to iterate over a collection value and generate a nested block for each element. For example, you can use a dynamic block to create multiple ingress rules for a security group resource.

This is the backend that the Terraform CLI uses by default, unless you specify a different backend in your configuration. The local backend stores the state file in a local file namedterraform.tfstate, which can be used to track and manage the state of your infrastructure.

In Terraform, theresource nameis the second argument in the resource block.

The structure of a resource block is:

resource 'provider_resource_type' 'resource_name' {

# Configuration settings

}

Here, the provider type isgoogle_compute_instance, and theresource nameis 'main'.

The name 'test' is simply the value assigned to the name attribute, which is unrelated to the Terraform resource name.

'google' and 'compute_instance' are part of the provider and resource type, not the resource name.

Official Terraform Documentation Reference:

Terraform Resource Documentation

Rationale for Correct Answer (C):

Best practice is to avoid hardcoding sensitive credentials in Terraform configurations or storing them in version control. Instead, credentials should be managed via environment variables, CLI authentication helpers, or secret managers (e.g., Vault).

Analysis of Incorrect Options:

A . Shared server: Not secure, introduces single point of failure and risk.

B . Storing credentials in config files: A major security risk, especially if pushed to version control.

D . None of the above: Incorrect, because option C is a valid and recommended approach.

Key Concept:

Security best practices in Terraform dictate that credentials should be externalized from Terraform code.

Terraform Exam Objective -- Navigate Terraform State and Backends.