Terraform Infrastructure Engineer Professional (002) is now open for registration. HashiCorp lists a price of $200 USD plus local taxes, a 90-minute duration, online proctoring, and an English-language exam based on Terraform 1.15. The credential remains valid for two years, and no free retake is included.
This November 3, 2026 update replaces provisional launch information: candidates no longer need to wait for pricing or a registration button. Before paying, still verify the final amount, taxes, appointment availability, and country-specific rules on the official Professional (002) page (opens in a new tab).
Confirmed conditions on November 3, 2026
| Item | Official information |
|---|---|
| Certification | Terraform Infrastructure Engineer Professional (002) |
| Registration | Open online |
| Listed price | $200 USD plus local taxes |
| Free retake | No |
| Duration | 90 minutes |
| Language | English |
| Format | Multiple choice, online proctored |
| Version tested | Terraform 1.15 |
| Validity | Two years |
The $200 figure is HashiCorp’s published base amount. The total can change with local tax, so do not convert it into a promise of a fixed price in another currency. The lack of a free retake also makes premature booking more expensive. Use the objectives and sample questions to identify gaps first.
HashiCorp recommends basic terminal skills, understanding of on-premises and cloud architecture, and practical production Terraform experience. Terraform Associate is strongly recommended, or equivalent knowledge. This describes the expected foundation; the page does not present Associate as a mandatory administrative prerequisite.
Why this exam goes beyond Terraform Associate
Terraform Associate covers Infrastructure as Code concepts, the core workflow, configuration, modules, state, and the HashiCorp ecosystem. Professional (002) starts from that foundation and asks how to make Terraform reliable across teams, environments, and production constraints.
A small local project can illustrate many Associate objectives. Professional preparation should add incidents and tradeoffs: how do you migrate state without recreating resources? How do teams avoid breaking a module interface? What controls apply after plan review? How does policy block a noncompliant change? What if conditions change between plan and apply?
“Professional” describes the level of problems being assessed, not guaranteed seniority. An experienced engineer may still need to study HCP Terraform. An Associate holder without production experience should practice before booking.
The seven official domains
The detailed objective review (opens in a new tab) organizes the exam into seven domains. HashiCorp does not publish percentage weights on the reviewed page, so do not invent them or assume the order predicts exact question frequency.
1. Scalable and resilient configurations
This domain covers codebase architecture: module composition, dependencies, version constraints, and integration of existing components. Candidates must understand coupling and input/output contracts, not just write a valid resource.
One objective also names the Terraform MCP server with AI coding agents. This is a focused Terraform workflow, not a general AI credential. Prioritize documented HashiCorp behavior and human review of generated changes.
2. State and backends
Candidates must select and configure a backend, perform state operations and migrations, and recover from problems. Practice separating configuration, real infrastructure, and recorded state. In a disposable environment, import an object, move a resource, and document recovery. Never experiment on production state.
3. Lifecycle and operations
Professional engineering includes planning, applying, drift, replacement, and upgrades. Build scenarios where a dependency changes, a provider is upgraded, or state no longer matches reality. The important skill is predicting impact and selecting a controlled, reversible procedure.
4. Continuous integration and delivery
A pipeline should validate code, create a plan, expose it for review, and apply only with suitable controls. Secrets, identities, plan artifacts, approvals, and execution permissions are architectural decisions. Knowing a Terraform command is not enough.
For adjacent declarative-automation practice, OnLevelUp’s published article on YAML and Docker microlearning can reinforce careful configuration review. It is not an official Professional (002) prerequisite.
5. Security and governance
The domain goes beyond sensitive variables. Candidates should minimize privileges, protect state access, control execution, and integrate policy. Design a workflow where a team proposes changes without permanent cloud credentials, then state who reviews, approves, executes, and audits.
6. Advanced modules and registries
Practice module publishing, versioning, and maintenance. Compare public, internal, and managed modules; preserve contracts and reduce breaking changes. A useful lab publishes a test module, consumes it from several configurations, and then evolves its interface.
7. HCP Terraform and Terraform Enterprise
The final domain addresses organization-scale operations: projects, workspaces, remote runs, integrations, and governance. Even if daily work is local and open source, study the features named in the official path. Do not assume that a third-party orchestrator maps one-to-one to HashiCorp concepts.
A six-week preparation plan
The official study path (opens in a new tab) groups resources by objective and confirms Terraform 1.15. Use it as the primary source.
- Week 1 — baseline. Read every objective and answer the sample questions (opens in a new tab) without documentation. Flag answers you recognize but cannot justify.
- Week 2 — modules. Refactor a configuration into versioned modules with provider constraints, input validation, and explicit outputs.
- Week 3 — state. Configure a remote backend in an isolated environment, simulate a migration, and write a recovery runbook.
- Week 4 — pipeline and security. Run formatting, validation, and plan, then require approval before apply. Inspect credentials and permissions.
- Week 5 — HCP Terraform or Enterprise. Complete tutorials for objectives missing from daily work and connect each feature to an operational problem.
- Week 6 — consolidation. Repeat the questions, explain each answer, and complete a timed 90-minute session.
Sample questions are calibration, not a bank to memorize. When an answer is version-dependent, verify it in the Terraform 1.15 documentation.
Keep an evidence log during these six weeks. For each objective, record one configuration, command sequence, review decision, or recovery note that demonstrates your understanding. The log should not contain production secrets or copied exam material. Its purpose is to expose weak spots: if you can state a definition but cannot produce a safe example or explain the tradeoff, that objective still needs work.
Use a disposable cloud account or local test environment wherever possible. Apply cost limits, least-privilege credentials, and cleanup procedures before creating resources. The Professional exam expects production reasoning, but preparation should never create an avoidable production incident.
Should you book now?
Book if you already operate Terraform in production, recognize most of the seven domains, and are ready for an English online-proctored assessment. Waiting is rational if you still need hands-on experience, HCP Terraform is new, or your employer must approve the total cost.
The credential lasts two years. HashiCorp describes two renewal routes starting six months before expiry: retake Professional or earn the AWS/Azure Terraform Authoring and Operations Advanced certification. An expired credential requires another exam attempt. Check the policy when the renewal window opens because it can change.
Registration availability does not mean every appointment slot or local condition will be identical. Read the booking flow through to the final review screen before committing. Confirm the legal name on your identification, the supported operating system and browser, room requirements, and cancellation or rescheduling terms. These practical checks do not improve technical knowledge, but they reduce the risk that a prepared candidate loses an attempt for an avoidable administrative issue.
Pre-payment checklist
- Confirm the $200 base amount and taxes shown for your region.
- Accept that no free retake is included.
- Review identification, workstation, network, and proctoring requirements.
- Work with Terraform 1.15.
- Cover all seven domains, including HCP Terraform or Enterprise.
- Practice state, modules, pipelines, and policy in an isolated environment.
- Book only after an honest diagnostic with official resources.
Terraform Infrastructure Engineer Professional (002) now has a clear position between knowing Terraform and engineering a durable platform. Registration and price are no longer hypothetical. The decision therefore shifts to readiness: a $200 payment without a free retake makes sense only when production skills are already demonstrable.



