- A
In the count or for_each of another module or resource.
Module outputs can control the number of instances or the iteration set of other resources.
- B
In a resource argument, e.g., subnet_id = module.vpc.public_subnet_ids
Directly using module outputs in resource arguments is the most common use case.
- C
In a data source definition as a filter.
Why wrong: Data sources query external data; they cannot directly reference module outputs from the same configuration.
- D
In a provider block to set endpoints.
Why wrong: Provider configurations are static and cannot reference interpolations from module outputs.
- E
In a locals block to perform transformations.
Locals can use module outputs to derive new local values.
Quick Answer
The answer is in a locals block to perform transformations, as well as direct references in resource arguments and use in count or for_each arguments. This is correct because module output values are exported attributes that behave like any other expression in Terraform, allowing them to be consumed wherever a value is expected within the same configuration—except where the language explicitly restricts them. On the HashiCorp Terraform Associate TF-003 exam, this question tests your understanding of the dependency graph and where expressions resolve; a common trap is assuming module outputs can feed into provider configurations or data sources, but those blocks require static, hard-coded values or variables, not dynamic references. To remember this, think of module outputs as "read-only variables" that flow into resources, meta-arguments, and locals, but stop short of providers and data sources. A useful mnemonic is "RLD": Resources, Locals, and count/for_each Dependencies—those are the valid homes for module output references.
TF-003 Interact with Terraform modules Practice Question
This TF-003 practice question tests your understanding of interact with terraform modules. 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 ways to reference a module output value within the same Terraform configuration?
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
In the count or for_each of another module or resource.
Options A, B, and D are correct. A: Direct reference in resource arguments. B: Use in count or for_each arguments of resources. D: Use in locals block for complex expressions. C is wrong because module outputs aren't used in provider configurations. E is wrong because data sources are for external data, not module outputs.
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.
- ✓
In the count or for_each of another module or resource.
Why this is correct
Module outputs can control the number of instances or the iteration set of other resources.
Related concept
CIDR notation defines the prefix length.
- ✓
In a resource argument, e.g., subnet_id = module.vpc.public_subnet_ids
Why this is correct
Directly using module outputs in resource arguments is the most common use case.
Related concept
CIDR notation defines the prefix length.
- ✗
In a data source definition as a filter.
Why it's wrong here
Data sources query external data; they cannot directly reference module outputs from the same configuration.
- ✗
In a provider block to set endpoints.
Why it's wrong here
Provider configurations are static and cannot reference interpolations from module outputs.
- ✓
In a locals block to perform transformations.
Why this is correct
Locals can use module outputs to derive new local values.
Related concept
CIDR notation defines the prefix length.
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
Data sources query external data; they cannot directly reference module outputs from the same configuration.
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.
- →
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 — CIDR notation defines the prefix length..
What is the correct answer to this question?
The correct answer is: In the count or for_each of another module or resource. — Options A, B, and D are correct. A: Direct reference in resource arguments. B: Use in count or for_each arguments of resources. D: Use in locals block for complex expressions. C is wrong because module outputs aren't used in provider configurations. E is wrong because data sources are for external data, not module outputs.
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.