Hello, you are using an old browser that's unsafe and no longer supported. Please consider updating your browser to a newer version, or downloading a modern browser.
Everything you need to know about the Terraform Associate (004), the infrastructure as code credential from HashiCorp, as of September 2026. This guide covers the one hour multiple choice exam, the eight objectives HashiCorp publishes, the Terraform 1.12 version it tests, cost and validity, DoD 8140 status, the roles it fits, and how it compares with the CKA and the Azure Administrator (AZ-104).
The Terraform Associate is the credential for people who define cloud infrastructure in code. It is issued by HashiCorp, the company that builds Terraform, and the current exam is version 004.
It validates the day-to-day work of an infrastructure as code practitioner: explaining what IaC is and why teams adopt it, installing and versioning providers, running the init, validate, plan, apply and destroy workflow, writing configuration with variables, outputs, expressions and functions, sourcing and versioning modules, managing state in a remote backend, importing infrastructure that already exists, and working in HCP Terraform. The exam is multiple choice, delivered online with a proctor, and runs one hour.
HashiCorp lists no prerequisite credential, but it states that candidates should have basic terminal skills and an understanding of on-premises and cloud architecture. The exam tests Terraform 1.12 and the credential is valid for two years. It is issued and maintained by HashiCorp, which publishes the eight objectives on its certification site.
What IaC is, the advantages of IaC patterns, and multi-cloud, hybrid cloud and service-agnostic workflows. 3 sub-objectives.
Installing and versioning providers, how Terraform uses them, multi-provider configuration, and how state is used and managed. 4 sub-objectives.
Init, validate, plan, apply, destroy, and formatting and style adjustments. 7 sub-objectives.
Resource and data blocks, references, variables and outputs, complex types, expressions and functions, dependencies, custom conditions, sensitive data. The largest at 8 sub-objectives.
Module sources, variable scope, using modules in configuration and managing module versions. 4 sub-objectives.
The local backend, state locking, remote state with the backend block, drift and state management. 4 sub-objectives.
Importing existing infrastructure, inspecting state with the CLI, and verbose logging. 3 sub-objectives.
Creating infrastructure in HCP Terraform, collaboration and governance features, workspaces and projects, and integration. 4 sub-objectives.
Four things that set the Terraform Associate apart from the single-cloud exams most infrastructure people have taken before.
Terraform describes infrastructure in HCL and hands the work to a provider, so the same workflow builds a network on AWS, a resource group on Azure or a project on Google Cloud. The first exam objective asks you to explain exactly that multi-cloud, hybrid cloud and service-agnostic model, which is why the credential travels between employers and platforms in a way a single cloud vendor's exam does not.
At $70.50 USD plus locally applicable taxes and fees, purchased from HashiCorp, this is one of the least expensive infrastructure exams you can book. The fee does not include a retake, so the low price rewards preparation rather than repeated attempts.
HashiCorp publishes all eight objectives and their 37 sub-objectives, so there is no guessing about scope. Turn that list into a lab plan; our guide to exam objectives documents shows how.
The Terraform Associate is not a DoD 8140 credential. It does not appear in the Qualification Matrix V2.1, so on its own it will not satisfy a cyber-coded position requirement. The current matrix is published at the DoD Cyber Exchange.
Its weight comes from the market instead. Terraform is the infrastructure as code tool that cloud, platform and DevOps teams standardize on across AWS, Azure and Google Cloud, HashiCorp is the company that builds it, and the exam is written from the same objectives that our HashiCorp course lineup is built around. Federal cloud teams ask for Terraform skills even though the credential sits outside the 8140 matrix.
Everything you need to know about the certification, the exam, and how long it stays current, as of September 2026.
The Terraform Associate proves you can write the code that builds the environment. From here, most people add a credential for the platform they build on, or for the cluster that runs on top of it. The three paths below are the common next moves.
The platform move for Microsoft shops. The Azure Administrator covers operating Azure environments across five domains in a 100-minute exam with a 700 out of 1000 passing score, costs $165 and renews free every year. If your Terraform providers are mostly azurerm, this is the credential that explains what the code is building.
The platform move for AWS shops. The AWS Solutions Architect Associate covers designing on AWS, which is the architecture your aws provider resources describe. Holding it alongside the Terraform Associate means you can both design the environment and write the configuration that provisions it.
The move up the stack. Terraform often provisions the managed cluster, and the CKA is the credential for running it: a two-hour performance-based exam for $445 with one retake included, valid two years. Together the two credentials cover the environment and the workloads on it.
The Terraform Associate sits early in the infrastructure path. Terminal skills and a grasp of cloud architecture come before it, and from there the path goes into the cloud platform you provision or up into the cluster that runs on it.
The skills HashiCorp expects
Write and run the code
Pick your path
Two questions to answer before you commit: can you sit it, and should you pursue the Terraform Associate specifically. Here's a straight answer to both.
No prerequisite credential, no required training, no application to approve.
The Terraform Associate has no formal prerequisites. You buy the exam from HashiCorp for $70.50 USD plus locally applicable taxes and fees, schedule it, and sit it online with a proctor. Nobody checks your resume first. HashiCorp does state what it expects you to bring: basic terminal skills and an understanding of on-premises and cloud architecture. Both are assumed by the questions rather than checked at the door, and both show up in the labs you should be running before you book.
A low price, no published passing score, and a second attempt is a second purchase.
The exam is inexpensive and the format is familiar, and that leads people to book before they are ready. HashiCorp does not publish the passing score or the question count, so there is no margin to calculate, and the fee does not include a retake. Candidates who have read about Terraform but never watched a plan change after editing state, never pinned a provider version or never configured a remote backend tend to be surprised by how specific the questions are. Spend your preparation running real configuration against real providers and work through all 37 sub-objectives before you schedule.
The Terraform Associate fits the roles that provision and operate cloud infrastructure. It is the credential that moves an administrator from the console to code, and the one cloud, platform and DevOps job listings name when they need someone who can read a plan and own the state.
Provisions and operates environments on AWS, Azure or Google Cloud, and increasingly does it in code rather than in the console. The provider, workflow and state objectives are the daily work of this role, and the credential is the shortest public signal that you can write and run the configuration.
Owns the pipeline from commit to running environment. Needs to understand plan output, remote state and module versioning well enough to put Terraform behind a pull request and a CI job, which is the core workflow and HCP Terraform objectives applied to a delivery system.
Builds the internal platform that product teams deploy onto. Publishes the modules other teams consume, manages the shared state backends and sets the guardrails, so the modules, state management and HCP Terraform objectives map directly to the job description.
Keeps production up and rebuilds it when it falls over. Drift detection, import of resources built by hand and reading state with the CLI are the maintenance objectives, and they are what an SRE reaches for during and after an incident.
The role that moves a data center team into code. An engineer who already understands networks, compute and storage uses the credential to show they can express that architecture in HCL, and the IaC and configuration objectives build directly on that background.
Designs the environment other people build. Architects who hold the credential can hand over reference modules instead of diagrams, review the plans their teams submit and speak to how a multi-cloud or hybrid design will actually be provisioned, which is the first objective in practice.
Three credentials infrastructure people often weigh together: one for the code that provisions the environment, one for the cluster that runs on it, and one for the cloud platform underneath. Here's how they line up.
| Terraform Associate | CKA | Azure Administrator (AZ-104) | |
|---|---|---|---|
| Issuer | HashiCorp | CNCF via the Linux Foundation | Microsoft |
| Role | Infrastructure as code practitioner | Kubernetes cluster administrator | Azure cloud administrator |
| Focus | Writing, running and maintaining Terraform configuration on any cloud | Installing, configuring, networking and troubleshooting Kubernetes clusters | Operating Azure environments |
| Prerequisites | None (terminal skills and cloud architecture understanding expected) | None | None (about 6 months Azure administration recommended) |
| Objectives or Domains | 8 objectives, no published weights | 5 domains | 5 domains |
| Exam | Multiple choice, online proctored, 1 hour | Performance-based, live cluster, 2 hours | 40 to 60 items, 100 minutes |
| Passing Score | Not published by HashiCorp | Not published on the exam page | 700 of 1000 |
| Exam Cost | $70.50 plus taxes and fees | $445 | $165 |
| Retake | Not included | One retake included | See the AZ-104 guide |
| Validity | 2 years | 2 years | 1 year, free renewal |
| Good Fit For | Cloud, DevOps, platform and infrastructure engineers on any cloud | Platform, DevOps, SRE and systems administrators who run clusters | Administrators of Microsoft-standardized environments |
Each exam is purchased from its own vendor and pricing may vary with taxes and region. The Terraform Associate is the only one of the three that is not tied to a single platform, and the only one delivered as a multiple choice test at this price point. None of the three appear on the DoD 8140 Matrix; their recognition is market-driven rather than DoD-listed. Read the CKA guide and the Azure Administrator guide for the full detail on each.
Certification Matchups: the published facts, strengths and weak spots of 33 certifications, side by side.
Our Terraform Essentials Boot Camp is three days of live online, hands-on, lab-based training built around the eight Terraform Associate exam objectives, with HCL labs across AWS, Azure and Google Cloud, a mock Terraform Associate exam on the last day, post-class mentoring and a free course retake within one year, for $2,195. The Terraform Associate exam itself is not included; you purchase it from HashiCorp for $70.50 plus applicable taxes and fees. For teams standardized on Azure, the three-day Managing Azure with Terraform Boot Camp ($2,195) covers the same objectives with every lab in Azure.
Which Kubernetes exam follows the environment you provision, how to study from an objectives list with no weights, the terminal groundwork underneath it, and what renewal looks like across certification bodies.
Terraform builds the environment and Kubernetes runs the workloads on it. The three CNCF exams side by side, what each one tests, and how to pick a first exam once the cluster you provisioned needs someone to operate it.
HashiCorp publishes eight objectives and 37 sub-objectives and nothing else about scope. How to turn that list into a lab plan when there are no weights to tell you where the points are.
Terraform people work across clouds more than most. When a second platform credential is worth the time, when it is not, and how a provider-agnostic tool changes the math.
Most Terraform runs start with a pull request. What the GitHub exams cover, including the Actions credential that sits closest to a Terraform pipeline, and which one fits an infrastructure role.
HashiCorp expects basic terminal skills before you sit the exam. A look at the current Linux+ exam for anyone who wants the command line foundation in place first.
How the major certification bodies handle renewal, from annual CPE quotas to fixed expiration dates like the Terraform Associate's two year validity, and what that means for planning your recertification calendar.
A vendor-neutral automation exam that overlaps with much of what Terraform practitioners do. What AutoOps+ covers, who it is written for, and where it sits next to a tool-specific credential.
HashiCorp organizes the exam into eight objectives and does not publish a weight for any of them. The badge on each row shows how many sub-objectives it contains, which is the only size signal HashiCorp gives: Terraform configuration has the most at eight and the core workflow follows with seven. Click any objective for what it covers.
Why teams define infrastructure in files instead of clicking through a console, and the advantages that come with the pattern: repeatable builds, reviewable changes and version history. It also asks you to explain how Terraform handles multi-cloud, hybrid cloud and service-agnostic workflows through one language and one workflow.
How providers work: installing them, pinning their versions and understanding how Terraform uses them to talk to each platform. You also write configuration that uses more than one provider at once and explain how Terraform uses and manages state to track what it has built.
The commands you run every day, in order: init to set up the working directory, validate to catch errors, plan to generate and review an execution plan, apply to make the changes and destroy to tear them down. Formatting and style adjustments to a configuration round out the workflow.
The largest objective by sub-objective count covers the language itself: resource and data blocks, attribute references between resources, variables and outputs, complex types, expressions and functions, and explicit resource dependencies. It also covers custom conditions for validating configuration and the sub-objective HashiCorp titles 'Understand best practices for managing sensitive data, including secrets management with Vault.'
How Terraform sources modules, from the public registry to Git repositories and local paths, and how variable scope works once configuration is split into modules. You use modules in a configuration and manage which version of a module you are pulling in.
The local backend and its limits, then state locking and why it matters when more than one person runs Terraform against the same infrastructure. You configure remote state with the backend block and handle drift when the real infrastructure no longer matches the state file.
Bringing infrastructure that already exists under Terraform control with import, and using the CLI to inspect state so you can see what Terraform believes is deployed. It also covers verbose logging: when to turn it on and how to use what it produces.
Using HCP Terraform, the hosted service, to create infrastructure, along with its collaboration and governance features. You also organize and use HCP Terraform workspaces and projects and configure HCP Terraform integration.
Objectives reflect the HashiCorp Certified: Terraform Associate (004) exam as published on developer.hashicorp.com and verified on September 29, 2026, testing Terraform 1.12. Sub-objective counts are shown because HashiCorp publishes no weights. Confirm the current objectives and Terraform version on the HashiCorp certification page before scheduling.
The questions candidates ask most often when researching the HashiCorp Certified: Terraform Associate.
The HashiCorp Certified: Terraform Associate is the entry credential for infrastructure as code with Terraform, issued by HashiCorp, the company that builds the tool. It shows that you understand why teams define infrastructure in code, can install and version providers, run the init, plan, apply and destroy workflow, write configuration with variables, outputs, modules and expressions, manage state in a remote backend, import existing resources and work in HCP Terraform. The current exam is version 004 and it tests Terraform 1.12.
It's an online, proctored, multiple choice exam that runs one hour. You take it from your own computer with a proctor watching, and every item is a question rather than a task in a live environment. HashiCorp doesn't publish how many questions are on the exam, so plan your pace around the hour rather than around a question count.
As of September 2026 the Terraform Associate (004) exam tests Terraform 1.12, which is the version HashiCorp lists on the exam page. HashiCorp updates the exam as Terraform moves, so practice on 1.12 and check the certification page again when you schedule. Features that changed between releases, such as how custom conditions validate configuration, are exactly what a current objective list expects you to know.
No prerequisite certification and no required training. HashiCorp does say that candidates should have basic terminal skills and an understanding of on-premises and cloud architecture, and both show up on the exam: you'll read CLI output and reason about how compute, network and storage fit together. You buy the exam from HashiCorp, schedule it online and sit it with a proctor. Nobody reviews your background first.
HashiCorp publishes eight objectives: Infrastructure as Code (IaC) with Terraform, Terraform fundamentals, Core Terraform workflow, Terraform configuration, Terraform modules, Terraform state management, Maintain infrastructure with Terraform, and HCP Terraform. Each one breaks into three to eight sub-objectives, 37 in total, and Terraform configuration is the largest with eight. Together they follow the path from why you'd use Terraform at all through writing, running, sharing and maintaining real configuration.
HashiCorp doesn't publish a weight for any objective and doesn't publish a passing score, so there's no percentage split to study toward and no number to aim for. The only size signal is the count of sub-objectives under each objective, and even that isn't a promise of how many questions you'll see. The practical approach is to be able to do every sub-objective at the terminal and to explain what each command changes, because the questions test understanding rather than memorized flags.
The exam costs $70.50 USD plus locally applicable taxes and fees, purchased directly from HashiCorp, and the fee does not include a retake; HashiCorp says so on the exam page, so a second attempt is a second purchase. The exam is not included in Training Camp's Terraform Essentials Boot Camp: you register and pay for it with HashiCorp separately, and the boot camp's $2,195 program fee covers three days of live online training, hands-on HCL labs across AWS, Azure and Google Cloud, a mock Terraform Associate exam on the last day, post-class mentoring and a free course retake within one year.
No. HashiCorp certifications don't appear on the DoD 8140 Approved Qualifications Matrix V2.1, so the Terraform Associate on its own won't satisfy a cyber-coded position requirement. Terraform still shows up in federal and defense job listings because agencies and contractors provision cloud environments with it, but that demand comes from the tooling, not the matrix. See the full DoD 8140 work role paths.
The credential is valid for two years from the date you earn it. HashiCorp's exam page states the two-year validity but doesn't spell out a renewal route on that page, so check the current certification program rules on developer.hashicorp.com as your expiration approaches. Since the exam version and the Terraform version it tests both move, plan on studying the objectives that are current when you renew rather than the 004 list on this page.
The Terraform Associate maps to the roles that provision and operate cloud infrastructure: Cloud Engineer, DevOps Engineer, Platform Engineer, Site Reliability Engineer, Infrastructure Engineer and Cloud Architect. Employers hiring for those roles want someone who can read a plan, understand state and ship a reviewed change through a pipeline, and the credential is the shortest public signal that you can. It's also the credential systems administrators use to show they've moved from console clicks to code.
It depends on which layer you own. If your job is writing the code that provisions environments, on any cloud, start with the Terraform Associate: it's a one-hour multiple choice exam for $70.50, and it's the only one of the three that isn't tied to a single platform. If you run Kubernetes clusters, the Certified Kubernetes Administrator (CKA) is a two-hour performance-based exam for $445 with one retake included. If your organization is standardized on Azure and you administer it day to day, the Azure Administrator (AZ-104) is a 100-minute Microsoft exam for $165 with a 700 out of 1000 passing score and a one-year validity with free renewal. Many people end up holding the Terraform Associate alongside one of the other two.
Easier in format than a performance-based exam, but not a giveaway. The questions assume you've actually run Terraform: you'll be asked what a plan will do, what happens to state when a resource is removed from configuration, how a module version constraint resolves and why a backend needs locking. Candidates who've only read about Terraform miss those. Plan on hands-on time with real providers, break and repair state on purpose, and read the eight objectives line by line before you book. There's no retake in the fee, so treat the first attempt as the only one.
For anyone who provisions cloud infrastructure, yes. Terraform is the common infrastructure as code layer across AWS, Azure and Google Cloud, and the Terraform Associate is the low-cost, vendor-issued credential that proves you understand its workflow, state model and module system rather than one cloud's console. It's a two-year credential with a $70.50 exam, so the investment is mostly study time. If your work is running clusters or administering a single platform, pair it with the CKA or the Azure Administrator, since the code that builds the environment and the platform it builds on are two different jobs.
If you're weighing the certification, planning an infrastructure as code path, or arranging Terraform training for a team, tell us where you are and we'll help you map out the right next step.