The answer is that the `required_providers` block is not declared in the root module. This is the most likely cause because Terraform’s provider installation logic is driven by the root module’s `required_providers` configuration; when a child module from the Registry declares a provider but the root module does not, `terraform init` may skip installing that provider, leading to a failure during `terraform plan`. On the HashiCorp Terraform Associate TF-003 exam, this concept tests your understanding of how Terraform aggregates provider requirements—the root module acts as the single source of truth for provider installation, and child module declarations alone are insufficient. A common trap is assuming that declaring a provider inside a module will automatically trigger its installation, but Terraform only installs providers explicitly required by the root module. Memory tip: think of the root module as the “gatekeeper” for providers—if it doesn’t list a provider, that provider won’t be installed, no matter what child modules request.
TF-003 Understand Terraform basics Practice Question
This TF-003 practice question tests your understanding of understand terraform basics. The scenario asks you to isolate a root cause — eliminate options that address a different problem before choosing. 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 Terraform configuration includes a module from the Terraform Registry. After running `terraform init`, the module is downloaded. However, a subsequent `terraform plan` fails with an error that a required provider is not installed, even though it is declared in the module. What is the most likely cause?
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.
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
The `required_providers` block is not declared in the root module
Option C is correct because in Terraform, the `required_providers` block must be declared in the root module to ensure all providers are installed during `terraform init`. When a module from the Registry declares a provider but the root module does not, `terraform init` may not automatically install that provider, leading to a 'required provider not installed' error during `terraform plan`. The root module acts as the top-level configuration that aggregates all provider requirements.
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.
✗
The module uses a different Terraform version
Why it's wrong here
Version mismatch would cause a different error.
✗
The provider version constraint is incompatible
Why it's wrong here
Would cause a different error during init or plan.
✓
The `required_providers` block is not declared in the root module
Why this is correct
Terraform may not install providers only declared in modules; root should also declare them.
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 module source URL is incorrect
Why it's wrong here
If init succeeded, the URL is correct.
Common exam traps
Common exam trap: answer the scenario, not the keyword
HashiCorp often tests the misconception that provider declarations in child modules are automatically inherited by the root module, leading candidates to overlook the necessity of a root-level `required_providers` block.
Detailed technical explanation
How to think about this question
Under the hood, `terraform init` reads the `required_providers` block from the root module to determine which providers to install. If a child module declares a provider not listed in the root module, Terraform will not install it unless the root module explicitly includes it, because provider installation is driven by the root configuration. In real-world scenarios, this often occurs when using community modules that require additional providers (e.g., `hashicorp/random`), and the root module omits the `required_providers` block entirely.
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.
Understand Terraform basics — This question tests Understand Terraform basics — Read the scenario before looking for a memorised answer..
What is the correct answer to this question?
The correct answer is: The `required_providers` block is not declared in the root module — Option C is correct because in Terraform, the `required_providers` block must be declared in the root module to ensure all providers are installed during `terraform init`. When a module from the Registry declares a provider but the root module does not, `terraform init` may not automatically install that provider, leading to a 'required provider not installed' error during `terraform plan`. The root module acts as the top-level configuration that aggregates all provider requirements.
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 →
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.