The answer is to use a separate DynamoDB table for each workspace to isolate locks. This solution directly addresses the core issue of state locking and workspace isolation: when a single DynamoDB table is shared across all workspaces, the lock key is identical, causing all `terraform apply` operations to contend for the same lock regardless of workspace. By provisioning a dedicated DynamoDB table per workspace, each workspace gets its own lock scope, allowing concurrent operations on different workspaces while still preventing simultaneous applies within the same workspace. On the HashiCorp Terraform Associate TF-003 exam, this scenario tests your understanding of how DynamoDB locking interacts with workspace isolation—a common trap is assuming a single table with a composite key suffices, but DynamoDB’s lock key must be unique per workspace. Remember the mnemonic: “One table per workspace, one lock per apply.”
TF-003 Understand IaC concepts Practice Question
This TF-003 practice question tests your understanding of understand iac concepts. 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 company manages a microservices application across multiple AWS accounts using Terraform. They have a dedicated 'infrastructure' repository with Terraform configurations for each account. The team recently migrated their Terraform state to a centralized S3 backend with DynamoDB locking. After the migration, they notice that when two developers run `terraform apply` simultaneously in the same workspace, one of them receives a lock error, but the other proceeds normally. The team wants to ensure that only one apply runs at a time across all workspaces. However, they also need to allow concurrent operations on different workspaces. The current backend configuration uses a single DynamoDB table for all workspaces. What should the team do to achieve their goals?
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Use a separate DynamoDB table for each workspace to isolate locks
The problem is that using a single DynamoDB table with a single lock key means all workspaces share the same lock, preventing concurrent applies on different workspaces. Option D is correct: Use a separate DynamoDB table for each workspace, which isolates locks per workspace. Option A is dangerous. Option B does not solve the cross-workspace contention because the lock key is shared. Option C loses centralized state.
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.
✗
Use a single DynamoDB table but increase the lock timeout
Why it's wrong here
Increasing timeout does not prevent contention across workspaces if the lock key is shared.
✗
Remove the backend configuration and use local state with manual locking
Why it's wrong here
Local state is not centralized and manual locking is error-prone.
✓
Use a separate DynamoDB table for each workspace to isolate locks
Why this is correct
Separate tables allow concurrent applies on different workspaces while maintaining locking per workspace.
Related concept
Read the scenario before looking for a memorised answer.
✗
Disable locking to allow parallel operations
Why it's wrong here
Disabling locking risks state corruption and conflicts.
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.
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.
Understand IaC concepts — This question tests Understand IaC concepts — Read the scenario before looking for a memorised answer..
What is the correct answer to this question?
The correct answer is: Use a separate DynamoDB table for each workspace to isolate locks — The problem is that using a single DynamoDB table with a single lock key means all workspaces share the same lock, preventing concurrent applies on different workspaces. Option D is correct: Use a separate DynamoDB table for each workspace, which isolates locks per workspace. Option A is dangerous. Option B does not solve the cross-workspace contention because the lock key is shared. Option C loses centralized state.
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.
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.