Terraform Associate 003 vs 004: what changed in January 2026
HashiCorp retired Terraform Associate 003 on January 8, 2026 and replaced it with the 004 version. Here's what's new and what to study.
HashiCorp retired the Terraform Associate (003) exam on January 8, 2026 and replaced it with the (004) version on the same day. If you scheduled a 003 attempt before that date you got to keep it; if you didn't, the only path now is 004. The cert ID is "HashiCorp Certified: Terraform Associate (004)" and the cert itself is still called "Terraform Associate" without a version on the badge β versions only matter at exam time.
There's a second change that's almost more impactful than the curriculum update: HashiCorp moved exam delivery from PSI to Certiverse with the 004 launch. Same online-proctored format conceptually, but the software is different, the check-in flow is different, and the keyboard shortcuts you might have memorized for PSI no longer apply. More on that below.
Background context worth knowing: IBM acquired HashiCorp. Announced April 2024, closed February 2025. The cert program kept HashiCorp branding through 2025 and into 2026 β IBM hasn't (yet) folded it into the IBM credentialing system. As of April 2026 the certs still live at developer.hashicorp.com/certifications. That may change.
What's new on the 004
HashiCorp added or expanded five areas:
Stacks. The big one. Stacks is HashiCorp's answer to multi-environment, multi-component orchestration β basically a way to declare "here are the components in this system, here are the deployments, here's how they depend on each other" without rolling your own wrapper. Stacks went GA in HCP Terraform in 2024 and the 004 exam tests Stacks vocabulary, the deployment lifecycle, and basic configuration. Don't expect deep authoring questions; expect "what does this Stacks block do" and "when would you use a Stack vs a workspace."
No-code modules. The ability to publish a module that platform teams can deploy via UI without writing HCL. The 004 expects you to know what no-code modules are, how they're published, and the difference between a no-code module and a regular registry module.
Run tasks. Webhook-based external integrations into the Terraform plan/apply lifecycle. Run tasks were technically available before 004 but weren't on the 003 curriculum. They're on 004 β what they do, when they fire, how they integrate with policy.
Drift detection. HCP Terraform's drift detection is now in scope. The exam tests what drift detection does, when it runs, what "managed resources changed outside Terraform" means, and the basic remediation flow.
Sentinel-as-policy and policy sets. Sentinel was on 003 lightly. On 004 it's expanded β policy sets, enforcement levels (advisory, soft-mandatory, hard-mandatory), the difference between Sentinel and OPA-via-run-tasks, and the workflow for applying policies across workspaces.
The 004 also rewrites the workflow content to assume HCP Terraform / Terraform Enterprise rather than just CLI workflows. CLI workflows are still tested but the share dropped.
What carried over from 003
A lot, honestly. The fundamentals are basically unchanged:
- Terraform language basics: providers, resources, data sources, variables, outputs, locals, expressions, functions, dynamic blocks.
- State management: local state, remote state, state locking,
terraform statesubcommands, the implications of corrupted state. - Modules: authoring, the registry, versioning, the public registry vs private registry.
- Provisioners (still discouraged, still tested).
- Workspaces (CLI and HCP varieties).
- Init / plan / apply / destroy lifecycle.
- The execution graph, dependency resolution,
depends_on.
If you studied 003 and didn't sit it before January 8, the good news is most of your prep transfers. Add 15β25 hours on the new content (Stacks, no-code modules, run tasks, drift detection, expanded Sentinel) and you're ready.
PSI to Certiverse: what's actually different
I've sat exams on both. The differences aren't huge but they're real:
Check-in flow. Certiverse's onboarding is slightly faster β fewer ID-photo retakes, less "please rotate your laptop to show the corners of the room three times." Both still scan your face, ID, and workspace. Both still want a clear desk and no second monitor.
The exam interface. Certiverse's question UI is cleaner. Flagging questions for review works similarly. The progress indicator is better. The web-based interface uses standard browser shortcuts; PSI's locked-down environment had its own quirks. People who memorized PSI's tab-flagging keys will need to relearn.
Calculator and notes. Certiverse provides an in-browser scratch pad. PSI required either a digital whiteboard plugin or no scratch at all. For Terraform Associate, scratch is rarely useful β you're not doing math. But if you like to outline, the scratch pad is there.
Reschedule policy. Slightly more lenient on Certiverse β 24 hours before the exam vs PSI's 48-hour window. Don't rely on this; the policy can change.
System requirements. Certiverse runs in the browser. PSI required a downloadable secure browser. If you've fought PSI Bridge with corporate-laptop antivirus before, Certiverse will be a relief.
The shift is positive overall in my opinion. The exam content is what's hard, not the platform β but a less-hostile platform reduces incidental stress on test day.
The exam mechanics on 004
- 57 questions (mix of multiple-choice, multiple-response, fill-in-the-blank, matching).
- 60 minutes.
- $70.50 USD plus tax.
- Passing score isn't published (HashiCorp doesn't disclose; community estimate ~70%).
- Online via Certiverse.
- Validity: 2 years.
- One retake allowed after 24 hours; subsequent retakes require 14-day waits.
There's no free retake bundled. If you fail, you pay another $70.50. That's still cheap compared to AWS / Azure / GCP exams ($165β$300) and very cheap compared to CNCF exams ($250β$445). Affordability is one of the things HashiCorp got right with this cert.
Study time and resources
Realistic study time for 004:
- Daily Terraform user: 15β25 hours over 2β3 weeks. Most of the time goes to reading the new-content docs (Stacks, run tasks) and doing 200β300 practice questions to verify exam-pattern recognition.
- Occasional Terraform user: 40β60 hours over 5β6 weeks. You'll need to revisit state management, modules, and HCP Terraform features that you don't touch in regular work.
- New to Terraform: 80β120 hours over 8β10 weeks. Read the official docs at developer.hashicorp.com/terraform/docs end to end. Build a real project (multi-environment AWS or Azure setup) before you sit the exam.
Resources that work: the official HashiCorp study guide is updated for 004 and free. The HashiCorp Learn tutorials cover most of what's on the exam, structured by topic. Practice question banks are essential for exam-pattern familiarity β the question style is HashiCorp-specific and you'll move faster on the live exam if you've seen the patterns.
The 003-era books (Sander van Vugt, the in Action series) are mostly still useful for fundamentals. They don't cover Stacks, no-code modules, or expanded Sentinel β supplement those with the official docs.
Should you take it now or wait?
Take it now if you work with Terraform. The 004 isn't likely to be replaced for at least 2 years, and the cert is cheap and respected. The Sentinel and HCP Terraform content advantage you with platform-engineering interviews where IaC governance comes up.
Wait if you don't currently use Terraform but think you will in 6+ months. Study the certification when you have a real project to ground the concepts in β book learning Terraform without using it leaves you with surface knowledge that fades fast.
Skip if your IaC tool is OpenTofu, Pulumi, or CloudFormation. There's overlap with Terraform but the cert specifically tests HashiCorp's product surface, including HCP Terraform features that don't exist on alternatives.
If you're going for it, browse the Terraform 004 practice bank on CertLabPro or start a timed exam. The question style is the part that benefits most from drill β content you can learn from docs, but pattern recognition under a clock you have to practice.