Question 112 of 519
Implement and maintain statemediumMultiple ChoiceObjective-mapped

Quick Answer

The answer is that the state file has not been refreshed since the manual AMI change, so it still reflects the old AMI. This is the most likely cause of terraform state drift because Terraform compares its local state file against the configuration, not against the live infrastructure, during a standard plan. When the state is stale, it reports no changes even though the actual AWS instance has been modified externally. On the HashiCorp Terraform Associate TF-003 exam, this scenario tests your understanding of state drift causes and the refresh lifecycle—a common trap is assuming `terraform plan` always checks the real world, when in fact it only reads the cached state. Remember that drift is invisible until you explicitly run `terraform refresh` or `terraform apply`, which triggers a state sync. A useful memory tip: “Plan reads state, not reality; refresh bridges the gap.”

TF-003 Implement and maintain state Practice Question

This TF-003 practice question tests your understanding of implement and maintain state. 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.

Exhibit

Refer to the exhibit.

```
$ terraform show
# data.aws_ami.ubuntu
id = "ami-0c55b159cbfafe1f0"
# aws_instance.web
resource "aws_instance" "web" {
  ami           = "ami-0c55b159cbfafe1f0"
  instance_type = "t2.micro"
  tags = {
    Name = "WebServer"
  }
}
```

Refer to the exhibit. A Terraform configuration includes an `aws_instance.web` resource. The state shows the instance with a specific AMI and instance type. After running `terraform plan`, Terraform reports no changes. However, an engineer observes that the actual instance in AWS has a different AMI ID but the same instance type. 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.

Question 1mediummultiple choice
Full question →

Exhibit

Refer to the exhibit.

```
$ terraform show
# data.aws_ami.ubuntu
id = "ami-0c55b159cbfafe1f0"
# aws_instance.web
resource "aws_instance" "web" {
  ami           = "ami-0c55b159cbfafe1f0"
  instance_type = "t2.micro"
  tags = {
    Name = "WebServer"
  }
}
```

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 state file has not been refreshed since the manual AMI change; it still reflects the old AMI

If the state shows the old AMI, but the actual instance has a different AMI, the state is stale. A `terraform refresh` or apply should detect drift. Option C correctly identifies that the state has not been refreshed.

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 instance type was modified after the last apply, but AMI was not

    Why it's wrong here

    The question says AMI changed and instance type same.

  • The state file has not been refreshed since the manual AMI change; it still reflects the old AMI

    Why this is correct

    Terraform compares state to config, not state to real world, unless refresh happens.

    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 `terraform plan` command ignores drift by default

    Why it's wrong here

    Plan always reads state; drift is only shown if refresh is enabled.

  • The AMI data source is returning a different value each time

    Why it's wrong here

    Data sources update during refresh, but the resource AMI is a fixed attribute.

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.

Trap categories for this question

  • Command / output trap

    Plan always reads state; drift is only shown if refresh is enabled.

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.

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.

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?

Implement and maintain state — This question tests Implement and maintain state — Read the scenario before looking for a memorised answer..

What is the correct answer to this question?

The correct answer is: The state file has not been refreshed since the manual AMI change; it still reflects the old AMI — If the state shows the old AMI, but the actual instance has a different AMI, the state is stale. A `terraform refresh` or apply should detect drift. Option C correctly identifies that the state has not been refreshed.

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 →

How Courseiva writes practice questions · Editorial policy

Same concept, more angles

1 more ways this is tested on TF-003

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. A user runs `terraform plan` and notices that the plan includes 'Outgoing changes' for a number of resources that were not modified in the configuration. What is the most likely cause?

hard
  • A.The provider version has changed.
  • B.The resources were manually changed in the cloud provider.
  • C.The backend configuration changed.
  • D.The state file is outdated and needs to be refreshed.

Why D: `terraform plan` compares configuration to state. If state is outdated (e.g., after manual changes), plan will show drift even without config changes. Option A correct. Option B could cause, but less likely. Option C is possible but most likely state is not refreshed. Option D unrelated.

Last reviewed: Jun 24, 2026

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.

Loading comments…

Sign in to join the discussion.

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.