The answer is that the 'name' attribute is likely marked as ForceNew, meaning any change to it forces resource replacement even if the engineer only modified a tag. In Terraform, the ForceNew meta-argument instructs the provider to destroy and recreate a resource whenever a specific attribute changes, regardless of what the engineer intended to update. This is a common trap on the HashiCorp Terraform Associate TF-003 exam, where candidates must distinguish between in-place updates and forced replacement. The exam tests your understanding that computed or provider-defined attributes like 'name' often trigger ForceNew behavior, while tags typically allow in-place modification. A memory tip: think of ForceNew as a "nuclear option" for an attribute—any change, even accidental, triggers a full rebuild.
TF-003 Read, generate and modify configuration Practice Question
This TF-003 practice question tests your understanding of read, generate and modify configuration. Examine the command output carefully: the correct answer depends on what the output actually shows, not on general recall alone. 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, the output indicates that a resource will be replaced (destroy then create) due to a change in the 'name' attribute. However, the engineer only changed a tag. 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 'name' attribute is computed and any change to the resource forces replacement.
Option C is correct: the 'name' attribute may be ForceNew, meaning any change forces replacement. Option A is wrong because create_before_destroy does not cause this. Option B is wrong because tags are not typically ForceNew. Option D is wrong because underlying SDK may not trigger replacement for tags.
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 tag change triggered a ForceNew attribute.
Why it's wrong here
Tags alone usually do not force replacement.
✗
The resource has create_before_destroy enabled.
Why it's wrong here
create_before_destroy affects ordering, not whether replacement occurs.
✓
The 'name' attribute is computed and any change to the resource forces replacement.
Why this is correct
Some providers mark certain attributes as ForceNew; if name is ForceNew, any config change to the resource may trigger replacement.
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.
✗
The underlying API does not support in-place updates.
Why it's wrong here
If the API doesn't support in-place updates, any change to any attribute would cause replacement, but tags often can be updated.
Common exam traps
Common exam trap: answer the scenario, not the keyword
Many certification questions include familiar terms but test a specific constraint. Read the exact wording before choosing an answer that is generally true but wrong for this case.
Detailed technical explanation
How to think about this question
This question should be treated as a scenario, not a definition check. Identify the problem, the constraint and the best action. Then compare each option against those facts.
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.
Use explanations to understand the rule behind the answer.
TExam Day Tips
→Underline the problem statement mentally.
→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 TF-003 exam domain this question belongs to, then review the specific concept being tested. Practise related questions in that domain and focus on understanding why each wrong answer is tempting — not just why the correct answer is right.
Read, generate and modify configuration — This question tests Read, generate and modify configuration — Read the scenario before looking for a memorised answer..
What is the correct answer to this question?
The correct answer is: The 'name' attribute is computed and any change to the resource forces replacement. — Option C is correct: the 'name' attribute may be ForceNew, meaning any change forces replacement. Option A is wrong because create_before_destroy does not cause this. Option B is wrong because tags are not typically ForceNew. Option D is wrong because underlying SDK may not trigger replacement for tags.
What should I do if I get this TF-003 question wrong?
Identify which TF-003 exam domain this question belongs to, then review the specific concept being tested. Practise related questions in that domain and focus on understanding why each wrong answer is tempting — not just why the correct answer is right.
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.