TF-IEP002 HashiCorp Terraform Infrastructure Engineer Professional (002)
- Vendor
- HashiCorp
- Level
- Professional
- Questions
- 60
- Time
- 90 min
- Domains
- 7
- In the bank
- 312
Practice 312 questionsTake a timed mock examDay-by-day study plan
Guides for this exam
- Terraform Infrastructure Engineer Professional (002) Study Guide: Four Traces That Solve Most Scenarios · 한국어
- Terraform State Backends and Workspaces: Local vs Remote, CLI vs HCP Terraform, and Which One a Question Wants · 한국어
The exam at a glance
| Level | Professional |
|---|---|
| Questions | 60 |
| Time | 90 minutes (about 1.5 minutes per question) |
| Passing mark | Not published by the vendor |
Domains and weights
The vendor does not publish domain weights for this exam, so the shares below are equal by assumption. Treat every domain as roughly the same size.
| Domain | Weight | Practice questions here |
|---|---|---|
| D1 · Terraform configuration | 14.3% | 63 |
| D2 · State management and upgrades | 14.3% | 37 |
| D3 · Infrastructure workflow and lifecycle | 14.3% | 64 |
| D4 · CI/CD and deployment | 14.3% | 37 |
| D5 · Security, secrets and compliance | 14.3% | 37 |
| D6 · Modules and the registry | 14.3% | 37 |
| D7 · HCP Terraform operations | 14.3% | 37 |
58 of the 312 practice questions (19%) ask for more than one answer.
D1 · Terraform configuration 14.3%
Expect short HCL snippets and team requirements rather than definitions. Some items ask you to predict what an expression returns, others ask which construct enforces a rule, reads an outside fact or configures a provider. The wrong answers tend to be constructs that look close but behave differently, such as a warning where a hard stop was asked for, or a function that treats null and errors alike.
What to watch for
- Decide first whether the rule must stop the run or only report a problem. Validation and preconditions block; a check block only warns.
- When a function result is asked, trace null, missing attributes and errors separately. try, coalesce and merge each treat these cases in their own way.
- For assistant and registry questions, remember that the Terraform MCP server supplies current documentation and workspace data as tools; it does not retrain the model.
Tasks in the official exam guide (8)
- 1.1 Translate business requirements into infrastructure code
- 1.2 Predictable and secure Terraform configuration
- 1.3 Trace input variables, local values, and outputs to identify the source of a configuration issue
- 1.4 Trace dynamic resources created with for_each
- 1.5 Predict the value of an expression that uses a Terraform function
- 1.6 Implement advanced configurations
- 1.7 Configure Terraform providers
- 1.8 Use the Terraform MCP server to enhance development with AI coding agents
D2 · State management and upgrades 14.3%
Most items start from a symptom: a version error on plan, a lock table to retire, a rename across many workspaces, or a need to inspect a large state. The task is to choose the backend setting, block or command that fixes it without losing or rewriting state. Options that edit state by hand or skip a migration step are the usual distractors.
What to watch for
- Treat state format as one-way. When an older CLI cannot read a state, the fix moves the lagging tool forward and tightens required_version.
- Match each inspection need to its command: addresses only, one instance, full machine-readable output, or the dependency graph. The scope of the output usually decides it.
- For renames and refactors in shared modules, prefer a moved block placed inside the module, so every caller picks up the new address on its own next plan.
Tasks in the official exam guide (5)
D3 · Infrastructure workflow and lifecycle 14.3%
This domain follows a change from adoption to apply: importing existing objects, protecting critical ones, splitting projects and loading variables. Scenarios usually include a constraint such as "reviewed before anything changes" or "must not be destroyed", and the right option respects it. Distractors often trade safety for speed, like skipping refresh or editing state directly.
What to watch for
- When a reviewer must see adopted objects first, favour the declarative import path that appears in plan over commands that change state at once.
- In split projects, check run order before blaming code. A consumer reading remote outputs fails if the producer has not applied in that environment.
- Read lifecycle questions carefully: prevent_destroy also blocks replacement, and create_before_destroy is the one rule that Terraform carries over to the resources it depends on.
Tasks in the official exam guide (9)
- 3.1 Manage and scale infrastructure projects
- 3.2 Plan changes to infrastructure
- 3.3 Apply changes to infrastructure
- 3.4 Import existing infrastructure to an infrastructure project
- 3.5 Manage infrastructure lifecycle
- 3.6 Manage multiple infrastructure environments
- 3.7 Troubleshoot deployment issues
- 3.8 Input and output data from infrastructure projects
- 3.9 Manage provider and module versions
D4 · CI/CD and deployment 14.3%
Pipeline questions describe a delivery setup (approval gates, preview environments, variable sets, cloud credentials) and something that went wrong or must be designed. You decide which mechanism keeps the reviewed change identical to the applied one and which identity or variable source wins. Answers that re-plan at apply time or rely on long-lived keys are typical traps.
What to watch for
- An approval only means something when the approved plan file is the one applied. Look for options that save the plan and apply that exact file.
- For variable conflicts in HCP Terraform, check whether a variable set is marked priority; that flag changes which value a workspace run receives.
- Dynamic provider credentials rest on a per-run OIDC token that the cloud verifies before handing out temporary credentials. Trust settings should match the subject, not only the audience.
Tasks in the official exam guide (4)
D5 · Security, secrets and compliance 14.3%
Security items mix three themes: who may do what in HCP Terraform, how secrets stay out of state and plans, and how policies gate or merely flag risky changes. The scenario names a control goal, and you pick the setting that reaches it with the least exposure. Close options often differ in whether they block, warn, or still store the secret.
What to watch for
- Add up permissions from organization, project and workspace scope before deciding what a team can do. A narrow workspace role does not cancel a broad organization grant.
- Ephemeral values may only flow into a short list of places, such as write-only arguments and provider blocks. Check each usage against that list.
- For policy enforcement, separate the levels: one blocks with an override path, one blocks fully, and an advisory policy or a check block only warns.
Tasks in the official exam guide (5)
D6 · Modules and the registry 14.3%
Module questions test design and lifecycle: what a reusable module may contain, how refactors keep existing objects, how registry sources and versions are written, and how terraform test runs and cleans up. Many stems include a code fragment and ask for the plan or the outcome. Wrong options usually assume behavior from plain configuration that does not hold inside modules or tests.
What to watch for
- If a module call fails with count or for_each, look for a provider block inside the module. A reusable module states what it needs and leaves provider configuration to the calling code.
- For a moved block with an instance key, follow the existing objects to that key and expect only the remaining instances to be created.
- Inside terraform test, variables set in the test file take priority over ones passed on the command line, and run blocks are cleaned up in the reverse of their order.
Tasks in the official exam guide (4)
D7 · HCP Terraform operations 14.3%
Here the scenarios come from running HCP Terraform for many teams: workspace triggers in a monorepo, project layout, cost estimates, external review gates and version upgrades. You choose the feature or run option that fits the operating need. The distractors are real features placed at the wrong layer, for example a policy where an external service call is needed.
What to watch for
- When a change starts no run, compare the edited path with the workspace working directory and its trigger patterns or prefixes.
- Map each gate to its tool: an external service reviewing plan data is a run task, while rules expressible in code belong in a Sentinel or OPA policy set.
- Group workspaces by team with projects, so access and credentials are set once per team while environments stay separate workspaces.
Tasks in the official exam guide (5)
A study order that works
The 20-day study plan for TF-IEP002 takes the domains in this order. Each day has a short reading, key terms and a quiz from the bank.
- Days 1–4: D1 · Terraform configuration
- Days 5–7: D2 · State management and upgrades
- Days 8–11: D3 · Infrastructure workflow and lifecycle
- Days 12–13: D4 · CI/CD and deployment
- Days 14–15: D5 · Security, secrets and compliance
- Days 16–17: D6 · Modules and the registry
- Days 18–19: D7 · HCP Terraform operations
- Day 20: Final Review: Exam Format, the Seven Domains, Commonly Confused Pairs and Test-Day Plan
Recent changes to these questions
- : 60 questions added
- : 1 explanation rewritten
About these questions
Every question is original, written from the public exam guide and checked against the vendor's own documentation. None comes from a real exam. Each one has an explanation of why the answer is right and why the other options are wrong. How the questions are written.