Quick Answer
The answer is providers.tf, as it is the only file not required in a Terraform module. A module inherits provider configurations from the root configuration, meaning it does not need its own providers.tf to define providers; instead, it relies on the parent module’s provider block to establish connections to cloud providers or services. The three files that are essential for a standard module are main.tf (for resource definitions), variables.tf (to accept input values), and outputs.tf (to return results), which together form the minimum file requirements for a Terraform module. On the HashiCorp Terraform Associate TF-003 exam, this question tests your understanding of module composition and the separation of provider configuration from reusable module logic—a common trap is assuming every Terraform directory needs a providers.tf, when in fact modules are designed to be provider-agnostic. A useful memory tip: think of a module as a function that receives inputs and returns outputs, but does not own the infrastructure provider—that belongs to the root module.
This TF-003 practice question tests your understanding of interact with terraform modules. 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.
Which of the following files is NOT required in a Terraform module?
Clue words in this question
Noticing these words before you look at the options changes how you read each choice.
Clue: "NOT"
Why it matters: Negative qualifier — you are looking for the one option that does NOT apply. Most options will be true; only one is false for this scenario.
providers.tf
A module does not need its own providers.tf; it uses the provider configuration from the root module.
outputs.tf
Why wrong: outputs.tf is recommended to expose values from the module.
variables.tf
Why wrong: variables.tf is required to declare input variables for the module.
main.tf
Why wrong: main.tf is typically used to define resources and is expected in a module.
Answer choices
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
providers.tf
Option D is correct because a module does not require its own providers.tf; it inherits provider configurations from the root module. Options A, B, and C are all standard files commonly found in a module (main.tf, variables.tf, outputs.tf).
Key principle: Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
Answer analysis
For each option: why learners choose it and why it is or isn't the right answer here.
providers.tf
Why this is correct
A module does not need its own providers.tf; it uses the provider configuration from the root module.
Clue confirmation
The clue word "NOT" in the question point toward this answer.
Related concept
Read the scenario before looking for a memorised answer.
outputs.tf
Why it's wrong here
outputs.tf is recommended to expose values from the module.
variables.tf
Why it's wrong here
variables.tf is required to declare input variables for the module.
main.tf
Why it's wrong here
main.tf is typically used to define resources and is expected in a module.
Common exam traps
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
outputs.tf is recommended to expose values from the module.
Detailed technical explanation
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.
Key takeaway
Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
Real-world example
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
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.
Interact with Terraform modules — study guide chapter
Learn the concepts, then practise the questions
Interact with Terraform modules 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
Use these pages to review the topic behind this question. This is how one missed question becomes focused revision.
Practise TF-003 questions linked to Understand IaC concepts.
Practise TF-003 questions linked to Understand Terraform basics.
Practise TF-003 questions linked to Understand Terraform's purpose.
Practise TF-003 questions linked to Use Terraform outside the core workflow.
Practise TF-003 questions linked to Interact with Terraform modules.
Practise TF-003 questions linked to Use the core Terraform workflow.
Practise TF-003 questions linked to Implement and maintain state.
Practise TF-003 questions linked to Read, generate and modify configuration.
Practise TF-003 questions linked to TF-003 fundamentals.
Practise TF-003 questions linked to TF-003 scenario.
Practise TF-003 questions linked to TF-003 troubleshooting.
Practice this exam
Short sessions build daily habit. Longer sessions build exam-day stamina. Try a timed session to simulate real conditions.
FAQ
Interact with Terraform modules — This question tests Interact with Terraform modules — Read the scenario before looking for a memorised answer..
The correct answer is: providers.tf — Option D is correct because a module does not require its own providers.tf; it inherits provider configurations from the root module. Options A, B, and C are all standard files commonly found in a module (main.tf, variables.tf, outputs.tf).
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.
Yes — watch for: "NOT". Negative qualifier — you are looking for the one option that does NOT apply. Most options will be true; only one is false for this scenario.
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 →
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.