- A
The security group rule was added manually and Terraform removed it to match the configuration.
Terraform detects drift and reverts changes not in the configuration.
- B
The state file was corrupted and Terraform performed a refresh.
Why wrong: A refresh only updates state; it does not remove resources.
- C
The configuration was changed to remove the rule after the apply.
Why wrong: If the configuration was changed after apply, the next plan would show the removal, but the apply itself would not remove the rule.
- D
The developer accidentally ran 'terraform destroy' instead.
Why wrong: 'terraform destroy' would remove all resources, not just the new rule.
Quick Answer
The correct answer is that Terraform removed the manually added security group rule to reconcile the actual infrastructure with its declared configuration. This happens because Terraform operates on a desired-state model: during `terraform apply`, it compares the `.tf` configuration files against both the real-world infrastructure and the state file. Any resource or property added outside of Terraform—such as a security group rule created manually through the cloud console—is detected as drift, and Terraform automatically removes it to enforce the exact state defined in code. On the HashiCorp Terraform Associate TF-003 exam, this scenario tests your understanding of Terraform’s lifecycle management and its strict adherence to configuration as the single source of truth. A common trap is assuming Terraform only adds resources; in reality, it also destroys anything not in the config. Memory tip: "Terraform enforces the config—if it wasn't in the .tf file, it gets the axe."
TF-003 Use the core Terraform workflow Practice Question
This TF-003 practice question tests your understanding of use the core terraform workflow. 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 team uses Terraform to manage infrastructure. After running 'terraform apply', a developer notices that a new security group rule was added, but then immediately removed. 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.
Clue:
"immediately / without restart"Why it matters: Time or reboot constraint — the correct answer must take effect right away without requiring a reboot or reload.
Answer choices
Why each option matters
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
The security group rule was added manually and Terraform removed it to match the configuration.
Option A is correct because Terraform operates on a desired-state model: it compares the configuration in `.tf` files against the real-world infrastructure and the state file. If a security group rule was added manually outside of Terraform, Terraform detects it as a drift during the next `apply` and removes it to reconcile the actual state with the declared configuration. This is the core behavior of Terraform's lifecycle management.
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 security group rule was added manually and Terraform removed it to match the configuration.
Why this is correct
Terraform detects drift and reverts changes not in the configuration.
Clue confirmation
The clue words "most likely", "immediately / without restart" in the question point toward this answer.
Related concept
Read the scenario before looking for a memorised answer.
- ✗
The state file was corrupted and Terraform performed a refresh.
Why it's wrong here
A refresh only updates state; it does not remove resources.
- ✗
The configuration was changed to remove the rule after the apply.
Why it's wrong here
If the configuration was changed after apply, the next plan would show the removal, but the apply itself would not remove the rule.
- ✗
The developer accidentally ran 'terraform destroy' instead.
Why it's wrong here
'terraform destroy' would remove all resources, not just the new rule.
Common exam traps
Common exam trap: answer the scenario, not the keyword
HashiCorp often tests the misconception that Terraform only adds resources and never removes them, or that manual changes are automatically adopted; the trap here is that candidates confuse Terraform's 'import' capability (which requires explicit import) with automatic drift correction, leading them to think Terraform would preserve the manual rule.
Trap categories for this question
Command / output trap
If the configuration was changed after apply, the next plan would show the removal, but the apply itself would not remove the rule.
Detailed technical explanation
How to think about this question
Under the hood, Terraform uses a three-phase process: refresh (sync state with real resources), plan (compute diff between config and state), and apply (execute changes). When a resource is created manually, the refresh phase detects it, but Terraform's plan then marks it for deletion because it is absent from the configuration. This behavior is governed by Terraform's 'managed resources' principle — any resource not defined in configuration but present in state is considered drift and is removed. In real-world scenarios, this often catches teams off guard when they make ad-hoc changes via the console or CLI, leading to unexpected deletions during the next `terraform apply`.
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 — study guide chapter
Learn the concepts, then practise the questions
- →
Use the core Terraform 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
Related TF-003 practice-question pages
Use these pages to review the topic behind this question. This is how one missed question becomes focused revision.
Understand IaC concepts practice questions
Practise TF-003 questions linked to Understand IaC concepts.
Understand Terraform basics practice questions
Practise TF-003 questions linked to Understand Terraform basics.
Understand Terraform's purpose practice questions
Practise TF-003 questions linked to Understand Terraform's purpose.
Use Terraform outside the core workflow practice questions
Practise TF-003 questions linked to Use Terraform outside the core workflow.
Interact with Terraform modules practice questions
Practise TF-003 questions linked to Interact with Terraform modules.
Use the core Terraform workflow practice questions
Practise TF-003 questions linked to Use the core Terraform workflow.
Implement and maintain state practice questions
Practise TF-003 questions linked to Implement and maintain state.
Read, generate and modify configuration practice questions
Practise TF-003 questions linked to Read, generate and modify configuration.
TF-003 fundamentals practice questions
Practise TF-003 questions linked to TF-003 fundamentals.
TF-003 scenario practice questions
Practise TF-003 questions linked to TF-003 scenario.
TF-003 troubleshooting practice questions
Practise TF-003 questions linked to TF-003 troubleshooting.
Practice this exam
Start a free TF-003 practice session
Short sessions build daily habit. Longer sessions build exam-day stamina. Try a timed session to simulate real conditions.
FAQ
Questions learners often ask
What does this TF-003 question test?
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: The security group rule was added manually and Terraform removed it to match the configuration. — Option A is correct because Terraform operates on a desired-state model: it compares the configuration in `.tf` files against the real-world infrastructure and the state file. If a security group rule was added manually outside of Terraform, Terraform detects it as a drift during the next `apply` and removes it to reconcile the actual state with the declared configuration. This is the core behavior of Terraform's lifecycle management.
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.
Are there clue words in this question I should notice?
Yes — watch for: "most likely", "immediately / without restart". 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 →
Last reviewed: Jun 30, 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.