How to Prepare for Terraform Associate

Use a personal demo setup with low-risk resources. Create one resource, one variable, one output, and one provider constraint. Run the whole workflow, then intentionally change configuration to see the plan. Small labs are safer than copying large modules because every plan line has a visible cause.

Treat `terraform plan` as a review document. Identify creates, updates, replacements, and destroys. If Terraform wants to replace a resource unexpectedly, inspect state, resource addressing, provider arguments, lifecycle rules, and any attributes that force replacement before accepting the plan.

Break common things on purpose: skip `init`, use an invalid variable type, reference a missing attribute, point to a bad module source, change a backend, remove a resource outside Terraform, and import an existing object. The exam often describes symptoms; practice should train you to name the first check.

A frequent mistake is assuming configuration and state are interchangeable. Configuration declares intent. State tracks managed objects and cached attributes. Import updates state, but you still need configuration that matches the object. Manual cloud-console edits may appear as drift and should be reconciled deliberately.

Know when local CLI is enough and when HCP Terraform is the better answer. Workspaces, projects, remote runs, shared variables, VCS integration, state storage, and policy enforcement solve team problems. They are not needed for every small local experiment.

After a missed DotCreds question, categorize the issue: provider setup, workflow command, state, module scope, variable/output behavior, lifecycle dependency, import, drift, or HCP Terraform collaboration. Then revisit the matching documentation or lab step and repeat the scenario until the symptom is familiar.