EnglishDeutschFrançaisEspañolPortuguês

HashiCorp · HC-TFP · Professional

HashiCorp Terraform Authoring and Operations Professional — Practice Questions and Mock Exam

Prepare for HC-TFP with original practice questions and clear answer explanations. Ask Alex, your AI tutor, when you need more detail, use your results to identify topics to review, and practice your pacing with timed mock exams.

240minTime limit

Checked against HashiCorp · September 2026 · Current exam version

About the exam

The HashiCorp Certified: Terraform Authoring and Operations Professional credential validates advanced, production-grade expertise with Terraform and HCP Terraform. It confirms that you can design reusable module hierarchies, engineer secure and scalable state strategies, implement policy as code, manage drift at scale, and operate Terraform across complex multi-team, multi-environment organizations. The six exam domains emphasize authoring depth, operational judgment, and troubleshooting under realistic constraints.

This certification targets senior platform engineers, infrastructure architects, and Terraform practitioners with at least one to two years of hands-on production experience. It is particularly valuable for those running centralized platform teams, building internal developer platforms on top of Terraform, or owning HCP Terraform and Terraform Enterprise deployments for their organization.

Try five HC-TFP questions

Try five practice questions from the app’s current HashiCorp Certified: Terraform Authoring and Operations Professional question bank, with answers and explanations.

Collaborate on infrastructure as code using HCP Terraform1 / 5

An HCP Terraform workspace is connected to a VCS repository with `Branch: main` and `Working Directory: infra/`. Which event automatically queues a plan?

AlexFull explanation from Alex

VCS-driven HCP Terraform workspaces register webhooks and queue runs only when commits land on the configured branch and modify files within the configured working directory. With Branch: main and Working Directory: infra/, only commits to main touching infra/ trigger a plan. The option “Any commit to any branch of the connected repository” ignores both branch and directory filters. The option “Commits whose message contains "[apply]" or "[plan]"” describes a commit-message convention HCP Terraform does not support. The option “A pull request opened against any branch of the repo” confuses speculative plans (triggered by PRs) with the auto-queued plan behavior tied to branch commits. Ref: developer.hashicorp.com/terraform/cloud-docs/workspaces/settings; /terraform/cloud-docs/workspaces/run/ui

Sourcedeveloper.hashicorp.com

Develop Collaborative Terraform Workflows2 / 5

Which optional argument in the `backend "s3"` block enables state locking via a managed table?

AlexFull explanation from Alex

The S3 backend's dynamodb_table argument specifies a DynamoDB table (with a String partition key named LockID) that Terraform uses for distributed state locking during operations, preventing concurrent modifications that could corrupt state. lock_table, state_lock, and ddb_lock are not valid arguments and would cause terraform init errors. Newer Terraform versions also support native S3 conditional-write locking, but dynamodb_table remains the long-standing mechanism. Ref: developer.hashicorp.com/terraform/language/backend/s3#state-locking; /terraform/language/state/locking

Sourcedeveloper.hashicorp.com

Develop and Troubleshoot Dynamic Configuration4 / 5

Which block lets you enforce that a variable's value matches a specific format, such as starting with `vpc-`?

AlexFull explanation from Alex

A validation block inside a variable definition runs a custom condition expression (e.g., can(regex(^vpc-, var.id))) and surfaces an error_message if the value fails, enforcing input format at plan time. precondition belongs inside lifecycle blocks on resources/data sources for runtime assertions. check is a top-level block for ongoing assertions against infrastructure state. lifecycle is a resource meta-argument controlling create_before_destroy and similar behaviors, not variable input validation. Ref: developer.hashicorp.com/terraform/language/values/variables#custom-validation-rules

Sourcedeveloper.hashicorp.com

Create, Maintain, and Use Terraform Modules5 / 5

Which meta-argument lets a module be called once per element of a map, producing one instance of the module per key?

AlexFull explanation from Alex

for_each accepts a map or set of strings and creates one module instance per element, each addressable as module.name["key"] (Ref: developer.hashicorp.com/terraform/language/meta-arguments/for_each). It is the recommended approach when instances are logically identified by a key rather than a numeric index, because adding or removing keys does not shift other instances. count creates instances by index and is fragile when the collection changes order — a removed middle element renumbers all subsequent ones. providers maps provider configurations into a child module. depends_on declares explicit ordering dependencies but does not create instances.

Sourcedeveloper.hashicorp.com

What's on the exam

Four of six domains tie at 17%: managing the resource lifecycle through init, plan, apply, and state operations; developing and troubleshooting dynamic configuration with HCL functions and meta-arguments; collaborative workflows built on version constraints and remote state; and authoring, refactoring, and versioning modules. Providers and HCP Terraform collaboration close the list at 16% each, covering provider authentication and troubleshooting, plus policy enforcement and workspace governance.

Unlike the Associate exam's eight-way split, six domains at this tier means each one carries enough weight to fail a candidate outright — a professional who can author modules but can't troubleshoot a provider authentication failure under exam conditions is exposed on a sixth of the exam, not a narrow corner of it.

Exam blueprint: HC-TFP

Manage Resource Lifecycle18%

Init options, plan options, apply options, destroy options, importing resources, reconciling resource drift.

≈ 15 h
Develop and Troubleshoot Dynamic Configuration16%

Language validation features, data sources, HCL functions, meta-arguments, input variables and outputs with complex types, sensitive data and Vault secrets management.

≈ 13 h
Develop Collaborative Terraform Workflows17%

Version constraints for binaries/providers/modules, remote state configuration, workflow automation, data sharing across configurations and workspaces.

≈ 14 h
Create, Maintain, and Use Terraform Modules17%

Module creation, usage, refactoring, versioning, converting existing configurations into modules.

≈ 14 h
Configure and Use Terraform Providers15%

Plugin-based architecture, provider aliasing/versioning/sourcing, authentication management, troubleshooting provider errors.

≈ 12 h
Collaborate on infrastructure as code using HCP Terraform16%

HCP Terraform run workflow analysis, workspace configuration and access management, provider credentials, policy as code and governance features.

≈ 13 h

The shares below describe how questions in the Pass-IT practice pool are distributed across domains. Refer to HashiCorp for the official exam blueprint.

Exam format and question types

The Professional exam runs four hours, including a 15-minute break, and combines hands-on lab scenarios in a pre-provisioned Linux environment with multiple-choice and fill-in-the-blank questions; a US QWERTY keyboard is required. Lab tasks require writing and fixing Terraform HCL against a live environment, resolving state problems, and wiring up HCP Terraform features such as workspaces, variable sets, and policy sets, while the multiple-choice portion checks the same objectives at a conceptual level. HashiCorp does not publish how the four hours split between labs and multiple-choice, so section timers on screen are the only guide during the exam.

Question types: HC-TFP

Multiple Choice100%

Select the single answer that best meets the question’s requirements.

See HashiCorp for official question-format information. The shares shown describe the Pass-IT practice pool; they do not establish the proportions on the official exam.

Preparing for HC-TFP

The exam is delivered online through Certiverse with a live proctor for the full four-hour session. The credential holds for two years, and renewing means passing the Professional exam again.

Preparation and logistics: HC-TFP

Preparation

Illustrative study time50–120 h

illustrative planning range: 50 h with relevant experience to 120 h when starting out; your needs may fall outside this range

LevelProfessional
Recommended backgroundTerraform Associate certification (strongly recommended). Linux skills. Experience with YAML, JSON, HCL, CSV. Networking fundamentals (TCP/IP, UDP). Extensive cloud provider production experience. Advanced configuration authoring skills.

Taking and maintaining the certification

DeliveryOnline proctored via Certiverse
Retake policyIncludes one free retake.
Certification validity2 years

Pass the Terraform Professional exam again to renew.

Common pitfalls

Topics to review: HC-TFP

  1. 01Sentinel enforcement

    advisory warns, soft-mandatory can be overridden by admins, hard-mandatory cannot. Mixing up the three levels costs direct questions.

  2. 02State surgery

    terraform state mv/rm only edits state; rm does not destroy infrastructure. Always pull, back up and verify before operating on state.

  3. 03Module composition

    Passing providers explicitly to child modules is required for multi-region; implicit inheritance only covers the single-provider case.

  4. 04Run triggers

    HCP Terraform run triggers chain workspaces on apply, not plan. Misordering producer and consumer breaks the deployment chain.

  5. 05Dynamic blocks

    Overusing dynamic blocks for static configuration hurts readability; they are only needed when the block structure depends on data.

Frequently asked questions

Which pitfalls should I review when preparing for HashiCorp Certified: Terraform Authoring and Operations Professional?

Topics to review include Sentinel enforcement, State surgery, Module composition, Run triggers, Dynamic blocks. Work through examples to check that you understand the distinctions and can explain your answer.

Do you need the Terraform Associate before the Professional exam?

HashiCorp strongly recommends it but does not require it. Beyond that the assumed background is broad: Linux skills, YAML, JSON, HCL and CSV, networking fundamentals, and extensive production experience with a cloud provider. The catalog budget of 80 hours assumes all of that is already in place.

How long is the Terraform Professional exam?

Four hours. HashiCorp does not publish a fixed question count for it, which is why our page shows a time limit but no number of questions. The length is the point: it is a long exam built around configuration work rather than recall.

What does the Terraform Professional exam cover?

Six objectives, weighted almost evenly: resource lifecycle, dynamic configuration and troubleshooting, collaborative workflows and module authoring at 17% each, with providers and HCP Terraform collaboration at 16%. Nothing dominates. Preparation that skips module authoring or dynamic configuration gives away a sixth of the exam either way.

How do you renew the Terraform Professional certification?

By passing the Professional exam again before the two-year mark. There is no continuing-education alternative and no higher HashiCorp Terraform exam to renew it for you.

What happens if you fail the Terraform Professional exam?

One retake is included with the registration, which is unusual and worth knowing before you book. It removes the second-attempt hesitation that stops people sitting a four-hour exam they are unsure about.

One certification, 12 months

Practice for HC-TFP

Focus your practice on one certification, or choose Pro to practice across all certifications.

Start a free practice sessionTry the first 20 questions without a card to see whether the practice suits you.

For eligible purchases: money-back guarantee if you fail your exam.

View guarantee terms →