- A
module "vpc" { source = "./vpc" } module "app" { source = "./app" subnet_id = module.vpc.outputs.subnet_id }
Why wrong: .outputs is not part of the syntax; it's just module.name.output.
- B
module "vpc" { source = "./vpc" } module "app" { source = "./app" subnet_id = vpc.output.subnet_id }
Why wrong: Incorrect syntax for referencing output; should be module.vpc.subnet_id.
- C
module "vpc" { source = "./vpc" } module "app" { source = "./app" subnet_id = module.vpc.subnet_id }
Correctly references VPC module output.
- D
module "app" { source = "./app" subnet_id = module.vpc.subnet_id }
Why wrong: Missing the vpc module definition, causing a reference error.
Quick Answer
The correct choice is B, because Terraform accesses module outputs using the syntax module.module_name.output_name, allowing you to pass outputs between modules seamlessly. When you define a VPC module and an app module, the app module can reference the VPC module’s output—such as subnet_id—by writing subnet_id = module.vpc.subnet_id, which creates a clean dependency chain. On the HashiCorp Terraform Associate TF-003 exam, this concept tests your understanding of inter-module communication and the module output attribute pattern, a frequent topic in questions about reusing infrastructure across environments. A common trap is confusing module outputs with resource attributes or forgetting to declare the source module first; options A and C use incorrect syntax like module.vpc.outputs.subnet_id or resource references, while D omits the VPC module definition entirely. To remember this, think of the module as a black box with labeled outputs—just call module.name.output_name, like accessing a property on an object.
TF-003 Read, generate and modify configuration Practice Question
This TF-003 practice question tests your understanding of read, generate and modify configuration. 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.
A team wants to reuse a VPC module across multiple environments. They need to pass outputs from one module as inputs to another. Which configuration is correct?
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
module "vpc" { source = "./vpc" } module "app" { source = "./app" subnet_id = module.vpc.subnet_id }
Correct B: module outputs are accessed as module.module_name.output_name. A and C use incorrect syntax, D misses the VPC module definition.
Key principle: Count usable hosts — not total addresses — and remember that the network and broadcast addresses are not available to hosts in standard IPv4 subnets.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
module "vpc" { source = "./vpc" } module "app" { source = "./app" subnet_id = module.vpc.outputs.subnet_id }
Why it's wrong here
.outputs is not part of the syntax; it's just module.name.output.
- ✗
module "vpc" { source = "./vpc" } module "app" { source = "./app" subnet_id = vpc.output.subnet_id }
Why it's wrong here
Incorrect syntax for referencing output; should be module.vpc.subnet_id.
- ✓
module "vpc" { source = "./vpc" } module "app" { source = "./app" subnet_id = module.vpc.subnet_id }
Why this is correct
Correctly references VPC module output.
Related concept
CIDR notation defines the prefix length.
- ✗
module "app" { source = "./app" subnet_id = module.vpc.subnet_id }
Why it's wrong here
Missing the vpc module definition, causing a reference error.
Common exam traps
Common exam trap: usable hosts are not the same as total addresses
Subnetting questions often tempt you into counting all addresses. In normal IPv4 subnets, the network and broadcast addresses are not usable host addresses.
Trap categories for this question
Command / output trap
.outputs is not part of the syntax; it's just module.name.output.
Detailed technical explanation
How to think about this question
Subnetting questions test whether you can identify the network, broadcast address, usable range, mask and correct subnet. Slow down enough to calculate the block size correctly.
KKey Concepts to Remember
- CIDR notation defines the prefix length.
- Block size helps identify subnet boundaries.
- Network and broadcast addresses are not usable hosts in normal IPv4 subnets.
- The required host count determines the smallest suitable subnet.
TExam Day Tips
- Write the block size before choosing the subnet.
- Check whether the question asks for hosts, subnets or a specific address range.
- Do not confuse /24, /25, /26 and /27 host counts.
Key takeaway
Count usable hosts — not total addresses — and remember that the network and broadcast addresses are not available to hosts in standard IPv4 subnets.
Real-world example
How this comes up in practice
A network engineer segments a warehouse floor into three subnets: 20 scanners, 5 printers, and 2 management hosts. Picking the wrong mask wastes addresses or leaves too few usable hosts. Exam questions test whether you can apply CIDR notation, calculate block size, and identify the correct usable-host range for a given prefix.
What to study next
Got this wrong? Here's your next step.
Review block sizes, usable host formulas (2^n − 2), and how to find network and broadcast addresses for /24 through /30. Then practise related TF-003 subnetting questions on CIDR, address ranges, and subnet selection.
- →
Read, generate and modify configuration — study guide chapter
Learn the concepts, then practise the questions
- →
Read, generate and modify configuration 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?
Read, generate and modify configuration — This question tests Read, generate and modify configuration — CIDR notation defines the prefix length..
What is the correct answer to this question?
The correct answer is: module "vpc" { source = "./vpc" } module "app" { source = "./app" subnet_id = module.vpc.subnet_id } — Correct B: module outputs are accessed as module.module_name.output_name. A and C use incorrect syntax, D misses the VPC module definition.
What should I do if I get this TF-003 question wrong?
Review block sizes, usable host formulas (2^n − 2), and how to find network and broadcast addresses for /24 through /30. Then practise related TF-003 subnetting questions on CIDR, address ranges, and subnet selection.
What is the key concept behind this question?
CIDR notation defines the prefix length.
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.