- A
source = "hashicorp/consul"
Why wrong: This is missing the provider component (e.g., /aws, /azurerm).
- B
source = "github.com/hashicorp/terraform-aws-consul"
Why wrong: This is a Git source, not a registry module reference.
- C
source = "hashicorp/consul/aws"
This is a valid registry module reference with namespace, module, and provider.
- D
source = "terraform-aws-modules/vpc/aws"
This is a valid registry module reference from the terraform-aws-modules namespace.
- E
source = "./modules/consul"
Why wrong: This is a local path source, not a registry module.
Quick Answer
The correct answers are the module references using the format `terraform-aws-modules/vpc/aws` and `hashicorp/consul/aws`. This is because the Terraform Registry enforces a strict three-part source format of `<namespace>/<module>/<provider>`, where the namespace identifies the organization, the module is the specific repository name, and the provider denotes the target infrastructure platform. On the HashiCorp Terraform Associate TF-003 exam, this question tests your ability to distinguish between valid registry references and other source types like Git URLs or local file paths, which are common traps. A frequent mistake is omitting the provider segment or confusing a registry path with a version constraint syntax. To remember the pattern, think of it as a three-layer address: who made it, what it does, and where it runs.
TF-003 Interact with Terraform modules Practice Question
This TF-003 practice question tests your understanding of interact with terraform modules. Match the stated requirement to the specific cloud service, access model, or configuration option — many options are valid in isolation but not for this scenario. 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 TWO of the following are valid ways to reference a module from the Terraform Registry?
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
source = "hashicorp/consul/aws"
Options A and C are correct because the Terraform Registry uses the format <namespace>/<module>/<provider>. Option A (hashicorp/consul/aws) and C (terraform-aws-modules/vpc/aws) follow this pattern. Option B is a Git URL. Option D is a local path. Option E is missing the provider component.
Key principle: NAT direction and interface roles matter as much as the IP address mapping. Inside/outside designation controls which traffic is translated.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
source = "hashicorp/consul"
Why it's wrong here
This is missing the provider component (e.g., /aws, /azurerm).
- ✗
source = "github.com/hashicorp/terraform-aws-consul"
Why it's wrong here
This is a Git source, not a registry module reference.
- ✓
source = "hashicorp/consul/aws"
Why this is correct
This is a valid registry module reference with namespace, module, and provider.
Related concept
Static NAT maps one inside address to one outside address.
- ✓
source = "terraform-aws-modules/vpc/aws"
Why this is correct
This is a valid registry module reference from the terraform-aws-modules namespace.
Related concept
Static NAT maps one inside address to one outside address.
- ✗
source = "./modules/consul"
Why it's wrong here
This is a local path source, not a registry module.
Common exam traps
Common exam trap: NAT rules depend on direction and matching traffic
NAT is not only about the public address. The inside/outside interface roles and the ACL or rule that matches traffic are just as important.
Detailed technical explanation
How to think about this question
NAT questions usually test address translation, overload/PAT behaviour, static mappings and whether the right traffic is being translated. Read the interface direction and address terms carefully.
KKey Concepts to Remember
- Static NAT maps one inside address to one outside address.
- PAT allows many inside hosts to share one public address using ports.
- Inside local and inside global describe the private and translated addresses.
- NAT ACLs identify traffic for translation, not always security filtering.
TExam Day Tips
- Identify inside and outside interfaces first.
- Check whether the scenario needs static NAT, dynamic NAT or PAT.
- Do not confuse NAT matching ACLs with normal packet-filtering intent.
Key takeaway
NAT direction and interface roles matter as much as the IP address mapping. Inside/outside designation controls which traffic is translated.
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.
Review the four NAT address types (inside local, inside global, outside local, outside global), PAT port overload, and static vs dynamic NAT use cases. Then practise related TF-003 NAT questions on configuration and troubleshooting.
- →
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
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?
Interact with Terraform modules — This question tests Interact with Terraform modules — Static NAT maps one inside address to one outside address..
What is the correct answer to this question?
The correct answer is: source = "hashicorp/consul/aws" — Options A and C are correct because the Terraform Registry uses the format <namespace>/<module>/<provider>. Option A (hashicorp/consul/aws) and C (terraform-aws-modules/vpc/aws) follow this pattern. Option B is a Git URL. Option D is a local path. Option E is missing the provider component.
What should I do if I get this TF-003 question wrong?
Review the four NAT address types (inside local, inside global, outside local, outside global), PAT port overload, and static vs dynamic NAT use cases. Then practise related TF-003 NAT questions on configuration and troubleshooting.
What is the key concept behind this question?
Static NAT maps one inside address to one outside address.
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 →
Keep practising
More TF-003 practice questions
- Which TWO statements accurately describe the purpose of Terraform? (Choose two.)
- A team is evaluating Terraform for managing their multi-cloud infrastructure. Which TWO statements accurately describe T…
- Which TWO of the following are valid use cases for using Terraform Cloud's Sentinel policies? (Choose two.)
- Match each Terraform function to its category.
- Match each Terraform provisioner to its typical use case.
- Match each Terraform meta-argument to its purpose.
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.