Terraform-Associate-004 Exam Dumps : HashiCorp Certified: Terraform Associate (004) (HCTA0-004)

Rationale for Correct Answer: terraform state rm < address > removes a resource from Terraform state without destroying the real infrastructure. After removal, Terraform “forgets” it and will no longer manage it (unless it’s re-imported). That matches the requirement: keep the resource, stop managing it.

Analysis of Incorrect Options (Distractors):

A: Removing the resource block causes Terraform to plan to destroy the resource (because it’s in state but no longer in config), which is the opposite of “keep it.”

B: Changing count can cause Terraform to destroy instances that no longer have an address (depending on indexing), and it doesn’t explicitly “stop managing” a specific existing instance safely.

D: moved blocks are for renaming/refactoring addresses while keeping management; they do not stop managing a resource.

Key Concept: Detaching resources from Terraform management using state subcommands (terraform state rm).

Detailed Explanation:

Rationale for Correct Answer:The error indicates that the saved plan is stale, meaning the Terraform state has changed since the plan was created. Terraform ensures consistency between the plan and the current state, so it will not allow applying an outdated plan file.

D is correct because generating a new plan (terraform plan) ensures it reflects the current state, after which it can be safely applied.

E is also correct because running terraform apply without a saved plan automatically creates a fresh plan and applies it in one step, ensuring consistency with the latest state.

Analysis of Incorrect Options (Distractors):

A. terraform state push — Incorrect because this command is used to manually push state data, not to update or fix a stale execution plan.

B. -refresh-only flag — Incorrect because this updates the state to match real infrastructure but does not resolve the stale saved plan issue or make it applicable.

C. -lock=false — Incorrect because state locking prevents concurrent operations; disabling it does not fix the mismatch between the saved plan and the current state.

Key Concept:Terraform saved plans are state-dependent and become invalid if the state changes. You must regenerate the plan or apply without using a saved plan.

Terraforminstalls providers during the terraform init phase.

Providers aredownloaded and installedwhen running terraform init.

A (terraform plan)is incorrect because terraform plan only calculates changes but does not install providers.

C (terraform refresh)is incorrect because terraform refresh only updates the state but does not install providers.

Official Terraform Documentation Reference:

Provider Installation - HashiCorp Documentation