Terraform Associate 004 30-, 60-, and 90-day study plan with topic order, review loops, and final-week priorities.
Use this study plan when you want a real route through Terraform Associate (004) instead of memorizing random CLI commands. The exam rewards workflow judgment: right initialization, right plan review, right state handling, and right module or provider decision.
flowchart LR
A["Write or update configuration"] --> B["Init, fmt, validate"]
B --> C["Plan and inspect change"]
C --> D["Check state and dependencies"]
D --> E["Apply safely"]
E --> F["Observe drift or new requirements"]
F --> C
004 emphasis areasTreat these as real exam lanes, not appendix trivia:
depends_on and create_before_destroyephemeral values and write-only arguments| Starting point | Typical study time | Good timeline |
|---|---|---|
| already using Terraform regularly | 12-20 hours | 2-3 weeks |
| infrastructure background but newer to Terraform | 20-30 hours | 3-4 weeks |
| newer to IaC and Terraform workflow | 30-45 hours | 4-6 weeks |
| If you are… | Use the plan like this |
|---|---|
| already comfortable with CLI basics but weaker on state | spend extra time on drift, import, backends, locking, and HCP run behavior |
| stronger on infrastructure than Terraform language | spend extra time on modules, expressions, variables, outputs, and lifecycle rules |
| comfortable with local CLI but weaker on HCP Terraform | spend extra time on workspaces, projects, runs, collaboration, and integrations |
| short on time | complete one pass through workflow, state, and HCP Terraform before chasing edge-case syntax |
| If your background is… | Best initial plan |
|---|---|
| already using Terraform regularly | compress to 2-3 weeks only if state and HCP Terraform misses are already narrow |
| infrastructure background but newer to Terraform | keep the full 4-week plan |
| newer to IaC and Terraform workflow | use 4-6 weeks and repeat workflow plus state before booking |
Keep one small Terraform workspace alive while you study. It should include:
004 objective topics are not abstract| Week | Focus | What to prove to yourself | Review links |
|---|---|---|---|
| 1 | 1. IaC, 2. Fundamentals, and 3. Workflow | You can explain why init, plan, and apply are separate workflow stages and why Terraform is more than a faster shell script. |
Cheat Sheet and Glossary |
| 2 | 4. Config and 5. Modules | You can distinguish resource from data, variables from outputs, modules from workspaces, and inferred dependencies from explicit ones. |
Resources and Cheat Sheet |
| 3 | 6. State and 7. Maintenance | You can explain what state records, why remote state and locking matter, and when import changes management without creating infrastructure. | Glossary and FAQ |
| 4 | 8. HCP and mixed review | You can separate local CLI workflow from remote operations, collaboration, governance, projects, run triggers, and integrations. | Cheat Sheet, Resources, and FAQ |
apply, not just after itbackend config affects state location, not resource definition004 additions instead of assuming older prep notes are enough| Miss pattern | Usually means | Best page to revisit |
|---|---|---|
| provider, backend, module, workspace, and project still blur together | your Terraform nouns are not separated cleanly yet | Glossary |
| you keep choosing commands instead of explaining workflow | you are memorizing CLI flags instead of the run lifecycle | Cheat Sheet |
| import, drift, and state corrections feel interchangeable | you need a stronger state model | FAQ |
| HCP Terraform answers still feel generic | you need to separate platform collaboration features from raw CLI behavior | Resources |
| custom conditions, lifecycle, or write-only arguments feel unfamiliar | your 004-specific review is too shallow |
Resources and FAQ |
You are getting close when:
004 details and sample-question page on resourcesplan, state, and apply stay concrete