The correct answer is that the variable change triggers a new value for each resource, causing Terraform to see differences. When you use `count` in a resource block, Terraform treats the resulting set of instances as an ordered list; any change to the `count` argument itself or to a variable referenced inside the resource—such as a new instance type variable—forces Terraform to recalculate the entire list. Because `count` relies on a static index, altering a variable that feeds into the resource configuration makes Terraform perceive every indexed instance as having changed, leading to full recreation rather than in-place updates. On the HashiCorp Terraform Associate TF-003 exam, this concept tests your understanding of how `count` interacts with `terraform plan` and state management; a common trap is assuming that only the `count` number itself triggers recreation, when in fact any referenced variable change can do so. Remember the memory tip: “Count creates a list, so any variable twist recreates the whole list.”
TF-003 Understand Terraform basics Practice Question
This TF-003 practice question tests your understanding of understand terraform basics. 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.
A Terraform configuration uses `count` to create multiple EC2 instances. After adding a new variable for instance type, the user runs `terraform plan` and sees that all instances are marked for recreation. 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 variable change triggers a new value for each resource, causing Terraform to see differences
Option A is correct because `count` treats the resource as a list; changing `count` or any argument used in the resource can cause recreation. Option B is wrong because the state file is not modified by plan. Option C is wrong because re-indexing only happens if the order changes, not for all. Option D is wrong because `terraform refresh` does not alter config. Option E is wrong because provider issues do not cause this.
Key principle: NAT direction and interface roles matter as much as the IP address mapping. Inside/outside designation controls which traffic is translated.
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 `count` index changed, causing all resources to be re-indexed
Why it's wrong here
Re-indexing does not force recreation unless the resource address changes.
✗
The user forgot to run `terraform refresh` after changing the variable
Why it's wrong here
Refresh reads real-world state, but does not change config.
✗
The state file is corrupt and needs to be refreshed
Why it's wrong here
Corrupt state would produce an error, not plan changes.
✓
The variable change triggers a new value for each resource, causing Terraform to see differences
Why this is correct
Correct: Changing attributes on a resource with count may cause recreation.
Clue confirmation
The clue word "most likely" in the question point toward this answer.
Related concept
Static NAT maps one inside address to one outside address.
✗
The provider version is incompatible with the new variable type
Why it's wrong here
Incompatible provider would cause an error, not plan changes.
Common exam traps
Common exam trap: NAT rules depend on direction and matching traffic
NAT is not only about the public address. The inside/outside interface roles and the ACL or rule that matches traffic are just as important.
Trap categories for this question
Real-world vs exam trap
Refresh reads real-world state, but does not change config.
Detailed technical explanation
How to think about this question
NAT questions usually test address translation, overload/PAT behaviour, static mappings and whether the right traffic is being translated. Read the interface direction and address terms carefully.
KKey Concepts to Remember
Static NAT maps one inside address to one outside address.
PAT allows many inside hosts to share one public address using ports.
Inside local and inside global describe the private and translated addresses.
NAT ACLs identify traffic for translation, not always security filtering.
TExam Day Tips
→Identify inside and outside interfaces first.
→Check whether the scenario needs static NAT, dynamic NAT or PAT.
→Do not confuse NAT matching ACLs with normal packet-filtering intent.
Key takeaway
NAT direction and interface roles matter as much as the IP address mapping. Inside/outside designation controls which traffic is translated.
Real-world example
How this comes up in practice
A small business has 20 workstations on the 192.168.1.0/24 network and one public IP from its ISP. The router uses PAT (NAT overload) so all 20 devices share one public address using different source ports. NAT questions test whether you understand the four address terms and which direction each translation applies.
What to study next
Got this wrong? Here's your next step.
Review the four NAT address types (inside local, inside global, outside local, outside global), PAT port overload, and static vs dynamic NAT use cases. Then practise related TF-003 NAT questions on configuration and troubleshooting.
Understand Terraform basics — This question tests Understand Terraform basics — Static NAT maps one inside address to one outside address..
What is the correct answer to this question?
The correct answer is: The variable change triggers a new value for each resource, causing Terraform to see differences — Option A is correct because `count` treats the resource as a list; changing `count` or any argument used in the resource can cause recreation. Option B is wrong because the state file is not modified by plan. Option C is wrong because re-indexing only happens if the order changes, not for all. Option D is wrong because `terraform refresh` does not alter config. Option E is wrong because provider issues do not cause this.
What should I do if I get this TF-003 question wrong?
Review the four NAT address types (inside local, inside global, outside local, outside global), PAT port overload, and static vs dynamic NAT use cases. Then practise related TF-003 NAT questions on configuration and troubleshooting.
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?
Static NAT maps one inside address to one outside address.
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.