The correct approach is to run terraform plan -out=plan.tfplan and then terraform show plan.tfplan. This two-step process saves the plan to a binary file and then displays the full, detailed output, including the exact attribute-level diff and the underlying reason for the proposed change—typically a drift between the Terraform configuration and the actual state of the infrastructure. By inspecting the plan output in this way, the engineer can isolate the root cause of the unintended security group rule update without applying any changes or affecting other resources. On the HashiCorp Terraform Associate TF-003 exam, this scenario tests your understanding of how to safely troubleshoot plan results; a common trap is to assume terraform plan alone provides enough detail, but it truncates the full diff. Remember the mnemonic: Plan to save, show to probe.
TF-003 Use the core Terraform workflow Practice Question
This TF-003 practice question tests your understanding of use the core terraform 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.
A company uses Terraform to manage infrastructure in multiple AWS accounts. An engineer runs terraform plan and sees that a security group rule will be updated, but the change is not intended. The engineer wants to understand why Terraform is proposing the change without affecting other resources. Which approach should the engineer take to troubleshoot?
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Run terraform plan -out=plan.tfplan and then terraform show plan.tfplan.
Option D is correct because `terraform plan -out=plan.tfplan` saves the plan to a binary file, and `terraform show plan.tfplan` then displays the full plan details, including the exact attribute-level diff and the reason for the change (e.g., a drift between the configuration and the state). This allows the engineer to inspect the proposed change without applying it, isolating the root cause without affecting other resources.
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.
✗
Run terraform state list to review the current state.
Why it's wrong here
State list shows resources in state, not proposed changes.
✗
Run terraform show to display the current state.
Why it's wrong here
terraform show shows state or plan, but without a plan file it shows state, not proposed changes.
✗
Run terraform validate to check for configuration errors.
Why it's wrong here
Validate checks syntax and consistency, not plan logic.
✓
Run terraform plan -out=plan.tfplan and then terraform show plan.tfplan.
Why this is correct
This saves the plan and allows detailed inspection of proposed changes.
Related concept
Read the scenario before looking for a memorised answer.
Common exam traps
Common exam trap: answer the scenario, not the keyword
HashiCorp often tests the misconception that `terraform show` alone (without a plan file) reveals the reason for a proposed change, when in fact it only displays the current state or a previously saved plan, not the diff logic for a new plan.
Trap categories for this question
Command / output trap
State list shows resources in state, not proposed changes.
Detailed technical explanation
How to think about this question
The `terraform plan -out` command serializes the plan into a binary format that includes the full dependency graph, resource attribute diffs, and the computed values for each planned action. When you run `terraform show` on that plan file, it decodes the binary and presents a human-readable diff, including the old and new values for each attribute, which is essential for debugging unintended changes caused by state drift, provider version differences, or manual modifications in the AWS console. In multi-account setups, this approach is critical because a plan might propose changes due to stale state or cross-account resource references that are not obvious from the plan summary alone.
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: Run terraform plan -out=plan.tfplan and then terraform show plan.tfplan. — Option D is correct because `terraform plan -out=plan.tfplan` saves the plan to a binary file, and `terraform show plan.tfplan` then displays the full plan details, including the exact attribute-level diff and the reason for the change (e.g., a drift between the configuration and the state). This allows the engineer to inspect the proposed change without applying it, isolating the root cause without affecting other resources.
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.