TF-003 Use the core Terraform workflow Practice Question
This TF-003 practice question tests your understanding of use the core terraform workflow. This is a configuration task: choose the command set that satisfies every stated requirement. Small differences — like 'secret' vs 'password' or 'transport input ssh' vs 'all' — change whether the answer is correct. 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.
When running `terraform plan`, an engineer sees that Terraform proposes to destroy an existing resource even though the configuration file appears unchanged. What is the most likely cause?
Clue words in this question
Noticing these words before you look at the options changes how you read each choice.
Clue: "most likely"
Why it matters: Probability qualifier — the question wants the most probable cause or outcome, not a guaranteed one. Eliminate low-probability options.
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
The resource's `count` or `for_each` meta-argument was removed from the configuration
Option A is correct because removing the `count` or `for_each` meta-argument from a resource block causes Terraform to interpret the resource as no longer being managed by the configuration. Since Terraform tracks resources by their logical address in the state, the absence of the meta-argument means the existing resource (previously indexed, e.g., `resource.name[0]`) no longer matches any configuration block, so Terraform plans to destroy it. This is a common source of unexpected destruction when the resource count is reduced or the loop construct is removed entirely.
Key principle: Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
✓
The resource's `count` or `for_each` meta-argument was removed from the configuration
Why this is correct
Correct! Removing the count or for_each reduces the number of instances, leading to planned destruction.
Clue confirmation
The clue word "most likely" in the question point toward this answer.
Related concept
Read the scenario before looking for a memorised answer.
✗
Another user ran `terraform destroy` without the engineer's knowledge
Why it's wrong here
If destroy was run, the resource would be gone and not appear in plan for destroy.
✗
The state file was corrupted and lost the resource
Why it's wrong here
If state is lost, Terraform would plan to create the resource, not destroy.
✗
The resource was manually deleted from the cloud provider console
Why it's wrong here
If the resource is already deleted, Terraform would not plan to destroy it; it would see it as missing and plan to create it.
Common exam traps
Common exam trap: answer the scenario, not the keyword
HashiCorp often tests the misconception that state corruption or manual deletion causes destruction plans, but the trap here is that candidates overlook how removing `count` or `for_each` changes the resource address, leading to an unexpected destroy without any change to the resource's own attributes.
Detailed technical explanation
How to think about this question
Under the hood, Terraform uses the resource address (e.g., `aws_instance.web[0]`) as the key in the state. When `count` or `for_each` is removed, the configuration no longer produces an indexed address, so Terraform sees the state entry as orphaned and schedules it for destruction. This behavior is governed by Terraform's core logic of comparing the configuration graph to the state graph, where any state resource without a matching configuration block is marked for deletion. In real-world scenarios, this often occurs when refactoring from a list of resources to a single resource or when accidentally deleting the meta-argument during a code merge.
KKey Concepts to Remember
Read the scenario before looking for a memorised answer.
Find the constraint that changes the correct option.
Eliminate answers that are true in general but not in this case.
TExam Day Tips
→Watch for words such as best, first, most likely and least administrative effort.
→Review why wrong options are wrong, not only why the correct option is correct.
Key takeaway
Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
Real-world example
How this comes up in practice
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
Got this wrong? Here's your next step.
Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.
Use the core Terraform workflow — This question tests Use the core Terraform workflow — Read the scenario before looking for a memorised answer..
What is the correct answer to this question?
The correct answer is: The resource's `count` or `for_each` meta-argument was removed from the configuration — Option A is correct because removing the `count` or `for_each` meta-argument from a resource block causes Terraform to interpret the resource as no longer being managed by the configuration. Since Terraform tracks resources by their logical address in the state, the absence of the meta-argument means the existing resource (previously indexed, e.g., `resource.name[0]`) no longer matches any configuration block, so Terraform plans to destroy it. This is a common source of unexpected destruction when the resource count is reduced or the loop construct is removed entirely.
What should I do if I get this TF-003 question wrong?
Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.
Are there clue words in this question I should notice?
Yes — watch for: "most likely". Probability qualifier — the question wants the most probable cause or outcome, not a guaranteed one. Eliminate low-probability options.
What is the key concept behind this question?
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 →
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.
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.