Free Terraform Pro 002 mock exams
Timed HashiCorp Certified: Terraform Infrastructure Engineer Professional (002) rehearsals: 65 questions in 90 minutes, the real exam's time limit, drawn across the official objectives. HashiCorp has not yet published the exam's question count or pass mark, so the paper length and the 700 / 1000 pass line are ours.
- Questions
- 65our paper length
- Time limit
- 90 minserver-timed
- Pass mark
- 700on a 100–1000 scale
- Papers
- 3retake any of them
More ways to rehearse
Every attempt draws questions you haven't met yet first · Pro.
A full-length paper drawn to the same domain weights, from the questions we rate hardest — the ones that combine two facts or weigh workable options against each other.
One exam domain at the real exam's pace — for the domain your last mock went worst in.
What's in a Terraform Pro 002 mock paper
Each paper draws its questions per domain in the same proportions HashiCorp publishes for the real Terraform Pro 002 — so a mock that goes badly in one domain is telling you something a randomly-drawn quiz couldn't.
| Domain | Official weight | Questions drawn | Share of paper |
|---|---|---|---|
| Scalable Terraform configuration design | 20% | 13 | 20% |
| Terraform state and backend operations | 13% | 8 | 12% |
| Infrastructure lifecycle and operations | 22% | 14 | 22% |
| CI/CD and automation workflows | 10% | 7 | 11% |
| Terraform security and governance | 13% | 8 | 12% |
| Advanced module usage and registry practices | 10% | 7 | 11% |
| HCP Terraform and Terraform Enterprise operations | 12% | 8 | 12% |
| Total | 100% | 65 | 100% |
What a Terraform Pro 002 paper is shaped like
Which way this particular paper applies pressure.
The clock
HashiCorp has not yet published the question count, so this is the pace of our 65-question papers on the real 90-minute clock. At roughly 1.4 minutes a question, the pacing is comfortable but not generous. You can afford to think on a hard question, and you cannot afford to do it twice. Most candidates finish with time for a second pass if they keep the first pass moving.
The weighting
The weighting is unusually flat — 7 domains with no single one dominating, the largest being Infrastructure lifecycle and operations at 22%. Nothing can be safely skipped, and there is no high-weight domain to carry a gap. Breadth beats depth on this paper.
The standard
HashiCorp publishes no pass mark for the Terraform Pro 002: results are reported as pass or fail. Our mocks score you on the 100–1000 scale with a line at 700, which is our yardstick, not the vendor's. Treat a result just over it as a fail in disguise and book only with a clear margin.
Pacing a Terraform Pro 002 paper
Where you need to be on the clock, quarter by quarter.
| Checkpoint | Elapsed | Be at question | Questions left |
|---|---|---|---|
| First quarter | 23 min | 16 | 49 |
| Halfway | 45 min | 33 | 32 |
| Three quarters | 68 min | 49 | 16 |
| Time called | 90 min | 65 | 0 |
What trips people up on a Terraform Professional mock
HashiCorp has not yet published a question count, a pass mark or domain weights for the 002 exam. Our mocks are spread by the number of official sub-objectives in each area and scored on a conventional scale, so read the per-domain results as a map of what you do not know rather than a forecast of the real score. A weak area here is a weak area on the real paper whatever its share turns out to be.
Many items put HCL, plan output or an error message in the question and ask what Terraform will do or what caused it. Associate-level habits fail here: knowing which command exists is not enough when the options are four valid-looking commands, addresses or blocks that each break one rule. Trace the code before reading the options, and decide what you expect before you look.
State, lifecycle and the pipeline are where professional candidates lose the most marks, because the right answer depends on what Terraform does to state at each step: imports, moved and removed blocks, replacements, drift, and how a change behaves when a pipeline runs it with remote state and limited credentials. Experience helps only where it matches; teams that never use one of these features meet it cold.
The paper tests Terraform 1.15 and current HCP Terraform behaviour, including newer features such as ephemeral values, write-only arguments, terraform test and the Terraform MCP server for AI coding agents. Material written for older releases leaves gaps there, and if those topics trail on your mocks while the classic ones are steady, the cause is coverage rather than difficulty.
Governance and HCP Terraform items usually offer several workable controls: a policy set, a run task, a variable set, team permissions, dynamic credentials. The deciding factor is the scope and the moment named in the question: which workspaces, which teams, and whether the check must block a run or only report. Sit your mocks to time so that reading scope carefully becomes a habit rather than a luxury.
Before you sit a Terraform Pro 002 mock
Terraform Pro 002 mock exams: your questions
Source
Exam structure, domain weights and scoring on this page come from the official Terraform Pro 002 exam guide.