The correct answer is partial configuration with a backend block that uses dynamic workspace references. This Terraform feature allows different backends per workspace by letting you omit certain backend arguments—like the storage bucket or state file path—and supply them dynamically at initialization time using `-backend-config` flags or workspace-specific variables. For example, a backend block with `key = "${var.env}/terraform.tfstate"` resolves to a unique path per workspace, enabling production and development to store state in entirely separate backends without hardcoding. On the HashiCorp Terraform Associate TF-003 exam, this tests your understanding of workspace isolation and backend flexibility; a common trap is assuming each workspace must share the same backend type. Remember: partial configuration means you leave the backend “unfinished” so each workspace can fill in its own details. Memory tip: think of it like a blank address label—each workspace writes its own destination.
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.
A team uses Terraform Cloud workspaces to manage multiple environments. They notice that the state file for the production workspace is stored in a different backend than the development workspace. Which Terraform feature allows different workspaces to use different backends?
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Using partial configuration with a backend block that has dynamic workspace references
Option C is correct because Terraform supports partial backend configuration, where the backend block can omit certain arguments (like the bucket or path) and those values can be supplied dynamically at initialization time. By using a backend block with dynamic workspace references (e.g., `key = "${var.env}/terraform.tfstate"`), each workspace can resolve to a different storage path or even a different backend type when combined with workspace-specific `-backend-config` files. This allows the production and development workspaces to store their state in entirely different backends without hardcoding the configuration.
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.
✗
Using the -backend-config flag
Why it's wrong here
While -backend-config can override backend config, it's not workspace-specific unless combined with workspace-specific variables.
✗
Using the backend block with a workspace key
Why it's wrong here
Backend blocks do not have a workspace key; workspaces are handled separately.
✓
Using partial configuration with a backend block that has dynamic workspace references
Why this is correct
Partial configuration allows injecting workspace-specific values like bucket keys.
Related concept
Read the scenario before looking for a memorised answer.
✗
Using a remote backend type
Why it's wrong here
Remote backends support workspaces but do not automatically use different backends per workspace.
Common exam traps
Common exam trap: answer the scenario, not the keyword
The trap here is that candidates often confuse the `-backend-config` flag (which supplies values to a single backend) with the ability to switch between entirely different backends per workspace, when in fact the dynamic workspace references in the backend block are what enable that per-workspace backend differentiation.
Detailed technical explanation
How to think about this question
Under the hood, partial configuration works by allowing the backend block to declare a `config` path or inline partial settings, and then at `terraform init`, you supply the remaining values via `-backend-config` flags or a separate configuration file. A common real-world scenario is using a single Terraform configuration with a backend block that references a workspace-specific key (e.g., `key = "env:${terraform.workspace}/state"`), enabling each workspace to store state in a different S3 bucket prefix or different GCS bucket. This approach avoids duplicating backend blocks across environments while maintaining isolation.
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 small business has 20 workstations on the 192.168.1.0/24 network and one public IP from its ISP. The router uses PAT (NAT overload) so all 20 devices share one public address using different source ports. NAT questions test whether you understand the four address terms and which direction each translation applies.
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.
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: Using partial configuration with a backend block that has dynamic workspace references — Option C is correct because Terraform supports partial backend configuration, where the backend block can omit certain arguments (like the bucket or path) and those values can be supplied dynamically at initialization time. By using a backend block with dynamic workspace references (e.g., `key = "${var.env}/terraform.tfstate"`), each workspace can resolve to a different storage path or even a different backend type when combined with workspace-specific `-backend-config` files. This allows the production and development workspaces to store their state in entirely different backends without hardcoding the configuration.
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.