Terraform Associate certification (004): exam and cost
The Terraform Associate certification is HashiCorp's foundational Terraform credential, and the current exam is Terraform Associate (004), which tests Terraform 1.12. Take it if you want to show a working foundation in Terraform before considering the Professional or Advanced exams: it is an hour-long, online-proctored exam and costs US$70.50 plus locally applicable taxes and fees as of November 2026.
This guide covers the eight objectives, the details HashiCorp does not publish, renewal for people who hold an older Associate credential, and the next certifications. It also gives you a study order and shows where practice questions can test the infrastructure-as-code judgement the exam expects.
At a glance
- Exam: HashiCorp Certified: Terraform Associate (004), the live, current Associate exam as of November 2026. It tests Terraform 1.12.
- Who it suits: cloud engineers with foundational Terraform skills. Basic terminal skills and an understanding of on-premises and cloud architecture help; professional experience is recommended, but a personal demonstration setup can provide the practice.
- Format: one hour, online proctored, as of November 2026. The published question formats include true/false, multiple-choice and multiple-answer questions.
- Price: US$70.50 plus locally applicable taxes and fees, as of November 2026. A free retake is not included.
- Credential: valid for two years. The renewal routes are different from simply assuming an older credential will be extended, so read the renewal section before booking another exam.
- Objectives: infrastructure as code, Terraform fundamentals, core workflow, configuration, modules, state management, infrastructure maintenance and HCP Terraform. HashiCorp publishes no percentage weights for those objectives.
Terraform Associate exam objectives
The objectives are a checklist for practical Terraform behaviour, not a request to memorise a collection of commands in isolation. When you revise an item, make yourself explain what changes in configuration, state and the next workflow step. That is more useful than recognising a term without knowing why it belongs in the workflow.
Infrastructure as code, fundamentals and workflow
The first objective is infrastructure as code with Terraform: understand why describing intended infrastructure in code makes a repeatable workflow possible. The fundamentals objective adds providers and state, so be ready to distinguish the configuration that uses a provider from the state Terraform uses while managing infrastructure. If a question describes an existing environment, pause to identify whether it is talking about configuration, the provider, or state.
The core workflow objective is where command knowledge has to become sequence knowledge. Know what terraform init, terraform validate, terraform plan, terraform apply, terraform destroy and terraform fmt ask Terraform to do, and when you would use each one. In practice, trace a change from setup and checking through a proposed change and application, rather than treating every command as an interchangeable way to run Terraform.
Configuration and modules
Configuration questions ask you to read the moving parts of a Terraform configuration. Review resource and data blocks, variables and outputs, then practise following complex types, expressions, functions and dependencies to their effect. You should also recognise custom conditions, how sensitive data is treated, and where Vault belongs when a scenario involves sensitive data.
Modules are a separate objective because reusable configuration needs its own judgement. Be able to identify a module boundary, what a caller supplies through variables, and what it receives through outputs. A useful revision exercise is to take a configuration with repeated resource blocks and explain which part you would turn into a module, without changing the infrastructure intent.
State management and maintenance
State management is more than knowing that a state file exists. The objective includes a local backend, locking, a remote backend and drift, so questions can ask where state is held, what prevents concurrent changes, or what it means when real infrastructure no longer matches the known state. Work through those situations as state behaviour: do not assume that a configuration file alone tells you what Terraform will find.
The maintenance objective covers importing resources, inspecting state and verbose logging. In a scenario, separate the task of bringing an existing resource under Terraform management from the task of examining the state Terraform already knows. Treat verbose logging as a diagnostic tool: it helps you investigate a workflow problem, but it does not replace checking the configuration and state involved.
HCP Terraform
HCP Terraform is its own eighth objective, so do not leave it until after a local-only review. Revisit the workflow with HCP Terraform in mind and practise identifying when a scenario places Terraform work there rather than solely in a local setup. This is the part that makes a study plan built only from old, generic command notes incomplete for the current objective list.
What HashiCorp doesn't publish
HashiCorp does not publish an Associate question count or a passing score. Your result is pass or fail, which means a blog post that presents a fixed number of questions or a percentage target is not an official exam rule. It is better to prepare for every published objective than to build a study plan around an unofficial threshold.
It also does not publish percentage weights for the eight objectives. You can use the objective list to make sure no domain is missing, but you cannot responsibly assign a certain share of the exam to state, modules or HCP Terraform. The published formats do tell you to expect more than one response style, including multiple-answer and true/false questions.
If you hold 002 or 003
Terraform Associate (004) is the current exam as of November 2026. If you are using material labelled 002 or 003, use it only as a source of core Terraform practice, then map every topic back to the current eight objectives and Terraform 1.12. Do not treat an older version label as evidence that it covers the current exam unchanged.
The renewal rule matters most if you already hold a credential. A 004 holder can extend the credential by passing Terraform Infrastructure Engineer Professional, either the AWS or Azure version of Terraform Authoring and Operations Advanced, or by retaking 004 starting six months before the credential expires. If a 002 or 003 holder retakes the Associate, that pass creates a new, separate credential; it does not update the older credential's expiry date.
If your Associate credential has already expired, pass the current Associate exam to earn the current credential again. That is a clearer goal than trying to infer a retirement date from an older version: HashiCorp has not published a retirement date for 003 or 004. Check the current Terraform Associate certification page before booking if your expiry date is close.
After the Associate: Professional and Advanced
Terraform Infrastructure Engineer Professional
Terraform Infrastructure Engineer Professional is newly available for registration as of November 2026. As of November 2026, it is a multiple-choice exam that tests Terraform 1.15, making it the next step for someone who has moved from foundational work to infrastructure-engineering responsibilities. Use the Associate objectives as a base, then choose this route when your work calls for the more advanced scope rather than taking another foundational exam for its own sake.
Terraform Authoring and Operations Advanced
Terraform Authoring and Operations Advanced is the hands-on-oriented option for practitioners with production-tested Terraform expertise. The live exam has AWS and Azure versions, tests Terraform 1.6, and is online proctored; its format is lab-based scenarios plus multiple-choice questions, with four hours and one 15-minute break, as of November 2026.
The Advanced exam costs US$295 plus locally applicable taxes and fees as of November 2026, and includes one free retake. Its credential is valid for two years. It is a poor shortcut for someone still learning providers, state and the core workflow, but a sensible progression when you can already author and operate Terraform in production-style situations.
Is the Terraform Associate certification worth it?
The Terraform Associate certification is worth pursuing if Terraform is part of the work you want to do and you need a structured way to prove you understand its basic workflow. It is especially useful when you can pair the credential with a repository or demonstration setup that shows you can work with providers, configuration, modules and state. The badge alone does not substitute for explaining a change plan or diagnosing drift in a real conversation.
It is less urgent if you only touch Terraform indirectly and a cloud-specific certification maps more closely to your current role. Compare the broader options in the best DevOps certification guide, then use the Associate when infrastructure as code is the skill gap you actually need to close. For interview practice, DevOps interview questions and Docker interview questions help you practise describing delivery and runtime choices alongside Terraform.
Terraform is also commonly discussed beside container platforms, but those are different skills. If your next role involves cluster operations, Kubernetes interview questions can reveal whether Kubernetes knowledge needs separate attention rather than being assumed from an infrastructure-as-code credential.
How to prepare for the Terraform Associate exam
Start with HashiCorp's free resources, including its Associate learning resources. They include a learning path, exam content list, sample questions and Get Started tutorials. Use the content list as your final coverage check, but use the tutorials to build and change configuration yourself; the exam objectives make more sense when you have seen a plan, state and configuration interact.
- Build the fundamentals first: use a provider, create and read configuration, then observe how state relates to a change. Make a habit of saying what each workflow command does before you run it.
- Move to configuration reading: practise resource and data blocks, variables, outputs, complex types, expressions, functions, dependencies, custom conditions and sensitive data. Then turn a repeated part into a module and trace its inputs and outputs.
- Make state scenarios deliberate: compare a local backend with a remote backend, explain why locking matters, and look for drift before deciding what a change will do. Add resource import, state inspection and verbose logging to the same review instead of learning them as unrelated commands.
Use cross-cloud infrastructure-as-code questions to test the decision-making around those concepts, while keeping in mind that they are not Terraform Associate exam questions. A practice question on immutable servers and configuration drift is useful for distinguishing replacement from long-lived configuration drift. A practice question on Terraform with Infrastructure Manager puts version-controlled Terraform into a Google Cloud service context.
Compare Terraform's workflow with other declarative tools without confusing their products. A practice question on declarative infrastructure with ARM templates tests repeatable, idempotent environment creation, while a practice question on repeatable infrastructure as code checks the same reasoning in an AWS setting. Explain why each answer fits its platform, then return to the Terraform-specific objectives and state behaviour.
Once those concepts are familiar, use the CI/CD and DevOps cert page to find related material and its practice-question bank to check your reasoning. Treat this as a concept check after hands-on study, not as a replacement for the free official material or for reading every objective. Before booking, revisit HCP Terraform as a distinct objective and do one final pass through the official content list.
Frequently asked questions
How much does the Terraform Associate certification cost in India?
The exam costs US$70.50 plus locally applicable taxes and fees as of November 2026. HashiCorp does not list an INR price, so its published information does not support a fixed rupee amount. A free retake is not included in that price.
How long is the Terraform Associate exam, and is it proctored?
The current 004 format is one hour and online proctored, as of November 2026. HashiCorp lists true/false, multiple-choice and multiple-answer formats, so do not prepare only for a single-answer response style.
Is Terraform Associate 003 or 004 current?
Terraform Associate (004) is the current, live version as of November 2026, and it tests Terraform 1.12. HashiCorp has not published a retirement date for 003 or 004, but current registration and study should target 004.
How many questions are on the Terraform Associate exam, and what is the passing score?
HashiCorp publishes neither an Associate question count nor a passing score. It reports the result as pass or fail, so treat precise counts and percentage targets from unofficial sources as estimates, not rules for the exam.
How do you renew Terraform Associate certification?
The 004 credential expires after two years. You can extend it by passing Terraform Infrastructure Engineer Professional or either the AWS or Azure version of Terraform Authoring and Operations Advanced, or by retaking 004 starting six months before it expires. If it has expired, pass the current Associate exam to earn the current credential again.