HashiCorp Terraform Associate Certification Study Guide
Preparing the Terraform Associate exam #
The HashiCorp Certified: Terraform Associate exam checks that you know the basics of Infrastructure as Code with Terraform. It is a one-hour test of multiple-choice, true/false and short-answer questions taken online with proctoring. Exam versions and objectives change, so read the current exam content list at developer.hashicorp.com before you start and verify price and format there.
The best preparation is writing configurations. Use a free-tier AWS account (create an AWS account for demos) and destroy everything after each practice. Everything below also works with OpenTofu, although the exam is about Terraform.
Exam objectives and where to study each #
| Objective | What to know | Study |
|---|---|---|
| Infrastructure as Code | What IaC is, benefits, declarative model | IaC |
| Terraform purpose | Providers, multi-cloud, state, plan | Terraform basics |
| Terraform basics | Providers, resources, data sources, init/plan/apply/destroy, version constraints |
AWS provider, cheat sheet |
| Terraform CLI | fmt, validate, taint/-replace, import, state, workspace, logging |
cheat sheet, replace and taint, debug |
| Modules | Sources, inputs and outputs, versions, scope | modules, registry modules |
| Core workflow | Write, plan, apply; saved plans; drift | drift, CI/CD |
| State | Local and remote backends, locking, sensitive data, terraform_remote_state |
state, backends, data sources |
| Configuration | Variables, outputs, locals, functions, expressions, count, for_each, dynamic, depends_on, lifecycle |
see below |
| HCP Terraform | Workspaces, remote runs, policies, private registry | HashiCorp tutorials |
Configuration topics to practice #
- Variables, outputs and locals, including types, validation,
sensitiveand the order of precedence of variable values. countandfor_each.- Dynamic blocks.
- Implicit and explicit dependencies.
- Lifecycle rules.
- Conditionals and
forexpressions and functions. - Provisioners and why they are a last resort.
- Secrets and the state.
A 4-week plan #
Week 1: core workflow. Install Terraform, create an S3 bucket and a VPC, and run init, plan, apply and destroy many times. Read the state with terraform state list and show.
Week 2: language. Rewrite the same project with variables, locals, outputs, for_each, conditionals and a data source. Add validation and sensitive variables.
Week 3: state and modules. Move the state to an S3 backend with locking, create a module, call it twice, use a registry module, and practice import, moved, workspaces and -replace.
Week 4: review and mock exams. Revisit the weak points, read the documentation of the CLI commands, and do practice questions (see the interview questions for scenario-style review).
Tips for the exam #
- Know the exact behavior of commands: what
terraform init,plan -out,refresh,fmt, andvalidatedo and do not do. - Know the precedence of variable definitions: environment,
terraform.tfvars,*.auto.tfvars,-varand-var-file. - Understand what happens when the state is lost, locked or contains drift.
- Know the difference between a resource and a data source, a provider and a module.
- Remember the three main types of version constraints (
=,>=,~>). - Be careful with questions that include absolute words such as "always" or "never".
After the exam #
The Associate level proves the basics. To go further, build real projects: a three-tier architecture, a CI/CD pipeline, and tests. The certificate is useful, but a repository of working infrastructure is worth more to employers.