TF-004 Understand Terraform basics Practice Question
Which two of the following are correct statements about Terraform providers?
⚠ Common exam trap
The trap is thinking providers must be manually declared in every configuration or that 'terraform plan' installs them; candidates often forget that 'terraform init' is the step that downloads providers.
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
✓
Providers are plugins that Terraform uses to manage resources.
Option B is correct because Terraform providers are plugins that implement the API interactions needed to create, read, update, and delete resources for a given platform or service, such as AWS, Azure, or Kubernetes. Option C is correct because providers are distributed and can be sourced from the Terraform Registry, which is the primary public repository for provider plugins and modules, and they are declared in the required_providers block with a source address. Option A is incorrect because a provider does not need to be explicitly defined in every configuration; Terraform can infer and use a default provider for a resource type, and the required_providers block is only needed when specifying a non-default source or version constraint. Option D is incorrect because a single Terraform configuration can use multiple providers simultaneously, and even multiple instances of the same provider via aliases. Option E is incorrect because providers are not automatically installed by terraform plan; installation occurs during terraform init, which downloads and installs the required provider plugins into the .terraform directory.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
A provider must be defined in every Terraform configuration.
Why it's wrong here
This statement is incorrect. A `provider` block is not universally mandatory in every Terraform configuration. It is only required if the configuration explicitly declares resources or data sources that belong to that specific provider. A configuration might exist solely to manage local files using the `local` provider, or even contain no resources at all (e.g., a module definition without direct resource declarations), thus not requiring a provider block.
- ✓
Providers are plugins that Terraform uses to manage resources.
Why this is correct
This statement is correct. Providers function as specialized plugins that extend Terraform's core capabilities, enabling it to interact with various cloud platforms, SaaS offerings, and on-premise infrastructure. Each provider implements a set of resource types and data sources, defining the API calls and logic necessary to create, read, update, and delete those specific infrastructure components.
- ✓
Providers can be sourced from the Terraform Registry.
Why this is correct
This statement is correct. The Terraform Registry serves as the primary and official repository for discovering and sourcing a vast array of Terraform providers, both official and community-contributed. When a `terraform init` command is executed, Terraform automatically downloads the specified providers from this registry, ensuring access to the necessary plugins for managing infrastructure.
- ✗
Only one provider can be used per configuration.
Why it's wrong here
This statement is incorrect. Terraform configurations are designed to be highly flexible and can seamlessly integrate multiple providers within a single codebase. For instance, a complex infrastructure setup might simultaneously provision resources in Amazon Web Services (AWS) using the AWS provider and manage DNS records in Google Cloud DNS using the GCP provider, all within the same root module or child modules.
- ✗
Providers are automatically installed by terraform plan.
Why it's wrong here
This statement is incorrect. Provider installation is a distinct phase handled exclusively by the `terraform init` command. This command initializes the working directory, downloading and configuring the necessary provider plugins based on the configuration's requirements. The `terraform plan` command, conversely, is responsible for generating an execution plan by comparing the desired state with the current state, and it assumes providers are already installed.
Go deeper
Related to this question
About these practice questions
Courseiva writes every TF-004 question from scratch — 434 in total, each with an explanation and a wrong-answer breakdown. None are copied from real exams or dumps. Learn why practice questions differ from exam dumps →
JA
Written and reviewed by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
Last reviewed September 2026 · checked against the official HashiCorp exam blueprint
This TF-004 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-004 exam.