cert-bank

Exams

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

The exam at a glance

LevelAssociate
Questions50
Time60 minutes (about 1.2 minutes per question)
Passing markNot 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.

DomainWeightPractice questions here
D1 · Infrastructure as Code (IaC) with Terraform12.5%38
D2 · Terraform fundamentals12.5%38
D3 · Core Terraform workflow12.5%39
D4 · Terraform configuration12.5%57
D5 · Terraform modules12.5%38
D6 · Terraform state management12.5%39
D7 · Maintain infrastructure with Terraform12.5%39
D8 · HCP Terraform12.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

Tasks in the official exam guide (3)
  • 1.1 Explain what IaC is
  • 1.2 Describe the advantages of IaC patterns
  • 1.3 Explain how Terraform manages multi-cloud, hybrid cloud, and service-agnostic workflows

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

Tasks in the official exam guide (4)
  • 2.1 Install and version Terraform providers
  • 2.2 Describe how Terraform uses providers
  • 2.3 Write Terraform configuration using multiple providers
  • 2.4 Explain how Terraform uses and manages state

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

Tasks in the official exam guide (7)
  • 3.1 Describe the Terraform workflow
  • 3.2 Initialize a Terraform working directory
  • 3.3 Validate a Terraform configuration
  • 3.4 Generate and review an execution plan
  • 3.5 Apply changes to infrastructure
  • 3.6 Destroy Terraform-managed infrastructure
  • 3.7 Apply formatting and style adjustments

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

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

Tasks in the official exam guide (4)
  • 5.1 Explain how Terraform sources modules
  • 5.2 Describe variable scope within modules
  • 5.3 Use modules in configuration
  • 5.4 Manage module versions

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

Tasks in the official exam guide (4)
  • 6.1 Describe the local backend
  • 6.2 Describe state locking
  • 6.3 Configure remote state with the backend block
  • 6.4 Manage resource drift and Terraform state

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

Tasks in the official exam guide (3)
  • 7.1 Import existing infrastructure
  • 7.2 Use the CLI to inspect state
  • 7.3 Describe when and how to use verbose logging

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

Tasks in the official exam guide (4)
  • 8.1 Use HCP Terraform to create infrastructure
  • 8.2 Describe HCP Terraform collaboration and governance features
  • 8.3 Organize and use HCP Terraform workspaces and projects
  • 8.4 Configure and use HCP Terraform integration

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.

  1. Day 1: D1 · Infrastructure as Code (IaC) with Terraform
  2. Days 2–3: D2 · Terraform fundamentals
  3. Days 4–6: D3 · Core Terraform workflow
  4. Days 7–11: D4 · Terraform configuration
  5. Day 12: D5 · Terraform modules
  6. Days 13–14: D6 · Terraform state management
  7. Day 15: D7 · Maintain infrastructure with Terraform
  8. Days 16–17: D8 · HCP Terraform
  9. Day 18: Final Review: Exam Format, the Eight Objectives, Commonly Confused Pairs and Test-Day Plan

Recent changes to these questions

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.