How I cleared the Terraform Associate on a 3-week sprint.

Three weeks. That's how long I gave myself to clear the HashiCorp Terraform Associate exam. I had a full-time job leading the InfraGenie team, a wedding two weekends out, and the kind of motivation that usually evaporates by week two. It worked anyway. Here's what mattered.

01 — contextWhy I bothered

I'd been writing Terraform for two years before I sat for the cert. That's the wrong reason to take it, and also exactly the right reason. The exam doesn't teach you Terraform. It exposes the gaps you've been patching over with experience.

For me, those gaps were: state file internals, the difference betweenterraform_remote_state and a data source, and a surprising amount of workspace behavior I'd never used at work but the exam loves.

02 — planThe three-week plan

I broke it into read, build, drill. One week each. The order matters; I tried building first the previous time I attempted this and burned out before I made it to drills.

Week 1 — read

Skim the entire HashiCorp Learn track end to end. Don't take notes the first pass. Just absorb. Goal: build a map. The bits that surprise you are the bits you'll come back to.

• Skip the marketing intro pages. Start at "Build infrastructure".
• Read on a tablet, not a laptop. Less typing means more reading.
• Bookmark every page that surprises you. You'll come back.

Week 2 — build

Pick a project. Not a real one. Something throwaway. I rebuilt a static site on AWS — S3, CloudFront, Route 53, ACM, the works — three different ways:

1. Once with all the resources in a single root module (ugly, instructive)
2. Once with three child modules (cleaner, this is what the exam wants you to recognise)
3. Once with a remote backend and workspaces for dev/staging/prod

The third pass is the one the exam tests on, and the one most people have never actually done at work.

Week 3 — drill

Practice exams. I did Bryan Krausen's set on Udemy (worth it) and HashiCorp's official sample (also worth it, but shorter). The rule I gave myself: any question I got wrong, I had to explain out loud to my partner before going to bed. If I couldn't, I went back to the docs.

If you can't explain why an answer is wrong, you've memorised the right answer for the wrong reasons. The exam will punish that.

03 — pitfallsThe five questions that nearly got me

These were the categories I bombed on practice runs. Save yourself the trouble:

# 1. State manipulation
terraform state mv module.web.aws_instance.app module.api.aws_instance.app

# 2. Targeted apply (rare in practice, common on the exam)
terraform apply -target="module.network"

# 3. The difference between -refresh-only and -refresh=false
terraform plan -refresh-only        # compute drift, no plan
terraform plan -refresh=false       # skip drift detection

# 4. Workspaces vs directories — and why workspaces aren't enough for prod
terraform workspace new staging

# 5. Sensitive values in outputs
output "db_password" {
  value     = aws_db_instance.main.password
  sensitive = true
}

Memorise these five. Then forget them. By the time you can write them without looking, you've internalised the model the exam is actually testing.

04 — metaWhat I'd do differently

• Take the official HashiCorp practice exam first, not last. Use it as a diagnostic. I waited until day 18 and wasted three days re-reading things I already knew.
• Skip the YouTube cram courses. They're optimised for engagement, not retention. Docs and one Udemy course are enough.
• Schedule the exam before you start studying. Deadlines work. I scheduled mine on day 1.
• Don't study the morning of. Walk the dog. Drink coffee. Show up calm.

05 — closeWas it worth it?

Yes, but not for the reasons I expected. The cert hasn't changed how I'm perceived in interviews — what changed is how I read Terraform PRs. The exam forced me to internalise the mental model behind the tool, not just the syntax. I make different choices now. Better ones, mostly.

If you've been writing Terraform for a year or more and you're on the fence: three weeks. Index card. Show up. You'll be fine.

—
questions? email me or find me on linkedin.