Question 85 of 519
Use Terraform outside the core workflowhardMultiple ChoiceObjective-mapped

Quick Answer

The correct answer is to split the configuration into separate directories per account and resource type, and use remote state sharing. This approach directly addresses the need to decompose monolithic Terraform configurations by breaking the codebase into independent, manageable parts while maintaining coordination through shared state backends. On the HashiCorp Terraform Associate TF-003 exam, this question tests your understanding of refactoring patterns and workspace limitations—many candidates mistakenly think Terraform Cloud workspaces alone solve code coupling, but workspaces only isolate state, not code logic. A common trap is assuming that a single configuration with many workspaces or a single mega-module reduces complexity; in reality, both increase tight coupling and cognitive load. Remember the memory tip: “Split by account and type, share state to stay tight.”

TF-003 Use Terraform outside the core workflow Practice Question

This TF-003 practice question tests your understanding of use terraform outside the core workflow. 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 has a monolithic Terraform configuration managing multiple AWS accounts. They want to decompose it into smaller configurations that can be managed independently. What is the recommended strategy?

Question 1hardmultiple choice
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

Split the configuration into separate directories per account and resource type, and use remote state sharing.

Option D is correct because splitting by account and resource type into separate workspaces or directories is a common pattern. Option A is wrong because using a single configuration with many workspaces still has tight coupling. Option B is wrong because pulling all into one module increases complexity. Option C is wrong because Terraform Cloud workspaces alone do not decompose the code.

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.

  • Split the configuration into separate directories per account and resource type, and use remote state sharing.

    Why this is correct

    This allows independent management and collaboration.

    Related concept

    Static NAT maps one inside address to one outside address.

  • Use Terraform workspaces to separate environments within the same configuration.

    Why it's wrong here

    Workspaces help with state separation, not code decomposition.

  • Create a single super-module that contains all resources.

    Why it's wrong here

    This increases complexity, not decomposition.

  • Move everything to Terraform Cloud and use different workspaces.

    Why it's wrong here

    Still single configuration; not decomposed.

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.

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?

Use Terraform outside the core workflow — This question tests Use Terraform outside the core workflow — Static NAT maps one inside address to one outside address..

What is the correct answer to this question?

The correct answer is: Split the configuration into separate directories per account and resource type, and use remote state sharing. — Option D is correct because splitting by account and resource type into separate workspaces or directories is a common pattern. Option A is wrong because using a single configuration with many workspaces still has tight coupling. Option B is wrong because pulling all into one module increases complexity. Option C is wrong because Terraform Cloud workspaces alone do not decompose the code.

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 →

How Courseiva writes practice questions · Editorial policy

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.

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.