Quick Answer
The answer is `terraform state rm <resource>`. This command is the correct choice because it surgically removes a specific resource from the Terraform state file without making any API calls to the actual infrastructure provider, leaving the real-world resource running and completely detached from Terraform management. On the HashiCorp Terraform Associate TF-003 exam, this question tests your understanding of state manipulation versus resource destruction—a common trap is confusing `terraform destroy` (which deletes infrastructure) with `terraform state rm` (which only removes tracking). The exam often presents scenarios where a resource must be taken out of state for migration or manual management, and the key distinction is that no cloud provider API is contacted. Remember the mnemonic: "State rm is a paperwork change, not a wrecking ball"—it only edits the local state file, leaving your actual servers untouched.
This TF-003 practice question tests your understanding of implement and maintain state. Read the scenario carefully and evaluate each option against the stated constraints before committing to an answer. After answering, compare your reasoning against the explanation and wrong-answer breakdown below. Once you have made your selection, read the full explanation to reinforce the concept and understand why each distractor is designed to mislead on exam day.
A user wants to remove a specific resource from Terraform state without destroying the actual infrastructure. Which command should they use?
Clue words in this question
Noticing these words before you look at the options changes how you read each choice.
Clue: "which command"
Why it matters: Tests specific CLI syntax. Recall the exact command and its required context — near-synonyms and partial matches are common distractors.
terraform state rm resource
This removes the resource from state without affecting the real infrastructure.
terraform taint resource
Why wrong: Taint marks resource for recreation, not removal from state.
terraform state mv resource
Why wrong: This moves the resource to a new address, not removal.
terraform destroy -target=resource
Why wrong: Destroy destroys the resource, not just state removal.
Answer choices
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
terraform state rm resource
The `terraform state rm` command is the correct choice because it removes a specified resource from the Terraform state file without making any API calls to the actual infrastructure provider. This allows the resource to be detached from Terraform management while leaving the real-world resource running, which is exactly what the user wants.
Key principle: Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
Answer analysis
For each option: why learners choose it and why it is or isn't the right answer here.
terraform state rm resource
Why this is correct
This removes the resource from state without affecting the real infrastructure.
Clue confirmation
The clue word "which command" in the question point toward this answer.
Related concept
Read the scenario before looking for a memorised answer.
terraform taint resource
Why it's wrong here
Taint marks resource for recreation, not removal from state.
terraform state mv resource
Why it's wrong here
This moves the resource to a new address, not removal.
terraform destroy -target=resource
Why it's wrong here
Destroy destroys the resource, not just state removal.
Common exam traps
HashiCorp often tests the distinction between state manipulation commands that affect only the state file versus commands that trigger actual infrastructure changes, so candidates may confuse `terraform state rm` with `terraform destroy` or `terraform taint`.
Detailed technical explanation
Under the hood, `terraform state rm` directly edits the state JSON file, removing the resource's entire block including its metadata and dependencies. This is useful in scenarios where a resource was manually created outside Terraform and imported, but you later decide to manage it with a different tool or simply stop tracking it, while ensuring no accidental deletion occurs.
Key takeaway
Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
Real-world example
A practitioner preparing for the TF-003 exam encounters this exact type of scenario on the job. The correct answer here is not the most general option — it is the best answer for the specific constraint described. Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option. Real exam questions reward reading the full scenario before eliminating options, because the constraint defines which answer fits.
What to study next
Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.
Implement and maintain state — study guide chapter
Learn the concepts, then practise the questions
Implement and maintain state practice questions
Targeted practice on this topic area only
All TF-003 questions
519 questions across all exam domains
HashiCorp Terraform Associate TF-003 study guide
Full concept coverage aligned to exam objectives
TF-003 practice test guide
How to use practice tests most effectively before exam day
Related practice questions
Use these pages to review the topic behind this question. This is how one missed question becomes focused revision.
Practise TF-003 questions linked to Understand IaC concepts.
Practise TF-003 questions linked to Understand Terraform basics.
Practise TF-003 questions linked to Understand Terraform's purpose.
Practise TF-003 questions linked to Use Terraform outside the core workflow.
Practise TF-003 questions linked to Interact with Terraform modules.
Practise TF-003 questions linked to Use the core Terraform workflow.
Practise TF-003 questions linked to Implement and maintain state.
Practise TF-003 questions linked to Read, generate and modify configuration.
Practise TF-003 questions linked to TF-003 fundamentals.
Practise TF-003 questions linked to TF-003 scenario.
Practise TF-003 questions linked to TF-003 troubleshooting.
Practice this exam
Short sessions build daily habit. Longer sessions build exam-day stamina. Try a timed session to simulate real conditions.
FAQ
Implement and maintain state — This question tests Implement and maintain state — Read the scenario before looking for a memorised answer..
The correct answer is: terraform state rm resource — The `terraform state rm` command is the correct choice because it removes a specified resource from the Terraform state file without making any API calls to the actual infrastructure provider. This allows the resource to be detached from Terraform management while leaving the real-world resource running, which is exactly what the user wants.
Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.
Yes — watch for: "which command". Tests specific CLI syntax. Recall the exact command and its required context — near-synonyms and partial matches are common distractors.
Read the scenario before looking for a memorised answer.
About these practice questions
Courseiva creates original exam-style practice questions with explanations and wrong-answer analysis. It does not publish real exam questions, exam dumps, or protected exam content. Learn why practice questions differ from exam dumps →
Last reviewed: Jun 30, 2026
This TF-003 practice question is part of Courseiva's free HashiCorp certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the TF-003 exam.
Question Discussion
Share a tip, memory trick, or ask about the reasoning behind this question. Do not post real exam questions, leaked content, braindumps, or copyrighted exam material. Comments are moderated and may be removed without notice.
Sign in to join the discussion.