Free Practice Questions for HashiCorp Terraform-Associate-004 Exam

Detailed Explanation:

Rationale for Correct Answer: Terraform uses local state by default, but you can later configure another backend and migrate the existing state. Remote state is therefore an architectural choice rather than something that must be configured before the first apply. HashiCorp explicitly documents migration from local state to HCP Terraform.

Analysis of Incorrect Options (Distractors):

A: Changing to a remote backend is not inherently discouraged; remote state is commonly used for collaboration and centralized state management.

B: Terraform does not require you to migrate away from the local backend.

D: Backend migration is supported, so changing the backend is not impossible.

Key Concept: Backend configuration and state migration.

These are some of the ways that a ticket-based system can slow down infrastructure provisioning and limit the ability to scale, as they introduce delays, bottlenecks, and manual interventions in the process of creating and modifying infrastructure.

Rationale for Correct Answer: Terraform state is Terraform’s record of what it manages: it maps resource addresses in configuration to real-world resource IDs and stores metadata needed to plan changes. That makes it a source of truth for resources Terraform is managing, enabling accurate diffs, updates, and deletes.

Analysis of Incorrect Options (Distractors):

A: Incorrect—Terraform state does not schedule jobs; that’s the role of external schedulers/automation tools.

B: Incorrect—the desired state is expressed in .tf configuration, not in the state file. State reflects the current known state of managed infrastructure.

D: Incorrect—resources created manually in a cloud console are not automatically in Terraform state unless they are imported/adopted.

Key Concept: Purpose of Terraform state: resource mapping, metadata, and planning accuracy.

Detailed Explanation:

Rationale for Correct Answer: Terraform uses the .terraform directory as working-directory data and caches downloaded dependencies there, including modules and provider/plugin-related files. HashiCorp ' s tutorial describes .terraform as containing modules and plugins used to provision infrastructure.

Analysis of Incorrect Options (Distractors):

A: .terraform.lock.hcl is stored in the root working directory, not inside .terraform.

C: With the default local backend, terraform.tfstate is normally in the working directory, not the .terraform dependency directory.

D: .tf configuration files belong in the module ' s working directory.

Key Concept: Terraform working-directory structure and initialization artifacts.

Detailed Explanation:

Rationale for Correct Answer: terraform plan generates an execution plan so that you can preview the infrastructure changes Terraform intends to perform. It is commonly used to validate configuration changes and confirm that the proposed actions match your expectations before applying them.

Analysis of Incorrect Options (Distractors):

B: This describes state-refresh/synchronization behavior rather than the primary purpose of a normal plan.

C: terraform init initializes the working directory.

D: terraform fmt formats Terraform configuration files.

Key Concept: The Terraform workflow of previewing changes before applying them.