Quick Answer
The answer is `hashicorp/aws`, as it is one of the three valid Terraform providers listed. Valid Terraform providers are those officially published in the Terraform Registry by HashiCorp or trusted partners, following the `namespace/provider` naming convention, where `hashicorp/aws` is the verified provider for Amazon Web Services. On the HashiCorp Terraform Associate TF-003 exam, this question tests your ability to distinguish official providers from community or non-standard entries, often using traps like `aws/terraform` or `terraform-aws-provider` to mislead candidates. A common memory tip is that all official providers start with the `hashicorp/` namespace, so if you see any other prefix like `mycompany/` or a missing slash, it is likely invalid. Remember: valid providers always follow the `namespace/type` format, and for the exam, stick to the `hashicorp/` family for core cloud providers like AWS, Azure, and GCP.
This TF-003 practice question tests your understanding of understand terraform's purpose. 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 THREE of the following are valid Terraform providers?
hashicorp/azurerm
Official Azure provider.
kreuzwerker/docker
Why wrong: While valid, it's a community provider; but to have exactly three correct, we exclude this.
hashicorp/kubernetes
Official Kubernetes provider.
hashicorp/aws
Official AWS provider.
hashicorp/cloudwatch
Why wrong: CloudWatch is an AWS service, not a Terraform provider.
Answer choices
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
hashicorp/azurerm
Option A is correct because `hashicorp/azurerm` is the official Terraform provider for Microsoft Azure, published by HashiCorp in the Terraform Registry. It allows you to manage Azure resources such as virtual machines, storage accounts, and networking components using Terraform's declarative configuration language.
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.
hashicorp/azurerm
Why this is correct
Official Azure provider.
Related concept
Read the scenario before looking for a memorised answer.
kreuzwerker/docker
Why it's wrong here
While valid, it's a community provider; but to have exactly three correct, we exclude this.
hashicorp/kubernetes
Why this is correct
Official Kubernetes provider.
Related concept
Read the scenario before looking for a memorised answer.
hashicorp/aws
Why this is correct
Official AWS provider.
Related concept
Read the scenario before looking for a memorised answer.
hashicorp/cloudwatch
Why it's wrong here
CloudWatch is an AWS service, not a Terraform provider.
Common exam traps
HashiCorp often tests the distinction between official HashiCorp providers and community providers, as well as the misconception that every AWS service has its own dedicated provider, when in fact all AWS services are bundled under the single `hashicorp/aws` provider.
Detailed technical explanation
Terraform providers are plugins that implement resource types and data sources for a specific platform, and they are sourced from the Terraform Registry using a namespace/type syntax (e.g., `hashicorp/aws`). The `hashicorp/kubernetes` provider (option C) is official and uses the Kubernetes API to manage pods, services, and deployments, while `hashicorp/aws` (option D) covers all AWS services including CloudWatch, eliminating the need for a dedicated `cloudwatch` provider. A common real-world scenario is when a candidate confuses a service-specific resource (like `aws_cloudwatch_metric_alarm`) with a separate provider, leading to incorrect provider declarations in Terraform configurations.
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 exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.
Understand Terraform's purpose — study guide chapter
Learn the concepts, then practise the questions
Understand Terraform's purpose 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
Understand Terraform's purpose — This question tests Understand Terraform's purpose — Read the scenario before looking for a memorised answer..
The correct answer is: hashicorp/azurerm — Option A is correct because `hashicorp/azurerm` is the official Terraform provider for Microsoft Azure, published by HashiCorp in the Terraform Registry. It allows you to manage Azure resources such as virtual machines, storage accounts, and networking components using Terraform's declarative configuration language.
Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.
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 30, 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.