cert-bank

Exams

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

The exam at a glance

LevelProfessional
Questions60
Time90 minutes (about 1.5 minutes per question)
Passing markNot 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.

DomainWeightPractice questions here
D1 · Terraform configuration14.3%63
D2 · State management and upgrades14.3%37
D3 · Infrastructure workflow and lifecycle14.3%64
D4 · CI/CD and deployment14.3%37
D5 · Security, secrets and compliance14.3%37
D6 · Modules and the registry14.3%37
D7 · HCP Terraform operations14.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

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

Tasks in the official exam guide (5)
  • 2.1 Create and manage remote backend and remote state configuration
  • 2.2 Manage state and remediate drift
  • 2.3 Identify dependency chains before upgrades
  • 2.4 Upgrade Terraform versions across environments
  • 2.5 Inspect Terraform state

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

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

Tasks in the official exam guide (4)
  • 4.1 Manage CI/CD pipeline functionality
  • 4.2 Understand deployment strategies
  • 4.3 Manage multiple sets of dynamic provider credentials across teams, projects, and workspaces
  • 4.4 Overwrite Terraform variables using auto.tfvars / .tfvars

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

Tasks in the official exam guide (5)
  • 5.1 Identify best practices for secrets
  • 5.2 Use secret rotation and integration with secrets management tools
  • 5.3 Secure CI/CD pipeline identities and access
  • 5.4 Establish core compliance/policy rules along with team/project specific policies
  • 5.5 Identify and mitigate risky infrastructure changes

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

Tasks in the official exam guide (4)
  • 6.1 Understand when to refactor a Terraform configuration into a module
  • 6.2 Understand the contract of a Terraform module
  • 6.3 Use the Terraform registry to build or update a configuration
  • 6.4 Validate modules with Terraform unit tests

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

Tasks in the official exam guide (5)
  • 7.1 Understand how to operate HCP Terraform
  • 7.2 Track resource usage and cost
  • 7.3 Implement multi-environment configuration
  • 7.4 Upgrade Terraform versions across workspaces
  • 7.5 Define policy as code in a CI/CD pipeline

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.

  1. Days 1–4: D1 · Terraform configuration
  2. Days 5–7: D2 · State management and upgrades
  3. Days 8–11: D3 · Infrastructure workflow and lifecycle
  4. Days 12–13: D4 · CI/CD and deployment
  5. Days 14–15: D5 · Security, secrets and compliance
  6. Days 16–17: D6 · Modules and the registry
  7. Days 18–19: D7 · HCP Terraform operations
  8. Day 20: Final Review: Exam Format, the Seven Domains, Commonly Confused Pairs and Test-Day Plan

Recent changes to these questions

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.