EnglishDeutschFrançaisEspañolPortuguês

HashiCorp · HC-TFA · Associate

HashiCorp Terraform Associate (004) — Practice Questions and Mock Exam

Practice with realistic HC-TFA questions aligned to the exam objectives. Alex explains every answer, and your readiness score shows what to study next.

57Questions
60minTime Limit

Checked against HashiCorp · August 2026Current exam version

About the exam

The HashiCorp Certified: Terraform Associate (004) credential validates foundational proficiency in infrastructure as code using Terraform. It confirms that you understand the purpose of IaC, can author and apply Terraform configurations, manage state, use modules, and work with providers to provision resources across cloud and on-premises environments. The exam covers eight domains spanning core workflow, state management, HCP Terraform basics, and the rationale behind declarative infrastructure.

This certification targets cloud engineers, DevOps practitioners, site reliability engineers, and platform teams who are new to Terraform or have been using it informally for six months or less. It is also a strong fit for system administrators transitioning into infrastructure automation, and for developers who need a baseline understanding before collaborating with platform teams on shared Terraform codebases.

What's on the exam

All eight domains sit within a single point of each other, 12–13%, so no section is safe to skip. IaC concepts and Terraform fundamentals open the exam at 13% each, followed by the core workflow of init, plan, apply, and destroy, and by the configuration syntax that drives it: resources, variables, expressions, and dependency handling, also at 13% each.

Modules, state management, maintaining infrastructure, and HCP Terraform close out the blueprint at 12% apiece, covering module sourcing and versioning, remote backends and drift, importing existing resources, and HCP Terraform's collaboration and governance capabilities. The flat weighting means depth matters less than breadth here — a candidate strong on configuration syntax but weak on state locking or HCP Terraform workspaces still has a quarter of the exam exposed.

Exam blueprint: HC-TFA

Infrastructure as Code (IaC) with Terraform13%

IaC concepts, advantages of IaC patterns, multi-cloud and hybrid cloud workflows.

≈ 5 h
Terraform Fundamentals14%

Providers installation and versioning, how Terraform uses providers, state management basics.

≈ 5 h
Core Terraform Workflow13%

Init, validate, plan, apply, destroy, fmt. The standard Terraform workflow.

≈ 5 h
Terraform Configuration13%

Resources, data sources, variables, outputs, complex types, expressions, functions, dependencies, custom conditions, sensitive data management.

≈ 5 h
Terraform Modules11%

Module sources, variable scope within modules, using modules in configuration, version management.

≈ 5 h
Terraform State Management12%

Local backend, state locking, remote state configuration, resource drift management.

≈ 5 h
Maintain Infrastructure with Terraform12%

Importing existing infrastructure, CLI state inspection, verbose logging and debugging.

≈ 5 h
HCP Terraform13%

HCP Terraform for infrastructure creation, collaboration and governance features, workspaces and projects, integration configuration.

≈ 5 h

HashiCorp doesn't publish domain weights for this exam — the shares below reflect our exam-aligned question pool, and shift as the pool grows.

Exam format and question types

The Terraform Associate exam runs 57 questions in 60 minutes, mixing true/false, single-select multiple-choice, and multiple-answer formats with no live lab component. Many items show CLI output or an HCL snippet and ask which command, block, or behavior is correct, rewarding the ability to predict a plan's outcome from configuration rather than recall command syntax in isolation.

Question types: HC-TFA

Multiple Choice60%

Pick the single best answer from four or five options — the exam's bread and butter.

Multiple Response25%

More than one answer is correct and you need all of them; the question tells you how many to pick.

True / False15%

Judge a single statement as true or false — quick points, but the exact wording decides.

HashiCorp confirms these question types — a percentage split is not published; the shares reflect our exam-aligned question pool.

Try five HC-TFA questions

Five questions straight from our HashiCorp Certified: Terraform Associate (004) pool. Answer one — Alex explains the why.

Terraform Fundamentals2 / 5

A developer adds a new provider requirement to a configuration and runs terraform plan, but receives an error stating the required provider plugin is not installed. What is the correct command to install the provider and prepare the working directory?

AlexFull explanation from Alex

terraform init is the first command you run in any new or changed configuration. It performs several initialization tasks: it configures the backend for state storage, downloads and installs the provider plugins declared in required_providers, downloads any referenced modules, and creates or updates the .terraform.lock.hcl dependency lock file. When a provider requirement is added or changed, you must re-run init so Terraform can fetch the appropriate plugin version that satisfies your version constraints. Other commands like validate, plan, and apply assume providers are already installed. Exam tip: any error about a missing provider, module, or backend almost always means you need to run terraform init.

Sourcedeveloper.hashicorp.com

Terraform Modules3 / 5

Which `source` value in a `module` block references a module whose files live in a sibling directory of the calling configuration?

AlexFull explanation from Alex

Terraform treats any source starting with ./ or ../ as a local filesystem path relative to the calling module's directory. The value ../network resolves to a sibling directory one level up. Local modules are read directly from disk with no download or caching required. (Ref: developer.hashicorp.com/terraform/language/modules/sources#local-paths) Distractors: “"hashicorp/network/aws"”) hashicorp/network/aws is Terraform Registry shorthand syntax. “"git::network"”) git::network is an incomplete/invalid Git URL source. “"registry:network"”) registry:network is not a supported source scheme.

Sourcedocs.hashicorp.com

Core Terraform Workflow4 / 5

A user wants `terraform apply` to execute without pausing to ask for interactive confirmation. Which option accomplishes this?

AlexFull explanation from Alex

The -auto-approve flag tells terraform apply to skip the interactive confirmation prompt and immediately execute the plan. This is the standard flag for CI/CD pipelines and automation. Terraform uses single-dash flags (e.g., -auto-approve), not GNU-style double-dash options. (Ref: developer.hashicorp.com/terraform/cli/commands/apply#auto-approve) Distractors: “`terraform apply --force`”) --force is not valid; -force was once used with terraform destroy but is deprecated in favor of -auto-approve. “`terraform apply --skip-confirm`”) --skip-confirm does not exist in Terraform. “`terraform apply --yes`”) --yes does not exist in Terraform.

Sourcedeveloper.hashicorp.com

HCP Terraform5 / 5

In HCP Terraform, what is the effect of setting a workspace's execution mode to `local`?

AlexFull explanation from Alex

Setting execution mode to local in HCP Terraform means terraform plan and terraform apply run on the operator's own CLI while HCP Terraform serves as the remote state backend (and optionally variables store). This contrasts with remote mode (HCP workers execute) and agent mode (self-hosted agents execute). (Ref: developer.hashicorp.com/terraform/cloud-docs/workspaces/settings#execution-mode) Distractors: “Plans and applies run on HCP Terraform but logs stay…”) Logs appear on the local CLI, not stored remotely. “The HCP Terraform UI runs plans…”) HCP Terraform never runs plans in the browser. “The workspace can only run speculative plans triggered…”) Speculative VCS plans are independent of execution mode.

Sourcedeveloper.hashicorp.com

384 questions, built like the exam

Every domain of the HC-TFA exam has enough questions in the pool to practice it in depth. A mock exam asks 57 questions in one sitting, on the same 60-minute clock as the real thing.

Audit record: HC-TFA

Spec check against HashiCorpAugust 6, 2026

last verified against the official HashiCorp source

Blueprint coverage37 official objectives

across 8 domains, from the official exam guide

Pool size384 questions

= 6 full practice exams of 57 questions each — never the same question twice

Domain coverageall 8 domains at official weight

Infrastructure as Code (IaC) with Terraform 50 · Terraform Fundamentals 52 · Core Terraform Workflow 49 · Terraform Configuration 49 · Terraform Modules 44 · Terraform State Management 45 · Maintain Infrastructure with Terraform 46 · HCP Terraform 49

Canonically validated384 of 384

each verified against official HashiCorp documentation — answer, options and explanation, source cited

Methodology openly documented.How questions are made →

Preparing for HC-TFA

How long you'll need depends on how much hands-on experience you bring. The rest is set by the vendor: how the exam is delivered, how soon you can retake it, and how long the credential stays valid.

The exam is delivered online through Certiverse with a live proctor. The credential holds for two years; renewing means passing the current Associate exam again, or passing the Professional exam to extend it.

Your plan: HC-TFA

Preparation

Study time25–60 h

typically around 25 h if you already work with this stack, around 60 h coming to it fresh

LevelAssociate
Worth having firstBasic terminal skills. Understanding of on-premises and cloud architecture. Professional experience recommended but not required.

Exam day & after

DeliveryOnline proctored via Certiverse
Retake policyFree retake not included. Standard retake available after waiting period.
Stays valid2 years

Pass the current version of the Terraform Associate exam or pass the Terraform Professional exam to extend credentials.

The hours are our own planning estimate — HashiCorp publishes no preparation time for this exam. A starting point for your calendar, not a target.

Common pitfalls

Terraform Associate questions reward an accurate mental model of state over configuration muscle memory — predicting what a plan will do to existing infrastructure rather than what the HCL alone implies. The gap shows up hardest around state operations: commands that only touch the state file look identical to commands that touch live infrastructure until a candidate has broken and repaired a state file at least once. Provider and variable configuration hide similar traps, where a block landing in the wrong place or an inverted precedence order produces a plan that looks correct until it runs.

Watch list: HC-TFA

  1. 01State locking

    Forgetting that local state has no locking; only remote backends like S3+DynamoDB or HCP Terraform lock state during concurrent operations.

  2. 02terraform import

    Import only populates state, not configuration. You must still write matching HCL by hand or the next plan proposes destroying the resource.

  3. 03Provider versioning

    required_providers goes in the terraform block, not the provider block. Missing version constraints let provider upgrades break the plan without warning.

  4. 04Variable precedence

    Order: env vars < terraform.tfvars < *.auto.tfvars < -var/-var-file CLI. Candidates often invert the precedence on the exam.

  5. 05count vs for_each

    count uses numeric indexes, so removing a middle item shifts all others; for_each keys by string and avoids accidental resource recreation.

Pass-IT trains you on exactly these weak spots — adaptive & spaced →

Frequently asked questions

How long is the HashiCorp Certified: Terraform Associate (004) exam?

The HashiCorp Certified: Terraform Associate (004) exam has 57 questions and a 60-minute time limit.

What are common mistakes on the HashiCorp Certified: Terraform Associate (004) exam?

Common pitfalls include: State locking, terraform import, Provider versioning, Variable precedence, count vs for_each. Focus study time on these areas to avoid losing points.

How is the Terraform Associate exam weighted?

It is the flattest weighting in our catalog: eight objectives, none above 13% and none below 12%. Infrastructure as code, Terraform fundamentals, the core workflow and configuration each take 13%, with modules, state, maintenance and HCP Terraform at 12%. There is no domain worth skipping and none worth over-investing in.

What do you need before the Terraform Associate exam?

Basic terminal skills and an understanding of on-premises and cloud architecture. HashiCorp recommends professional experience but does not require it, and no certification gates the booking. The catalog budget is around 40 hours, which is short because the exam stays close to the core workflow.

How long is the Terraform Associate valid?

Two years. You renew by passing the current version of the Associate exam again, or by passing the Terraform Authoring and Operations Professional exam, which extends the credential instead. There is no credit or continuing-education route.

What comes after the Terraform Associate?

The Terraform Authoring and Operations Professional exam is the direct step up, and it is a different kind of test: four hours long and built around dynamic configuration, module design and collaborative workflows. Passing it also renews your Associate credential. The Vault Associate exam is the sideways move if secrets management is becoming part of the job.

Pass-IT is an independent study tool, not affiliated with or endorsed by HashiCorp; HashiCorp and exam names are trademarks of their respective owners.

One certification. One payment.

Full HC-TFA access

Get the full question pool for this certification. Alex explains every answer, and your readiness score shows what to work on next.

Buy HC-TFA access for $29.99One payment. Lifetime access to this certification.
Take the free readiness check20 questions. No card. See what to study before you buy.

Reach 80% readiness and pass — or your money back.

How the score works →