The answer is that the new instance is created first, then the old one is deleted. This is correct because Terraform’s default lifecycle behavior for most resources is `create_before_destroy = false`, meaning the old resource is typically destroyed before the new one is created. However, when a change like a new AMI triggers a recreate, Terraform intelligently reverses this order: it creates the replacement resource first, then destroys the old one, ensuring minimal downtime during the update. On the HashiCorp Terraform Associate TF-003 exam, this concept tests your understanding of how Terraform handles resource replacement versus simple updates—a common trap is assuming the default destroy-then-create order always applies. Remember that for resources supporting replacement, Terraform prioritizes availability by creating before destroying. A helpful memory tip: think “new first, then old” for any change that forces a recreate, as Terraform builds the replacement before removing the original to keep your infrastructure running.
TF-003 Understand IaC concepts Practice Question
This TF-003 practice question tests your understanding of understand iac concepts. 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.
After applying the configuration above, the user changes the AMI to a new value and runs 'terraform apply'. Assuming the new AMI triggers a recreate, what happens during the apply?
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
The new instance is created first, then the old one is deleted.
Option C is correct because Terraform's default lifecycle behavior for most resources is 'create_before_destroy = false', meaning the old resource is destroyed before the new one is created. However, when a resource's configuration change triggers a recreate (like an AMI change for an AWS instance), Terraform first creates the new instance, then destroys the old one, ensuring minimal downtime. This is the standard behavior for resources that support replacement, as Terraform plans the creation of the new resource before destroying the old one to maintain availability.
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 existing instance is deleted before the new one is created.
Why it's wrong here
That is the default behavior; create_before_destroy inverts this.
✗
Both instances run simultaneously only if the instance type allows it.
Why it's wrong here
Create_before_destroy always creates the new before destroying the old, so both exist during transition.
✓
The new instance is created first, then the old one is deleted.
Why this is correct
Create_before_destroy ensures the new resource is ready before removing the old.
Related concept
Read the scenario before looking for a memorised answer.
✗
The plan fails because AMI change with create_before_destroy is not allowed.
Why it's wrong here
AMI changes are allowed; create_before_destroy is a lifecycle option.
Common exam traps
Common exam trap: answer the scenario, not the keyword
HashiCorp often tests the misconception that Terraform always destroys before creating, but the trap here is that for resources requiring replacement (like an AMI change), Terraform defaults to creating the new resource first to minimize downtime, unless explicitly configured otherwise.
Detailed technical explanation
How to think about this question
Under the hood, Terraform's resource lifecycle uses a dependency graph to determine the order of operations. For resources like 'aws_instance', when a force-new attribute (e.g., AMI) changes, Terraform marks the resource for replacement and schedules the creation of the new resource before the destruction of the old one, unless 'create_before_destroy' is explicitly set to false. This behavior is controlled by the 'lifecycle' meta-argument, and the default for most resources is 'create_before_destroy = false', but for resources that support replacement, Terraform overrides this to create first to prevent downtime. In real-world scenarios, this is critical for maintaining service availability during rolling updates or infrastructure changes.
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.
Understand IaC concepts — This question tests Understand IaC concepts — Read the scenario before looking for a memorised answer..
What is the correct answer to this question?
The correct answer is: The new instance is created first, then the old one is deleted. — Option C is correct because Terraform's default lifecycle behavior for most resources is 'create_before_destroy = false', meaning the old resource is destroyed before the new one is created. However, when a resource's configuration change triggers a recreate (like an AMI change for an AWS instance), Terraform first creates the new instance, then destroys the old one, ensuring minimal downtime. This is the standard behavior for resources that support replacement, as Terraform plans the creation of the new resource before destroying the old one to maintain availability.
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.
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.