HashiCorp Terraform Associate 003 exam guide covering IaC, workflow, config, state, modules, and HCP decisions.
This guide targets HashiCorp Certified: Terraform Associate (003) as a legacy-transfer guide rather than as a current live blueprint. As of April 14, 2026, HashiCorp’s current certification page lists Terraform Associate (004) as the active associate exam, testing Terraform 1.12 in an online-proctored 1 hour assessment priced at $70.50 USD in English with 2-year credential validity. That same current certification page also says that people who still hold an unexpired 002 or 003 Terraform Associate certification can pass the 004 version starting 6 months before expiration to extend or refresh their certification path. HashiCorp’s old certification-003 study, review, and sample-question routes still exist, but they now point to the current associate-prep materials rather than a frozen 003 archive. This guide turns that reality into something useful: a vendor-first way to make older 003 notes, practice sets, and concepts still usable.
State: Terraform’s record of the infrastructure objects it tracks and how they map to configuration.
Backend: Terraform setting that decides where state is stored and how collaboration or locking works.
| Exam fact | Current official signal |
|---|---|
| Active associate version on April 14, 2026 | 004 |
| Product version tested on the active exam | Terraform 1.12 |
| Current certification-page assessment label | multiple choice |
| Format | online proctored |
| Duration | 1 hour |
| Price | $70.50 USD, plus locally applicable taxes and fees |
| Language | English |
| Credential validity | 2 years |
| Legacy-holder path | unexpired 002 or 003 holders can take 004 starting 6 months before expiration |
| Guide model | 6 transfer chapters -> 12 section lessons |
This is not a vendor-published live 003 blueprint anymore, because HashiCorp no longer publishes one separately. Instead, this guide uses the durable Terraform Associate skill lanes that still survive in HashiCorp’s current associate prep materials: Terraform basics, core workflow, configuration, modules, state and maintenance, and HCP Terraform crossover. If you are using old 003 notes, that is the cleanest way to keep them useful.
003 notes or an older question bank into something current and usable.003 versus 004 status, legacy-holder paths, and common workflow/state confusion.certification-003 tutorial routes, and the core Terraform docs.HashiCorp’s current certification page and surviving associate-prep routes point to a durable Terraform Associate skill map even though 003 is no longer the active exam version. This guide follows that transfer model directly.
| Transfer lane | Chapter | Start here |
|---|---|---|
| Terraform purpose, IaC model, and baseline nouns | 1. Foundations | 1.1 IaC and What Still Transfers, 1.2 Providers, Plugins, and State Purpose |
| Core Terraform CLI workflow | 2. Workflow | 2.1 Init, Plan, Apply, and Destroy, 2.2 Fmt, Validate, and Safe Review |
| Reading and writing Terraform configuration | 3. Config | 3.1 Resources, Data, and Expressions, 3.2 Variables, Outputs, and Sensitive Values |
| Module usage and reuse | 4. Modules | 4.1 Module Sources and Interfaces, 4.2 Versioning and Reuse Discipline |
| State, backends, drift, and maintenance | 5. State & Maintenance | 5.1 Backends, Locking, and Workspaces, 5.2 Import, Drift, Replace, and Repair |
| HCP Terraform crossover | 6. HCP | 6.1 Remote Runs and Workspace Behavior, 6.2 Variables, Policy, and Integrations |
flowchart LR
A["1. Terraform purpose and durable nouns"] --> B["2. Core CLI workflow"]
B --> C["3. Configuration and module structure"]
C --> D["4. State, drift, and maintenance"]
D --> E["5. HCP Terraform crossover"]
E --> F["FAQ, glossary, and live HashiCorp checks"]
003 notes for durable concepts, not for frozen version wording| Failure pattern | Better instinct |
|---|---|
| treating Terraform like a bag of commands | start from configuration plus state plus workflow stage |
| mixing provider, backend, module, workspace, and project together | classify the noun before choosing the answer |
| assuming import means Terraform created the resource | import changes Terraform management, not infrastructure history |
using old 003 wording as if it were still the live blueprint |
use legacy notes for durable concepts and current pages for active facts |