Quick Answer
The correct answer is to run terraform apply again. This works because Terraform maintains a state file that records every resource it manages; when an apply fails mid-way, the state file is updated to reflect only the resources that were successfully created, not the ones that failed. Running terraform apply again causes Terraform to compare the current state against your configuration, detect that the already-created resources exist, and proceed to create only the remaining resources—effectively resuming the failed apply without destroying anything. On the HashiCorp Terraform Associate TF-003 exam, this scenario tests your understanding of Terraform’s state-driven workflow and the idempotent nature of apply; a common trap is assuming you must run terraform destroy first or manually roll back, but Terraform’s state file makes that unnecessary. Memory tip: “State saves the day—apply again, no need to slay.”
This TF-003 practice question tests your understanding of use terraform outside the core workflow. The scenario asks you to isolate a root cause — eliminate options that address a different problem before choosing. 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.
During a `terraform apply`, the operation fails mid-way due to a network outage, leaving some resources created. The operator wants to resume applying from where it left off without destroying the already-created resources. What should they do?
Run terraform apply again
Idempotent; creates missing resources.
Run terraform destroy and then apply
Why wrong: Unnecessarily destroys existing resources.
Run terraform refresh
Why wrong: Only updates state, does not create resources.
Run terraform apply -auto-approve
Why wrong: Same as apply, but auto-approve doesn't resume.
Answer choices
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
Run terraform apply again
Option A is correct because Terraform uses a state file to track the resources it manages. When `terraform apply` fails mid-way, the state file is updated to reflect the resources that were successfully created. Running `terraform apply` again will cause Terraform to compare the current state with the configuration, detect that the already-created resources exist, and proceed to create only the remaining resources, effectively resuming from where it left off without destroying anything.
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.
Run terraform apply again
Why this is correct
Idempotent; creates missing resources.
Related concept
Read the scenario before looking for a memorised answer.
Run terraform destroy and then apply
Why it's wrong here
Unnecessarily destroys existing resources.
Run terraform refresh
Why it's wrong here
Only updates state, does not create resources.
Run terraform apply -auto-approve
Why it's wrong here
Same as apply, but auto-approve doesn't resume.
Common exam traps
The trap here is that candidates may think a failed apply requires a full destroy or refresh, but Terraform's state-driven design allows idempotent resumption, and the exam tests understanding that `terraform apply` is the correct command to re-run after any partial failure.
Detailed technical explanation
Under the hood, Terraform's state file acts as the source of truth for resource dependencies and lifecycle. When a partial apply occurs, the state file is written incrementally, so subsequent plans correctly treat existing resources as 'no-op' (no operation needed). A real-world scenario is a large multi-region deployment where a transient network failure stops the apply; re-running `terraform apply` leverages the state to skip completed resources and only attempt the failed ones, avoiding costly full teardowns.
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.
Use Terraform outside the core workflow — study guide chapter
Learn the concepts, then practise the questions
Use Terraform outside the core workflow 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
Use Terraform outside the core workflow — This question tests Use Terraform outside the core workflow — Read the scenario before looking for a memorised answer..
The correct answer is: Run terraform apply again — Option A is correct because Terraform uses a state file to track the resources it manages. When `terraform apply` fails mid-way, the state file is updated to reflect the resources that were successfully created. Running `terraform apply` again will cause Terraform to compare the current state with the configuration, detect that the already-created resources exist, and proceed to create only the remaining resources, effectively resuming from where it left off without destroying anything.
Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.
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 →
Same concept, more angles
These questions test the same concept from different angles. Work through them to make sure you can recognise it however the exam phrases it.
Variation 1. During a CI/CD pipeline run, terraform apply fails halfway through due to a network error. The state file is locked. The team wants to resume from the last successful apply. What should they do?
hardWhy A: Option C is correct because `terraform apply -lock=false` is dangerous and not recommended. The correct approach is to fix the issue, then re-run `terraform apply` which will attempt to apply the remaining resources because state knows what was already created. Option A is wrong because forcing unlock without investigation can corrupt state. Option B is wrong because destroy will remove partially created resources. Option D is wrong because manual deletion is error-prone.
Last reviewed: Jun 11, 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.