Question 90 of 519
Use Terraform outside the core workfloweasyMultiple ChoiceObjective-mapped

Quick Answer

The answer is that the team did not migrate the existing production state into the 'prod' workspace. When they ran `terraform workspace new prod`, Terraform created a brand-new, empty state file for that workspace, completely separate from the original production state file stored in the old directory. Without explicitly migrating that existing state using `terraform workspace select prod` followed by `terraform state push` or by copying the state file into the workspace’s backend location, Terraform has no knowledge of the already-deployed production resources and therefore plans to recreate them. This scenario directly tests your understanding of Terraform workspaces as isolated state containers—a key concept on the HashiCorp Terraform Associate TF-003 exam. A common trap is assuming that creating a workspace with the same name as an existing environment automatically inherits its state; it does not. Remember the mnemonic: “New workspace, new state—migrate or recreate.”

TF-003 Use Terraform outside the core workflow Practice Question

This TF-003 practice question tests your understanding of use terraform outside the core 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 small startup is using Terraform to deploy AWS resources. They have two separate environments: development and production. Currently, they manage two sets of Terraform configuration files in different directories, each with its own state file stored locally. The CEO wants to reduce duplication and simplify management. The team decides to restructure into a single configuration with workspaces. After implementing workspaces, they run `terraform workspace new dev` and `terraform workspace new prod`, then `terraform apply` in the dev workspace. However, when they switch to prod and run `terraform apply`, the plan shows that Terraform wants to recreate all resources instead of managing the existing production resources. What is the most likely reason for this behavior?

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 1easymultiple choice
Full question →

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 team did not migrate the existing production state into the 'prod' workspace.

Option C is correct because when the team restructured into a single configuration with workspaces, they created new empty workspaces (`dev` and `prod`) but did not migrate the existing production state file into the `prod` workspace. Terraform workspaces maintain separate state files, so without importing the existing production state into the `prod` workspace, Terraform has no record of the existing production resources and plans to create them from scratch. The `terraform workspace new` command creates a fresh, empty state for that workspace.

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.

  • Workspaces cannot be used for different environments; only for temporary feature branches.

    Why it's wrong here

    Workspaces are commonly used for environment separation.

  • The Terraform configuration uses the same resource names in both workspaces, causing conflicts.

    Why it's wrong here

    Workspaces allow same resource names; state is separate.

  • The team did not migrate the existing production state into the 'prod' workspace.

    Why this is correct

    Workspaces have independent state; existing state must be imported or moved.

    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 team must configure a remote backend for workspaces to function correctly.

    Why it's wrong here

    Workspaces work with local state, though remote is recommended.

Common exam traps

Common exam trap: answer the scenario, not the keyword

HashiCorp often tests the misconception that workspaces automatically inherit or share state from previous configurations, when in fact each workspace starts with a completely empty state unless explicitly migrated.

Detailed technical explanation

How to think about this question

Under the hood, Terraform workspaces use separate state files stored in the backend's workspace directory (e.g., `terraform.tfstate.d/prod/` for local backends). When `terraform workspace new prod` is run, it creates an empty state file for that workspace. If the team had previously managed production resources with a separate local state file (e.g., `terraform.tfstate` in the production directory), they must copy or migrate that state into the new `prod` workspace's state file using `terraform workspace select prod` followed by `terraform state push` or by manually copying the state file. Without this step, Terraform has no knowledge of the existing production infrastructure and treats the configuration as a fresh deployment.

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.

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?

Use Terraform outside the core workflow — This question tests Use Terraform outside the core workflow — Read the scenario before looking for a memorised answer..

What is the correct answer to this question?

The correct answer is: The team did not migrate the existing production state into the 'prod' workspace. — Option C is correct because when the team restructured into a single configuration with workspaces, they created new empty workspaces (`dev` and `prod`) but did not migrate the existing production state file into the `prod` workspace. Terraform workspaces maintain separate state files, so without importing the existing production state into the `prod` workspace, Terraform has no record of the existing production resources and plans to create them from scratch. The `terraform workspace new` command creates a fresh, empty state for that workspace.

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". 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

Last reviewed: Jun 30, 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.