The correct answer is that when using for_each with modules, the module’s outputs become a map of output values keyed by the for_each keys. This occurs because for_each creates one module instance per key in the provided map or set, and each instance produces its own set of outputs; Terraform then collects all those outputs into a single map, using the original for_each keys as the map keys. On the HashiCorp Terraform Associate TF-003 exam, this concept tests your understanding of how for_each transforms module outputs, often appearing in questions that contrast for_each with count or that ask about output structure. A common trap is assuming outputs remain a simple list or single value, but the key insight is that for_each always yields a map. Remember: for_each keys become output map keys—think “key to key” to avoid confusion.
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.
You have a list of VPC configurations and want to create multiple VPCs using a single module block with for_each. Which statement is true?
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
When using for_each, the module's outputs will be a map of output values for each instance.
Option C is correct. When using for_each on a module block, the module's outputs become a map of output values keyed by the for_each keys. Option A is false; for_each works with any module. Option B is false; for_each does not require count support. Option D is false; for_each is supported on module blocks since Terraform 0.13.
Key principle: Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
✗
for_each on a module is not supported.
Why it's wrong here
for_each is supported on module blocks since Terraform 0.13.
✗
You can use for_each on a module block only if the module is published in the registry.
Why it's wrong here
for_each works with any module source, not just registry modules.
✓
When using for_each, the module's outputs will be a map of output values for each instance.
Why this is correct
Each instance's outputs are collected into a map with keys matching the for_each keys.
Related concept
Read the scenario before looking for a memorised answer.
✗
for_each on a module block requires the module to support count.
Why it's wrong here
for_each and count are separate mechanisms; a module does not need to support count to use for_each.
Common exam traps
Common exam trap: answer the scenario, not the keyword
Many certification questions include familiar terms but test a specific constraint. Read the exact wording before choosing an answer that is generally true but wrong for this case.
Detailed technical explanation
How to think about this question
This question should be treated as a scenario, not a definition check. Identify the problem, the constraint and the best action. Then compare each option against those facts.
KKey Concepts to Remember
Read the scenario before looking for a memorised answer.
Find the constraint that changes the correct option.
Eliminate answers that are true in general but not in this case.
Use explanations to understand the rule behind the answer.
TExam Day Tips
→Underline the problem statement mentally.
→Watch for words such as best, first, most likely and least administrative effort.
→Review why wrong options are wrong, not only why the correct option is correct.
Key takeaway
Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
Real-world example
How this comes up in practice
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
Got this wrong? Here's your next step.
Identify which TF-003 exam domain this question belongs to, then review the specific concept being tested. Practise related questions in that domain and focus on understanding why each wrong answer is tempting — not just why the correct answer is right.
Interact with Terraform modules — This question tests Interact with Terraform modules — Read the scenario before looking for a memorised answer..
What is the correct answer to this question?
The correct answer is: When using for_each, the module's outputs will be a map of output values for each instance. — Option C is correct. When using for_each on a module block, the module's outputs become a map of output values keyed by the for_each keys. Option A is false; for_each works with any module. Option B is false; for_each does not require count support. Option D is false; for_each is supported on module blocks since Terraform 0.13.
What should I do if I get this TF-003 question wrong?
Identify which TF-003 exam domain this question belongs to, then review the specific concept being tested. Practise related questions in that domain and focus on understanding why each wrong answer is tempting — not just why the correct answer is right.
What is the key concept behind this question?
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 →
These questions test the same concept from different angles. Work through them to make sure you can recognise it however the exam phrases it.
Variation 1. Given the plan output, how is the module 'instances' configured in the root module?
medium
✓ A.The root module uses for_each in the module block with a map variable.
B.The module uses count with a list variable.
C.The module is declared twice with different names.
D.The module contains a resource with for_each inside.
Why A: Option D is correct because for_each with a map creates one instance per key, and each instance can have different variables like ami and instance_type. Option A is wrong because count would show index numbers, not keys. Option B is wrong because using module multiple times would show different module addresses. Option C is wrong because a module with a single resource but for_each inside would still show one instance per key.
Last reviewed: Jun 24, 2026
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.
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.