Pass the HashiCorp Terraform Associate Terraform-Associate-004 Questions and answers with CertsForce

Rationale for Correct Answer: terraform plan -refresh-only refreshes (reconciles) the state with the real infrastructure only for the purpose of the plan output. It does not persist (write) those updates to the state file. To actually update the stored state, you must run terraform apply -refresh-only (or a normal terraform apply). This matches the Terraform CLI objective: plan previews changes; apply makes changes (including writing state).

Analysis of Incorrect Options (Distractors):

A (True): Incorrect because terraform plan does not write state; it only calculates and displays what would change.

Key Concept: The plan vs apply workflow and when Terraform writes state.

Theversion argumentin a module ensures Terraform uses aspecific versionof a module, preventing unintended updates.

A (source)– Specifies the module source butdoes not control versioning.

B (count)– Controls how many instances of a resource/module exist,not updates.

D (lifecycle)– Controls how resources behavebut does not control module versioning.

Official Terraform Documentation Reference:

Module Version Constraints

This is not a responsibility of a Terraform provider, as it does not make sense grammatically or logically. A Terraform provider is responsible for exposing resources and data sources based on an API, managing actions to take based on resource differences, and understanding API interactions with some service.

Rationale for Correct Answer: depends_on explicitly adds a dependency edge in Terraform’s graph. By adding depends_on = [azurerm_role_assignment.kv_access] to the web app resource, you force Terraform to create the role assignment first, even if Terraform can’t infer the dependency from attribute references.

Analysis of Incorrect Options (Distractors):

B: create_before_destroy is a lifecycle setting relevant to replacement behavior, not initial create ordering between independent resources.

C: File/block order does not control creation order; Terraform uses its dependency graph.

D: count controls quantity, not ordering.

Key Concept: Dependency graph and explicit dependencies via depends_on.

This is a secure way to inject sensitive variables into your Terraform run, as they will not be stored in any file or source code repository. You can also use environment variables or variable files with encryption to pass sensitive variables to Terraform.

Detailed Explanation:

Rationale for Correct Answer: terraform init initializes the working directory. It downloads required providers, installs modules, and configures the backend. You must run it before running terraform plan or terraform apply for the first time in a new configuration directory.

Analysis of Incorrect Options (Distractors):

B. terraform workspace. Incorrect. This command manages Terraform workspaces but does not initialize providers, modules, or backends.

C. terraform validate. Incorrect. Validation is useful, but it is not the required initialization step before planning or applying.

D. terraform import. Incorrect. Import brings existing infrastructure into Terraform state. It is not required before planning or applying a new configuration.

Key Concept: Terraform working directories must be initialized with terraform init.

C (✅Correct)– If changes require aresource replacement(e.g., changing an immutable attribute like instance type), Terraform willdestroy and recreate the resource.

E (✅Correct)– Terraform only appliesthe configuration in the current directory or workspace.

Rationale for Correct Answer (False):

Any user with access to the saved plan file (terraform plan -out=planfile) can run terraform apply planfile. Terraform does not enforce user-specific restrictions.

Analysis of Incorrect Option:

True: Incorrect — Terraform doesn’t tie plan files to individual users.

Key Concept:

Plan files ensure predictability but are not bound to the identity of the user.

Rationale for Correct Answer: Terraform can store state in a remote backend (remote location) configured in the terraform block (for example, terraform { backend " s3 " { ... } } or terraform { cloud { ... } }). Remote backends store the state outside the local filesystem and often add collaboration features like locking.

Analysis of Incorrect Options (Distractors):

B: Incorrect—CLI configuration files (like .terraformrc / terraform.rc) control CLI behavior (credentials helpers, plugin cache, etc.), but backend/state storage is configured in the Terraform configuration (terraform block) and initialized with terraform init.

C: Incorrect—Terraform must persist state between runs; in-memory storage would be lost when the process ends.

D: Incorrect—environment variables can influence behavior (e.g., credentials, logging), but Terraform does not store state in environment variables.

Key Concept: Configuring remote backends for state storage via the terraform block.

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.