Terraform Professional study plan (002)
A good Terraform Professional study plan has four phases: confirm you have the production experience the exam assumes, work through the seven official objective areas with a lab of your own beside the notes, drill the tracing and prediction questions that separate this exam from the Associate, then rehearse with timed mocks. The exam is multiple choice and multiple answer, sat online with a proctor, but its questions are scenarios from running Terraform in production: state shared between engineers, pipelines that hold credentials, upgrades across many workspaces and policy that blocks a risky change. Reading alone will not prepare you for those, so most of the plan is spent applying real configurations in your own environment.
Know what kind of exam this is
The Infrastructure Engineer Professional (002) is a multiple-choice exam for people who already run Terraform at work. HashiCorp’s sample questions mix single-answer items with multiple-answer items, where the question tells you how many options to choose, and many of them include an HCL snippet you have to read: a backend block, a module call with variables and locals, a version constraint. HashiCorp also says the questions are not meant to trick you and do not test spelling or obscure details.
It is not a hands-on lab exam. That format belongs to HashiCorp’s separate Terraform Authoring and Operations Advanced exam. The Professional exam still rewards hands-on work, because a scenario about two engineers running apply at the same moment, or a module upgrade that changes a resource address, is far easier to answer once you have caused and fixed that problem yourself.
Where the Associate checks that you know what a command or block does, the Professional asks what to do about a situation. It covers configuration design, state and backends, lifecycle operations, CI/CD, security and governance, modules and the registry, and operating HCP Terraform and Terraform Enterprise. It is tested against a specific Terraform version, currently 1.15, so check the exam page and study against that release.
Phase 1 — Check your footing (a day or two)
Start with the prerequisites, because HashiCorp is unusually direct about them. It strongly recommends the Terraform Associate certification, or equivalent experience, and says experience with Terraform in a production setting is necessary, alongside basic terminal skills and an understanding of on-premises and cloud architecture. If you have only used Terraform on personal projects, the Terraform Associate study plan is the better place to start.
Then read the exam objectives end to end, work through HashiCorp’s own sample questions, and answer a short practice session cold. The aim is to find out which areas sit outside your day job. An engineer who writes modules all day may never have set up dynamic provider credentials or written a policy, and an operator who runs HCP Terraform may not have written a terraform test file.
Set up a lab you can break: a sandbox cloud account or a local provider, a remote backend with locking, a version-control repository and a CI runner. SaveMyCert provides the revision notes, practice questions and mocks; the hands-on work happens in your own Terraform environment.
Phase 2 — Work through the seven areas (the bulk of the plan)
Pair each lesson with a practice session on the same area, then do the matching exercise in your lab. Read every explanation, including those for options you rejected. In this exam the wrong options are usually real commands or settings that would work in a different situation, and the explanation says which detail in the scenario rules them out.
- Configuration design: turning requirements into code, variables, locals and outputs, for_each, functions, advanced configuration, provider configuration and the Terraform MCP server for AI coding agents.
- State and backends: remote backends and remote state, inspecting state, remediating drift, finding dependency chains before an upgrade and upgrading Terraform across environments.
- Lifecycle and operations: scaling projects, planning and applying, importing existing infrastructure, lifecycle management, multiple environments, troubleshooting, passing data between projects and pinning provider and module versions.
- CI/CD and automation: pipeline functionality, deployment strategies, dynamic provider credentials across teams and workspaces, and overriding variables with .tfvars and .auto.tfvars files.
- Security and governance: handling and rotating secrets, securing pipeline identities, organisation-wide and team-specific policy rules, and spotting risky changes before they apply.
- Modules and the registry: when to extract a module, what a module’s contract is, building from the registry and validating modules with terraform test.
- HCP Terraform and Terraform Enterprise: operating the platform, tracking usage and cost, multi-environment configuration, upgrading Terraform across workspaces and policy as code in the pipeline.
Phase 3 — Drill tracing and prediction (a few days)
Several objectives ask you to read configuration and work out what it produces: trace a variable, local or output to find where a bug comes from, work out which instances a for_each creates, and predict the value of an expression that uses a function. These are the items experience covers least, because at work you would run terraform console and look. Practise answering them on paper first, then check in the console.
HashiCorp’s learning path points at less familiar built-in functions such as one, distinct and flatten, so give the collection and type-conversion functions their own session. Do the same for removing resources from management (a removed block against terraform state rm), moved blocks after a refactor and import blocks, where two options can look equally reasonable until you notice whether the scenario wants the real infrastructure kept or destroyed.
Rebuild practice sessions from your incorrect and flagged questions alongside this, and sort each miss by cause: a fact you did not know, a snippet you misread, or a scenario detail you skipped. The third kind is the one mocks expose.
Phase 4 — Rehearse, then book
Sit full-length timed mocks under exam conditions, with no documentation open and no terraform console. Scenario questions with code take longer to read than the Associate’s direct questions, so use the first mock to find your pace as well as your gaps.
Between mocks, take each wrong answer back to your lab and reproduce it where you can. Use the cheat sheet in the last days to go over each area’s key points. Book once consecutive mocks with different questions clear the pass line comfortably and no area is trailing.
Signals you are ready
Book the exam when all of these are true:
- Consecutive full-length mocks clear the pass line with margin, not one good result.
- You can predict the output of a for_each or a nested function call without running it.
- You can explain what happens to state and real infrastructure for import, moved, removed and terraform state rm.
- You have configured a remote backend with locking, a pipeline using dynamic credentials and a policy check yourself.
- No objective area trails the others in your per-domain results.
Plan your prep
Questions, answered
Sources
Exam facts in this guide come from the vendor's published exam guide. Vendors revise these — check the source for the current version before you book.