Terraform Infrastructure Engineer Professional (002): new HashiCorp exam

As of October 24, 2026, HashiCorp is preparing to launch Terraform Infrastructure Engineer Professional (002), a new certification for practitioners who design and operate Terraform in production. The official page says the exam launches at IBM TechXchange 2026 in Atlanta, held October 26–29, while online registration is still marked “coming soon.” The exam lasts 90 minutes, uses online proctoring, is delivered in English, and tests Terraform 1.15.

This credential is not simply a harder edition of Terraform Associate. Its scope includes configuration architecture, remote state, CI/CD pipelines, security, governance, and HCP Terraform or Terraform Enterprise operations. In other words, it evaluates decisions made when multiple teams, environments, and production constraints meet—not just whether a candidate can recognize Terraform syntax.

What is confirmed—and what is not yet available

HashiCorp has published the official certification page (opens in a new tab), an exam preparation hub (opens in a new tab), the detailed content list (opens in a new tab), and sample questions (opens in a new tab). These resources are sufficient to begin a structured preparation plan before general registration opens.

Item	Official information as of October 24, 2026
Name	Terraform Infrastructure Engineer Professional (002)
Announced launch	IBM TechXchange 2026 in Atlanta, October 26–29
Online registration	Coming soon; not yet open on the official page
Format	Multiple choice, online proctored
Duration	90 minutes
Language	English
Version tested	Terraform 1.15
Credential validity	Two years
Price	Not yet published

Two distinctions matter. First, a launch at an event does not guarantee that identical online appointments will immediately be available in every region. Second, HashiCorp has not displayed a price. Candidates should not estimate the fee by copying the current cost of Terraform Associate or another HashiCorp exam. Monitor the official page until registration, regional conditions, and pricing are explicitly published.

Who should consider Professional (002)?

HashiCorp expects basic terminal skills, an understanding of on-premises and cloud architecture, and practical experience with production Terraform. Terraform Associate is “strongly recommended,” but the official page also accepts equivalent knowledge. It is therefore guidance about the expected foundation rather than a mandatory administrative prerequisite.

The strongest candidates will already have worked through several of these situations: reusable module design, backend migration, state repair, pull-request plan review, provider version management, environment separation, policy enforcement, and remote-run troubleshooting. Someone whose Terraform experience consists only of short local exercises should build more hands-on experience first. The objectives require candidates to reason about tradeoffs, failure modes, and organizational scale.

For platform engineers, cloud engineers, SREs, senior DevOps practitioners, and infrastructure consultants, the certification can turn scattered production experience into a structured study framework. It may also help candidates articulate why one Terraform architecture is safer and easier to maintain than another, which is often more valuable than merely recalling a command.

Candidates building their cloud foundation separately can also consult the AWS Solutions Architect Associate SAA-C03 guide, while keeping the vendor-specific objectives distinct.

The seven exam domains

The official content list groups the exam into seven domains. The page reviewed does not publish percentage weightings, so candidates should not rely on invented allocations or assume the order indicates importance.

1. Scalable and resilient configurations

The first domain covers how to structure a Terraform codebase: module composition, integration of existing modules, dependencies, and design choices. The goal is not just to produce a valid resource block. Candidates need to understand how coupling, interfaces, and version constraints affect future changes.

One objective explicitly mentions using the Terraform MCP server with AI coding agents. This is a focused Terraform workflow objective, not evidence that the credential is a general AI certification. If you need background on Model Context Protocol training, OnLevelUp's French overview of MCP courses and the MCPA certification provides context; for this exam, prioritize HashiCorp's documented behavior and human review of generated changes.

2. State and backend management

This domain includes selecting and configuring a backend, performing state operations, migrating state, and recovering from problems. Candidates must separate three concepts clearly: configuration code, the real infrastructure, and Terraform's recorded state. In a lab, practice moving a resource, importing an existing object, and recovering a test environment without unnecessarily recreating infrastructure.

3. Lifecycle and operational workflows

Professional-level Terraform work includes planning, applying, upgrading, and responding to drift over the lifetime of an environment. Build scenarios around replacement, dependency changes, provider upgrades, and unexpected differences between state and reality. The important skill is predicting impact and choosing a controlled, reversible procedure whenever possible.

4. Continuous integration and delivery

Production infrastructure rarely moves directly from a developer laptop to a cloud account. A pipeline should validate code, create a plan, expose the plan for review, and apply only with appropriate controls. Candidates need to understand the responsibilities of the repository, CI/CD system, and Terraform execution platform. Secrets, approvals, plan artifacts, and execution permissions are architectural concerns, not last-minute configuration details.

For adjacent automation practice, the OnLevelUp article about Docker and YAML microlearning can help reinforce configuration and pipeline literacy. It is not a substitute for the HashiCorp objectives, but it can strengthen the habits used to review declarative files.

5. Security and governance

Security goes beyond marking variables as sensitive. Candidates should know how to minimize privileges, protect state access, control execution, and integrate policies. A useful exercise is to design a workflow where a team can propose infrastructure changes without receiving permanent cloud credentials. Document who can review, approve, execute, and audit each change.

6. Advanced modules and registries

This domain deepens module design, distribution, and lifecycle management. Candidates should be able to compare internal, public, and managed modules; version interfaces deliberately; and minimize breaking changes. Practice publishing or consuming a module through a registry and maintaining it when several teams depend on its outputs and input contracts.

7. HCP Terraform and Terraform Enterprise operations

The final domain focuses on organization-scale operation: projects, workspaces, remote runs, integrations, and governance. Even if your daily experience is mostly local or open source, study the HCP Terraform and Terraform Enterprise features named by the official learning path. Do not assume that an unrelated orchestrator maps one-to-one onto HashiCorp's platform concepts.

How it differs from Terraform Associate

Terraform Associate validates foundational Infrastructure as Code concepts, the core Terraform workflow, configuration, modules, state, and the broader HashiCorp ecosystem. Professional (002) begins with that foundation and asks a wider question: how do you make these elements reliable across production environments and an organization?

The difference changes how you should study. A small local project can demonstrate many Associate concepts. Professional preparation should add constraints and incidents: What happens when state must move? How do you control a provider upgrade? What if two teams change the same module? How does a policy block a plan? What should a pipeline do if conditions change between plan and apply?

“Professional” should not be interpreted as a guarantee of seniority. It describes the level of problems being evaluated. An experienced engineer with little HCP Terraform exposure may have a clear study gap. An Associate-certified candidate with no production experience should build that experience before booking the exam.

A six-week preparation plan

The official Professional (002) study path (opens in a new tab) organizes resources by domain and explicitly states that the exam tests Terraform 1.15. Use it as the primary source, and shorten or extend the schedule based on honest evidence from your own work.

Week 1—baseline. Read every objective and answer the sample questions without documentation. Flag any topic where you can describe what to do but cannot explain why it is the safer choice.
Week 2—module architecture. Refactor a configuration into versioned modules. Add provider constraints, input validation, and a deliberate output interface. Test how a compatible and incompatible change affects consumers.
Week 3—state and recovery. Configure a remote backend in a disposable environment, simulate a migration, and write a recovery runbook. Never experiment on production state.
Week 4—pipeline and security. Build a workflow that runs formatting, validation, and plan, then requires controlled approval before apply. Review secrets, identities, and the lifetime of credentials.
Week 5—HCP Terraform or Enterprise. Complete official tutorials for objectives your daily role does not cover. Connect each platform feature to a specific operational problem rather than memorizing menu names.
Week 6—consolidation. Repeat the sample questions, explain each answer aloud, and revisit weak objectives. Run a timed 90-minute review session to assess pacing and concentration.

Sample questions are a calibration tool, not a dump to memorize. When an answer depends on version-specific behavior, verify it in the Terraform 1.15 documentation instead of relying on an undated video or an older blog post.

Should you register as soon as it opens?

Early registration makes sense if you already operate Terraform in production, recognize most of the seven domains, and are comfortable with a newly launched preparation ecosystem. Waiting is reasonable if you still need practical experience, require a language other than English, or need a confirmed price before your employer approves funding.

The credential is valid for two years. HashiCorp says holders may begin renewal six months before expiration by taking the Professional exam or earning the AWS/Azure Terraform Authoring and Operations Advanced certification. If the credential expires, the exam must be taken again. Check the policy when your renewal window approaches because rules can change during a two-year validity period.

Booking checklist

Confirm that online registration is open in your region on the official page.
Use the actual published price rather than extrapolating from another exam.
Verify that English delivery and online proctoring suit your circumstances.
Study and practice with Terraform 1.15, not an older documentation set.
Cover all seven domains, including HCP Terraform or Terraform Enterprise.
Practice state migrations, pipelines, policies, and modules in an isolated environment.
Read identification, system, and testing rules before exam day.

Terraform Infrastructure Engineer Professional (002) fills a clear gap between knowing Terraform commands and engineering a durable Terraform platform. HashiCorp has released enough official material to start preparing, but pricing and general online registration still need confirmation. The practical decision today is to build verifiable skills and book only after the complete terms appear on the official page.