AI-assisted: I put this together from HashiCorp's Terraform Associate (004) page with help from an AI tool, and checked each fact against that page. I run LearnSome.tech, which teaches Terraform; you can prepare without us.
The Terraform Associate is HashiCorp's foundational Terraform certification. The current version is 004. Here is what the official page says, and what it leaves out.
The facts
- Format: multiple choice, online proctored.
- Duration: 1 hour.
- Terraform version tested: 1.12.
- Price: USD 70.50 plus local taxes and fees. A free retake is not included.
- Valid for: 2 years.
- Prerequisites: basic terminal skills and an understanding of on-premises and cloud architecture. HashiCorp says professional experience is recommended, but you can also prepare by practising the objectives in a personal demo setup.
What the page doesn't publish: the number of questions, the pass mark, or any weighting between the objective areas. So you can't game it by skipping a "small" domain. Every area can matter.
The eight objective areas
- Infrastructure as Code with Terraform
- Terraform fundamentals (providers, and how Terraform uses state)
- The core workflow: init, validate, plan, apply, destroy, fmt
- Terraform configuration: resources and data blocks, variables and outputs, complex types, expressions and functions, dependencies, custom conditions, sensitive data
- Modules: sources, variable scope, versions
- State management: the local backend, locking, remote state, drift
- Maintaining infrastructure: import, inspecting state from the CLI, verbose logging
- HCP Terraform: workspaces and projects, collaboration and governance
How I'd study for a one-hour, unweighted exam
Do the workflow with your hands, even though the exam won't ask you to. Questions about plan and apply are far easier when you have watched a plan want to replace something you didn't expect. A free local setup is enough: a local_file or a random provider resource lets you practise state, import and drift with no cloud bill.
Know the state questions cold. State, backends and locking appear in two separate areas (2 and 6). Be clear that not every backend locks, that a backend block takes literal values only, and that marking a value sensitive hides it from output but not from the state file.
Read the HCP Terraform area properly. It's a whole objective area, and people who only use the CLI tend to skim it.
The thing it can't check
Multiple choice shows you know Terraform's workflow and language. It doesn't test hands-on skill, and it doesn't replace managing real infrastructure: reading a plan carefully before you approve it is a habit, and no exam can see habits.
What's the Terraform concept that took you longest to really get?
Top comments (0)