Advanced Terraform
Take Terraform from single configs to production scale. Learn reusable modules, how state really works, day-two maintenance, and HCP Terraform — and remember it with spaced repetition.
- practice cards
- 80
- practice cards
- per day
- ~10 min
- per day
- level
- Intermediate → Advanced
- level
- modules
- 4
- modules
Beyond the basics
Once you know the core plan/apply workflow, real Terraform work is about scale and safety. Modules let you package and reuse infrastructure instead of copy-pasting it. State — how Terraform tracks what it manages — becomes something you have to share, lock and protect as a team grows.
This track covers the parts that bite in production: writing and composing modules, managing remote and locked state, day-two operations like import and refactoring with moved blocks, and what HCP Terraform adds for collaboration, runs and policy.
It uses spaced repetition so the patterns stick — and it lines up with the advanced objectives of the HashiCorp Terraform Associate exam.
4 modules, seed to bloom
Each module is a set of practice cards — 80 in total. Answer, review, and watch your knowledge grow from seed to full bloom.
Terraform Modules
Reusable modules — module blocks, sources, inputs and outputs, versioning, and the Registry
20 cardsTerraform State
Managing state — its purpose, local vs remote backends, locking, sensitive data, and state commands
20 cardsMaintaining Infrastructure
Day-two operations — import, apply -replace and taint, -target, drift detection, and workspaces
20 cardsHCP Terraform
The managed platform — HCP Terraform vs Community Edition, remote runs and state, VCS workflow, and policy
20 cardsSample questions
A taste of the real cards. Pick an answer, then reveal the explanation.
What is a module in Terraform?
- AA container of Terraform files in a directory used together as a reusable unit
- BA single Terraform file that defines exactly one resource for one provider
- CA plugin that teaches Terraform how to manage a specific platform's API
- DA stored record of the real infrastructure that Terraform currently manages
What is the purpose of Terraform state?
- ATo map the resources in your configuration to the real objects that exist in the world
- BTo store the provider plugins that Terraform downloads for the configuration to use
- CTo record the ordered commands that Terraform will run during the next apply step
- DTo hold the version constraints that Terraform applies when selecting its providers
What does the terraform import command do?
- ABrings an existing real resource under Terraform management by recording it in state
- BCreates a brand new resource from configuration and records it in the state file
- CCopies a resource definition from another module into the current configuration
- DDownloads a published module from the Registry into the working directory tree
What is HCP Terraform?
- AA managed platform by HashiCorp that runs Terraform and stores state for teams
- BA separate language that replaces HCL for writing cloud infrastructure at scale
- CA command-line tool you install locally to apply Terraform without any account
- DA public registry that only hosts verified providers for large organizations
Learn it once, keep it for good
Answer a question
Each card is one practical concept with multiple options. Pick what you think is right.
Get the full answer
See the correct option plus a clear explanation, and a link to deeper docs when one is available.
Review at the right time
A spaced-repetition engine (SM-2 or FSRS) resurfaces each card just before you would forget it.
Why advanced Terraform pays off
Reuse instead of repeat
Modules turn battle-tested infrastructure into building blocks you can share across projects and teams.
State without surprises
Understanding remote state, locking and drift is what keeps a team from clobbering each other's changes.
Operate day two
Import, refactor and migrate real infrastructure safely — the work that starts after the first apply.
Certification-ready
Covers the advanced objectives of the HashiCorp Terraform Associate exam.
Common questions
Should I do the fundamentals first? +
Yes — this track assumes you already know the core plan/apply workflow and basic HCL. Start with Terraform Fundamentals if those are new to you.
How long does it take? +
About 10 minutes a day. Spaced repetition means short, frequent sessions beat long cramming, so the patterns stick.
Is it free? +
Yes, completely free. No registration or credit card is required, and all your progress is stored locally in your browser.
Ready to scale your Terraform?
Plant your first seed today. Ten minutes a day is all it takes to grow production-grade infrastructure skills.