Terraform-Associate-004 HashiCorp Exam Lab Questions

Detailed Explanation:Rationale for Correct Answer:When using multiple configurations of the same provider (e.g., AWS in different regions), Terraform requires the use of an aliasto distinguishalias argument:provider " aws " { alias = " west " region = " us-west-2 " }This allows resources to explicitly reference the aliased provider using:provider = aws.westThis is the standard Terraform pattern for multi-region or multi-account deployments.Analysis of Incorrect Options (Distractors):

Answer: Resource block only — Incorrect because it does not define how to use a different region; it relies on provider configuration.

Answer: provider " aws " " west " — Incorrect syntax; Terraform does not support naming providers this way. The correct method is using the alias argument.

Answer: provider " aws_west " — Incorrect because provider names must match actual providers (e.g., aws). You cannot invent a new provider name. Key Concept:Provider aliasing enables multiple configurations of the same provider (e.g., multiple AWS regions).

Detailed Explanation:

Rationale for Correct Answer: In Terraform, data sources are referenced using the format:data. < DATA_SOURCE_TYPE > . < NAME > . < ATTRIBUTE >

In this case:

Data source type = aws_ami

Name = web

Attribute = id

Therefore, the correct reference is:

data.aws_ami.web.id

This follows Terraform syntax for accessing attributes from data sources, which is a key concept in configuration authoring.

Analysis of Incorrect Options (Distractors):

B. aws_ami.web.id Incorrect because this format is used for resources, not data sources.

C. web.id Incorrect because it omits both the data prefix and the resource type.

D. data.web.id Incorrect because it is missing the data source type (aws_ami).

Key Concept: Proper referencing of data sources using data. < type > . < name > . < attribute > syntax.

This is how Terraform manages most dependencies between resources, by using the references between them in the configuration files. For example, if resource A depends on resource B, Terraform will create resource B first and then pass its attributes to resource A.

Rationale for Correct Answer: terraform init initializes the working directory: it sets up the backend, downloads providers, and installs modules. It does not validate that required input variables have values—that check occurs when running commands that evaluate the configuration (typically plan/apply), and terraform validate checks configuration structure, not whether you supplied runtime variable values.

Analysis of Incorrect Options (Distractors):

A: Yes—init installs required providers.

C: Yes—init initializes and configures the backend.

D: Yes—init retrieves and installs modules referenced by module blocks.

Key Concept: What terraform init does vs what happens at plan/apply time.