- A
Refactor into multiple Terraform modules and use a single root module
Why wrong: Incorrect. Modules within a single root module still result in one state file and one plan/apply cycle.
- B
Split the configuration into separate root modules, each with its own state file, and use data sources to share outputs
Correct. This is the recommended pattern for large infrastructures: each root module manages a subset of resources with its own state, reducing plan time and limiting the impact of changes.
- C
Use Terraform workspaces to separate environments
Why wrong: Incorrect. Workspaces separate state but still manage all resources in one state file; they don't reduce blast radius or improve single state file performance.
- D
Use terraform state mv to reorganize resources into different state files
Why wrong: Incorrect. state mv moves resources between state files but does not refactor the configuration; it's a manual operation for state management, not a design approach.
TF-003 Understand Terraform basics Practice Question
This TF-003 practice question tests your understanding of understand terraform basics. 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 has a monolithic Terraform configuration that manages all infrastructure. As the infrastructure grows, plan and apply times become very long. They want to break the configuration into smaller, independent units to improve performance and reduce blast radius. Which approach should they take?
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
Split the configuration into separate root modules, each with its own state file, and use data sources to share outputs
Splitting into separate root modules, each with its own state file, and using data sources to share outputs, is the recommended approach for reducing blast radius and improving performance. This allows independent plan/apply cycles and smaller state files.
Key principle: Authentication proves identity; authorization controls what that identity can do after login. Both must work for full privileged access.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Refactor into multiple Terraform modules and use a single root module
Why it's wrong here
Incorrect. Modules within a single root module still result in one state file and one plan/apply cycle.
- ✓
Split the configuration into separate root modules, each with its own state file, and use data sources to share outputs
Why this is correct
Correct. This is the recommended pattern for large infrastructures: each root module manages a subset of resources with its own state, reducing plan time and limiting the impact of changes.
Related concept
Authentication checks who the user is.
- ✗
Use Terraform workspaces to separate environments
Why it's wrong here
Incorrect. Workspaces separate state but still manage all resources in one state file; they don't reduce blast radius or improve single state file performance.
- ✗
Use terraform state mv to reorganize resources into different state files
Why it's wrong here
Incorrect. state mv moves resources between state files but does not refactor the configuration; it's a manual operation for state management, not a design approach.
Common exam traps
Common exam trap: authentication is not authorization
Logging in proves the user can authenticate. It does not automatically mean the user is allowed to enter privileged or configuration mode. Watch for AAA authorization, privilege level and command authorization details.
Detailed technical explanation
How to think about this question
This kind of question is testing the difference between identity and permission. A user may successfully log in to a router because authentication is working, but still fail to enter configuration mode because authorization is missing, misconfigured or mapped to a lower privilege level.
KKey Concepts to Remember
- Authentication checks who the user is.
- Authorization controls what the user is allowed to do after login.
- Privilege levels affect access to EXEC and configuration commands.
- AAA, TACACS+ and RADIUS can separate login success from command access.
TExam Day Tips
- Do not assume successful login means full administrative access.
- Look for words such as cannot enter configuration mode, privilege level, authorization or command access.
- Separate login problems from permission problems before choosing the answer.
Key takeaway
Authentication proves identity; authorization controls what that identity can do after login. Both must work for full privileged access.
Real-world example
How this comes up in practice
A junior network technician can log in to a core router but cannot reach the enable prompt or configuration mode. The AAA server is authenticating the login — but the authorisation policy only grants privilege level 1, not 15. Authentication (who you are) is working; authorisation (what you can do) is not.
What to study next
Got this wrong? Here's your next step.
Review Cisco AAA concepts — authentication, authorization, and accounting. Study privilege levels (0–15), command authorization under TACACS+, and how RADIUS differs. Then practise related TF-003 questions on access control and AAA configuration.
- →
Understand Terraform basics — study guide chapter
Learn the concepts, then practise the questions
- →
Understand Terraform basics 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?
Understand Terraform basics — This question tests Understand Terraform basics — Authentication checks who the user is..
What is the correct answer to this question?
The correct answer is: Split the configuration into separate root modules, each with its own state file, and use data sources to share outputs — Splitting into separate root modules, each with its own state file, and using data sources to share outputs, is the recommended approach for reducing blast radius and improving performance. This allows independent plan/apply cycles and smaller state files.
What should I do if I get this TF-003 question wrong?
Review Cisco AAA concepts — authentication, authorization, and accounting. Study privilege levels (0–15), command authorization under TACACS+, and how RADIUS differs. Then practise related TF-003 questions on access control and AAA configuration.
What is the key concept behind this question?
Authentication checks who the user is.
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 24, 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.