Terraform Associate 004 is the current foundational exam
HashiCorp Certified: Terraform Associate (004) validates foundational Terraform knowledge for cloud engineers and other practitioners who work with infrastructure as code. HashiCorp currently identifies Terraform 1.12 as the version tested. The assessment lasts one hour, is online-proctored and uses selected-response questions. The credential is valid for two years. The issuer recommends professional Terraform experience, but a personal demonstration environment can be a suitable way to practice the objectives. A candidate needs basic terminal skills and a general understanding of infrastructure rather than provider-specific expertise in one cloud.
The current Terraform Associate 004 exam is organized into eight objective groups, with no official percentage weights published for individual groups. The best starting point is the current HashiCorp certification page, its 004 content list and the Terraform 1.12 documentation. Older 003 materials can still teach persistent concepts, but they do not cover every changed objective. Do not claim that a practice provider knows the live exam items or that one unofficial passing percentage is guaranteed by HashiCorp.
Objective 1: infrastructure as code and its benefits
The first objective group asks what infrastructure as code means, why declarative patterns are useful, and how Terraform supports multi-cloud, hybrid and service-agnostic workflows. An engineer should be able to explain repeatable configuration, version control, reviewable changes and the relationship between desired state and real infrastructure. Infrastructure code is valuable because teams can inspect proposed changes before executing them and maintain a shared description of intended resources. That is different from simply placing a script in a source repository.
HashiCorp does not require candidates to know every cloud provider’s product catalog. The assessment focuses on the Terraform mechanism for using providers to work with APIs. A strong answer distinguishes Terraform’s workflow from the work performed by a provider and explains why a plan and state exist. The broader Terraform across cloud providers topic can deepen the architectural context, but the tested concept is infrastructure-as-code behavior rather than the features of a particular provider.
Objective 2: providers, versions and Terraform fundamentals
Terraform uses providers to interact with target systems. Candidates should understand provider blocks, required provider declarations, version constraints, multiple-provider configurations, and the dependency lock file. A version constraint expresses allowable releases; the lock file records selections used for reproducibility. Those mechanisms differ from choosing a Terraform binary version. Initialization obtains required provider plugins and modules and prepares the working directory or backend. A configuration can parse correctly but fail later because the provider is unavailable or its credentials are not authorized.
This group introduces Terraform state: the mapping Terraform maintains between resource addresses in configuration and managed remote objects. Knowing that state exists is necessary before the later state-management domain can make sense. State may contain sensitive operational data, and it is not an ordinary file to edit casually. The Terraform and HCP Terraform fundamentals relationship is useful for distinguishing local execution from collaborative remote operation.
Objective 3: the core command workflow
HashiCorp’s 004 content list covers initializing a working directory, formatting configuration, validation, generating and reviewing an execution plan, applying changes and destroying managed resources. These commands have different effects. terraform fmt changes layout, terraform validate checks configuration properties, terraform plan proposes actions, and terraform apply makes changes when authorized. The plan step should not be described as automatically changing the infrastructure. Provider API errors or missing permissions may still arise even after a configuration validates successfully.
Practice predicting a plan before running it. A resource update, replacement or deletion can have availability consequences, so an engineer should inspect the proposed actions rather than approving a plan blindly. A destroy operation is part of the lifecycle but must be reserved for authorized, disposable resources in a training exercise. The exam tests what the workflow does and why one command is the appropriate next step, not just the spelling of each command.
Objective 4: configuration, expressions and new 004 additions
The configuration domain covers resource and data blocks, attribute references, variables, outputs, complex types, expressions, built-in functions and dependency behavior. A resource block describes a managed object; a data block obtains information about an existing object. References usually let Terraform infer a dependency, while explicit depends_on is useful in selected situations where the dependency is not represented through ordinary data flow. The 004 syllabus explicitly calls out lifecycle behavior such as create_before_destroy, which can alter replacement order but cannot overcome provider limitations or scarce resource names automatically.
Custom conditions are another addition: variable validation, preconditions, postconditions and checks can express assumptions beyond syntax, subject to their evaluation behavior. Terraform 1.12 also makes ephemeral values and write-only arguments relevant to sensitive-data handling in supported contexts. A variable marked sensitive may limit display without guaranteeing the value is absent from state; ephemeral and write-only mechanisms address different persistence concerns. Candidates should learn when the language and selected provider support the feature and why secret management remains necessary.
Objectives 5 and 6: modules and state management
Modules organize reusable configuration behind inputs and outputs. The Associate exam covers where modules come from, variable scope, module usage and version selection. A module should have a clear interface so that a consumer can understand what it controls and how to upgrade it. Module versions, provider versions and the Terraform binary version are separate layers of change. Upgrading a module can affect many managed resources even when the root configuration changes only one source reference, so module changes deserve a plan review.
State management covers local and remote backends, state locking and drift. Remote state supports collaboration where the selected backend provides appropriate access and locking behavior, but it should not be treated as universally equivalent across all backends. State is sensitive because it represents managed objects and can contain values that must be protected. Drift occurs when actual infrastructure no longer matches declared configuration. A careful administrator decides whether to bring reality back into alignment or update approved configuration, rather than modifying state blindly to suppress a surprising plan.
Objective 7: maintaining existing infrastructure
The maintenance domain includes importing existing resources, inspecting state through the CLI and knowing when verbose logging helps diagnose failure. Import does not mean Terraform automatically understands the correct ongoing configuration; resource addresses and matching configuration still matter. Refactoring may use moved or removed blocks in supported circumstances to manage the relationship between configuration and state without unnecessarily recreating real objects. That work requires review because a mistaken address or missing mapping can produce destructive changes.
Enable diagnostic logging when investigating a controlled failure, then protect and remove logs that may contain sensitive information. A strong candidate can explain why a provider authorization error is different from a state-address problem or a configuration-validation error. The objective is safe long-term maintenance, not only provisioning an empty environment for the first time.
Objective 8: HCP Terraform collaboration and governance
HCP Terraform provides a hosted workflow for infrastructure runs, state and collaboration. The current Associate syllabus includes creating infrastructure, collaboration and governance features, workspace and project organization, and integration with Terraform workflows. A project can organize related workspaces, while each workspace has its own run and state context. VCS-driven and CLI-driven workflows differ in how configuration changes reach a remote run. Teams should understand where variables, policies, approvals and credentials are managed instead of assuming HCP Terraform is only a location to upload a state file.
Variable sets, run triggers, dynamic provider credentials, drift detection, private registries and policy enforcement illustrate the collaboration model where supported. These do not replace the local Terraform language; they add organizational controls around how changes are planned, reviewed and applied. The 004 update specifically calls attention to HCP Terraform projects and workspaces. A candidate should know how one application’s development and production workspaces might be organized without pretending that every HCP feature exists on every subscription or account.
What changed from 003 and how to review the official scope
HashiCorp’s published differences between Terraform Associate 003 and 004 include explicit lifecycle/dependency behavior, custom conditions, ephemeral/write-only handling and HCP Terraform workspace/project organization; 004 tests Terraform 1.12. The official guide does not give a fixed weighted allocation by objective, so a sound review covers all eight groups. Practicing one small configuration through initialization, plan, apply, module reuse, state, drift and a supported HCP workflow helps connect them without creating large infrastructure costs.
Use HashiCorp’s own sample questions to understand the selected-response format and the current certification page for scheduling, price and recertification policies. The separate Terraform command reference can aid syntax recall, but the decisive skill is explaining why a plan proposes a particular change and how the organization can apply it safely. This page is an issuer-specific current exam-scope reference; it should not duplicate the hands-on labs, HCP-focused study path or broader Terraform lifecycle article.