Terraform Certification in 2026: New Exam, IBM Ownership, and a Real Community Split
If you’re studying for HashiCorp’s Terraform Associate certification right now, you’re studying for a tool that changed hands, changed license, and is currently losing a measurable chunk of its user base to a fork — all while the certification itself just got a content refresh. None of that is a reason to skip certifying, but it’s worth understanding before you commit study time.
What Actually Changed in the Exam Itself
Terraform Associate 003 retired January 7, 2026. Version 004 launched January 8, 2026, testing Terraform 1.12 and reflecting how teams actually use Terraform today rather than the patterns current when 003 was written. Key additions in 004 include:
- Custom conditions for validation and precondition/postcondition checks.
- Ephemeral and write-only values — safer handling of sensitive data that shouldn’t persist in state.
- HCP Terraform projects — organizational structure for managing workspaces at scale.
If your existing 003 credential is still active, nothing forces you to retest — it remains valid for its full two-year term from your pass date. When it’s time to renew, you’ll recertify on whatever version is current at that point, which today means 004.
The Backdrop You Should Actually Know About
Here’s what makes this certification different from a routine version bump: HashiCorp itself has changed ownership and licensing terms in ways that are actively reshaping its user community.
- IBM completed its $6.4 billion acquisition of HashiCorp in early 2025, and as of September 2025, all HashiCorp business operations formally transitioned to IBM. Product names are being renamed into IBM’s Automation portfolio branding over time.
- Terraform itself has operated under the Business Source License (BSL) since August 2023 — a more restrictive license than the open-source model that built Terraform’s original ecosystem dominance.
- The combination has pushed a real, measurable slice of the user base to reconsider: surveys show roughly 38% of Terraform users are actively evaluating or migrating to alternatives. The leading destination is OpenTofu, the open-source fork, which has seen triple-digit annual download growth and Linux Foundation backing — not a fringe project.
- Separately, HashiCorp/IBM ended external language support for Terraform’s Cloud Development Kit (CDKTF), pushing teams that had built workflows in Python or TypeScript toward HCL-only configuration going forward.
- HCP Terraform’s free tier was also restructured in 2026 — the legacy free plan ended March 31, 2026, replaced by a capped tier (500 managed resources), part of a broader pattern of previously-free features moving behind paywalls since the IBM acquisition closed.
Does This Mean Skip the Certification?
No — and here’s the honest reasoning why, not just reassurance:
The certification tracks the tool employers are actually using today, regardless of where the ecosystem sentiment is heading. Terraform’s job-posting dominance hasn’t evaporated just because a vocal segment of the community is evaluating alternatives — OpenTofu’s growth is real, but it hasn’t displaced Terraform in enterprise environments at a scale that shows up in hiring requirements yet. A certification validates current market reality, not where a technology might be in three years.
Your Terraform skills mostly transfer if the ecosystem does shift. OpenTofu maintains roughly 95%+ feature parity with Terraform and uses the same HCL syntax. If you’re worried about betting on the “wrong” tool, the honest answer is that the underlying skill — writing and managing infrastructure as code in HCL, understanding state, modules, and provider ecosystems — is not tool-specific in practice, even though the certification badge is.
The uncertainty is real, but it’s a “watch this” situation, not a “avoid this” one. If you’re already deep into Terraform at work, certifying makes sense regardless of the ownership drama — you’re validating skills you’re using daily. If you’re choosing an IaC tool to learn from scratch with zero existing investment, it’s fair to weigh OpenTofu as a genuine alternative given the licensing and ownership trajectory — but that’s a different decision than “should I certify in the tool my job already requires.”
What to Actually Do
If you’re studying for Terraform Associate right now: keep going. Study the 004 objectives (custom conditions, ephemeral values, HCP Terraform projects specifically — these are the parts most likely to trip up candidates who only reviewed 003-era material).
If you haven’t started and are choosing between Terraform and OpenTofu from scratch: check what your target employers actually list in job postings before deciding — this is a case where the job market, not certification-body politics, should drive the choice.
Either way: don’t let the IBM/BSL/OpenTofu conversation talk you out of a certification that still maps directly to current job requirements. Skill portability between Terraform and OpenTofu is high enough that this isn’t the high-stakes bet it might feel like from the outside.
Bottom Line
Terraform Associate 004 is a legitimate, current certification worth pursuing if Terraform is what your job (or target job) actually uses — the community uncertainty around IBM’s ownership and the OpenTofu fork is real and worth tracking, but it hasn’t reached the point where it should change your certification plans today.
DailyDebian’s Terraform Associate 004 question set is built around the current exam blueprint, including the new custom conditions and ephemeral values content.