TF-TA004 HashiCorp Terraform Associate (004)
- Vendor
- HashiCorp
- Level
- Associate
- Questions
- 50
- Time
- 60 min
- Domains
- 8
- In the bank
- 326
Practice 326 questionsTake a timed mock examDay-by-day study plan
Guides for this exam
- Terraform Associate (004) Study Guide: Configuration, State and Real Infrastructure, and Which Command Touches Which · 한국어
- Terraform State Backends and Workspaces: Local vs Remote, CLI vs HCP Terraform, and Which One a Question Wants · 한국어
The exam at a glance
| Level | Associate |
|---|---|
| Questions | 50 |
| Time | 60 minutes (about 1.2 minutes per question) |
| Passing mark | Not published by the vendor |
Domains and weights
The vendor does not publish domain weights for this exam, so the shares below are equal by assumption. Treat every domain as roughly the same size.
| Domain | Weight | Practice questions here |
|---|---|---|
| D1 · Infrastructure as Code (IaC) with Terraform | 12.5% | 38 |
| D2 · Terraform fundamentals | 12.5% | 38 |
| D3 · Core Terraform workflow | 12.5% | 39 |
| D4 · Terraform configuration | 12.5% | 57 |
| D5 · Terraform modules | 12.5% | 38 |
| D6 · Terraform state management | 12.5% | 39 |
| D7 · Maintain infrastructure with Terraform | 12.5% | 39 |
| D8 · HCP Terraform | 12.5% | 38 |
61 of the 326 practice questions (19%) ask for more than one answer.
D1 · Infrastructure as Code (IaC) with Terraform 12.5%
As the entry point of the exam, this domain checks the ideas behind infrastructure as code more than syntax. Items ask what Terraform is for, how it works across platforms, and which of its parts (providers, modules, HCL, state) plays which role. Distractors often stretch Terraform into jobs it does not do, such as managing software inside servers.
What to watch for
- Keep the roles apart: providers translate resources into API calls, modules package reusable configuration, and state records what Terraform manages.
- When a stem talks about many clouds, the shared part is the workflow and language. Resource types still belong to each provider.
- Watch for in-guest tasks like installing packages or editing config files. Those point to configuration management tools rather than to Terraform.
Tasks in the official exam guide (3)
D2 · Terraform fundamentals 12.5%
Fundamentals covers providers and state at a practical level. You read a short configuration and say which provider configuration a resource uses, which version a constraint selects, what a lock file error means, or what state adds beyond the code. Correct answers follow Terraform's documented rules exactly, while wrong ones rely on intuition about "latest" or "default".
What to watch for
- For version constraints, apply every condition together and then take the newest version that passes all of them, unless a lock file already fixes the choice.
- A resource without a provider argument uses the default configuration; only an explicit alias reference selects another one.
- State holds what configuration cannot: the link from each instance to its real object ID, plus metadata such as recorded dependencies.
Tasks in the official exam guide (4)
D3 · Core Terraform workflow 12.5%
Questions walk through write, plan and apply, then ask about the flags that change each step: init upgrades, formatting gates in CI, saved plans, targets and refresh options. Each scenario has a goal such as "do not change files" or "apply exactly what was reviewed". The right flag meets that goal, and close alternatives either do too much or quietly skip a safety check.
What to watch for
- Planning options belong on the plan command. A saved plan file already holds its decisions, so apply rejects added planning flags.
- A formatting gate in CI should report problems without rewriting files and should cover subfolders, which takes two separate options.
- Skipping refresh makes plans faster but blind to changes made outside Terraform. Refresh-only does the opposite: it updates state and changes nothing real.
Tasks in the official exam guide (7)
D4 · Terraform configuration 12.5%
Configuration items are the most hands-on in this exam. They show resource, data, variable and local blocks, and ask how to reference an instance, what an expression evaluates to, when a data source is read, or when a validation runs. Precise reading of the snippet matters, because the distractors are usually near-miss syntax or a wrong step in the run order.
What to watch for
- Address for_each instances by key and count instances by index. The brackets look similar, but the value inside them differs.
- When a data source depends on a value not known yet, expect its read to move to the apply phase and its attributes to show as known after apply.
- Compare secret handling options by where the value ends up. Ephemeral resources keep it out of state and plans, while ordinary data sources store their results.
Tasks in the official exam guide (8)
- 4.1 Use and differentiate resource and data blocks
- 4.2 Refer to resource attributes and create cross-resource references
- 4.3 Use variables and outputs
- 4.4 Understand and use complex types
- 4.5 Write dynamic configuration using expressions and functions
- 4.6 Define resource dependencies (depends_on, create_before_destroy)
- 4.7 Validate configuration using custom conditions
- 4.8 Manage sensitive data, ephemeral values and secrets (Vault)
D5 · Terraform modules 12.5%
Module scenarios focus on boundaries and sources. You decide how values cross into and out of a child module, how to order a module after a resource it does not reference, where init places downloaded code, and how tightly a source is pinned. Options that assume a module can see the caller's variables or resources directly are common traps.
What to watch for
- Only arguments in the module block go in, and only outputs come out. Anything else inside another module is out of reach.
- If ordering matters but no attribute links the two, an explicit depends_on on the module block is the tool to consider.
- Judge module proposals by the abstraction they add. A thin wrapper that passes every argument through unchanged adds a layer without real value.
Tasks in the official exam guide (4)
D6 · Terraform state management 12.5%
State management is tested through operational situations: locking without extra services, objects deleted outside Terraform, stuck locks, local backend behavior and saved plans that fail later. You pick the setting or command that keeps state consistent with reality without risking corruption. Unsafe shortcuts, such as unlocking another person's live run, appear often as attractive wrong answers.
What to watch for
- Know what each refresh option touches: refresh-only rewrites state to match reality and leaves real objects alone, so a later normal plan may recreate missing ones.
- Force-unlock is a recovery tool for a stale lock you own. Using it to bypass a running operation risks several writers on one state.
- A saved plan carries backend settings with it. Short-lived backend credentials are safer passed through environment variables.
Tasks in the official exam guide (4)
D7 · Maintain infrastructure with Terraform 12.5%
Maintenance items check that you can import, inspect and debug without causing damage. Scenarios include binding existing objects, reading state with scripts, changing log levels and sharing command output. The correct option is usually the read-only or narrowly scoped one; distractors either change more than needed or overlook that some outputs reveal sensitive values in plain text.
What to watch for
- Bind every real object to one resource address only. Two addresses for one object leads to conflicting actions later.
- Separate state subcommands that read from those that modify; only the modifying ones write backups, and none of them change real infrastructure.
- Treat machine-readable state output as secret material. Sensitive values that are hidden in normal CLI output can appear there unmasked.
Tasks in the official exam guide (3)
D8 · HCP Terraform 12.5%
This domain describes everyday use of HCP Terraform: VCS-driven runs, workspace variables, team permissions, cloud block settings and policy enforcement. Each stem names an action, such as opening a pull request or failing a policy, and asks what the platform does next. Knowing the default behavior of each workflow separates the right option from plausible guesses.
What to watch for
- Link the event to the run type: a pull request gives a plan that cannot be applied, while a merge to the tracked branch starts a normal run.
- Sensitive workspace variables can be replaced but never read back. They can still leak if the configuration exposes them in state or logs.
- Team access adds up across organization, project and workspace levels, so the broadest grant decides what a team can actually do.
Tasks in the official exam guide (4)
A study order that works
The 18-day study plan for TF-TA004 takes the domains in this order. Each day has a short reading, key terms and a quiz from the bank.
- Day 1: D1 · Infrastructure as Code (IaC) with Terraform
- Days 2–3: D2 · Terraform fundamentals
- Days 4–6: D3 · Core Terraform workflow
- Days 7–11: D4 · Terraform configuration
- Day 12: D5 · Terraform modules
- Days 13–14: D6 · Terraform state management
- Day 15: D7 · Maintain infrastructure with Terraform
- Days 16–17: D8 · HCP Terraform
- Day 18: Final Review: Exam Format, the Eight Objectives, Commonly Confused Pairs and Test-Day Plan
Recent changes to these questions
- : 2 answer choice sets changed, 2 answer keys corrected, 2 explanations rewritten
- : 60 questions added
- : 1 explanation rewritten
- : 3 answer choice sets changed, 3 answer keys corrected, 3 explanations rewritten
- : 3 explanations rewritten
About these questions
Every question is original, written from the public exam guide and checked against the vendor's own documentation. None comes from a real exam. Each one has an explanation of why the answer is right and why the other options are wrong. How the questions are written.