Question 146 of 519
Interact with Terraform moduleshardMultiple SelectObjective-mapped

Quick Answer

The answer is to output important resource attributes that consumers may need, as this aligns with the single-responsibility principle where each Terraform module should encapsulate a clear, focused purpose such as provisioning a VPC or an EC2 instance. By exposing only necessary outputs, you keep modules reusable, testable, and easy to compose, avoiding brittle, hard-to-maintain code that tries to do too much. On the HashiCorp Terraform Associate TF-003 exam, this concept tests your understanding of module composition and abstraction, often appearing in a "select three" format where distractors include overly broad outputs or hardcoding values. A common trap is thinking you should output everything for flexibility, but best practices for Terraform modules emphasize minimal, intentional outputs that consumers actually need. Remember the mnemonic "S.O.S." — Single responsibility, Output essentials, Stay abstract.

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 THREE practices are recommended when using Terraform modules? (Select THREE.)

Question 1hardmulti select
Full question →

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

Design modules to have a single clear purpose.

Option A is correct because Terraform modules should follow the single-responsibility principle: each module should encapsulate a clear, focused purpose (e.g., provisioning a VPC, an EC2 instance, or a database). This makes modules reusable, testable, and easier to compose. A module that tries to do too many things becomes brittle and hard to maintain.

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.

  • Design modules to have a single clear purpose.

    Why this is correct

    Single-responsibility modules are easier to reuse and test.

    Related concept

    Read the scenario before looking for a memorised answer.

  • Use version constraints when referencing modules from a registry.

    Why this is correct

    Version pinning prevents breaking changes.

    Related concept

    Read the scenario before looking for a memorised answer.

  • Output important resource attributes that consumers may need.

    Why this is correct

    Outputs allow consumers to access created resources.

    Related concept

    Read the scenario before looking for a memorised answer.

  • Hardcode provider-specific details like region inside the module to simplify usage.

    Why it's wrong here

    Hardcoding reduces reusability; pass such details as variables.

  • Create a new module for each individual resource type.

    Why it's wrong here

    Modules should group related resources, not be created for each resource.

Common exam traps

Common exam trap: answer the scenario, not the keyword

HashiCorp often tests the misconception that modules should be as granular as possible (one per resource type) or that hardcoding provider details simplifies usage, when in fact both practices reduce reusability and violate Terraform best practices.

Detailed technical explanation

How to think about this question

Under the hood, Terraform modules are just directories of `.tf` files that can be called with `module` blocks. When you use version constraints (e.g., `source = "hashicorp/consul/aws"` with `version = "~> 1.0"`), Terraform resolves the module version from the registry using semantic versioning, ensuring deterministic builds. Outputting resource attributes (e.g., `output "instance_id" { value = aws_instance.web.id }`) allows consumers to reference those values without hardcoding, enabling cross-module data flow and dependency management.

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.

TExam Day Tips

  • 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 exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.

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.

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 — Read the scenario before looking for a memorised answer..

What is the correct answer to this question?

The correct answer is: Design modules to have a single clear purpose. — Option A is correct because Terraform modules should follow the single-responsibility principle: each module should encapsulate a clear, focused purpose (e.g., provisioning a VPC, an EC2 instance, or a database). This makes modules reusable, testable, and easier to compose. A module that tries to do too many things becomes brittle and hard to maintain.

What should I do if I get this TF-003 question wrong?

Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.

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 →

How Courseiva writes practice questions · Editorial policy

Last reviewed: Jun 30, 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.

Loading comments…

Sign in to join the discussion.

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.