Terraform Professional

Associate checks whether you can write and apply working configuration. Professional assumes that and tests judgment: refactoring existing code, recovering state, designing modules other teams depend on, structuring workspaces and team collaboration, and enforcing security and tests. Expect fewer recall items and more scenarios where several answers are technically valid but only one is the right operational choice.

Both multiple choice and multiple select are used, so read each stem for how many options it wants. Select-all items usually hinge on one detail - a lifecycle argument, a version constraint operator, or whether a value is sensitive - so evaluate each option independently rather than eliminating down to a favourite.

HashiCorp publishes the current item count and time limit in its official exam guide and booking page, and those figures change between delivery formats. Check the official site rather than relying on secondhand numbers, then plan your pacing from the real figure before exam day.

Both are set by HashiCorp and published on its certification site, along with any regional pricing differences. Neither is fixed here because they are revised periodically. Look up the current fee and scaled passing score on the official page at the point you are ready to schedule.

Most candidates find it materially harder than Associate because the failure modes are subtle: a module that works but is unversionable, a backend migration that silently loses workspaces, a provider constraint that resolves differently on CI. If you have never debugged state or written a module for someone else, expect several weeks of deliberate practice.

Start with configuration authoring and refactoring, since everything else builds on it. Then state and backends, then module design and consumption. Move to provider and version constraints, then HCP Terraform collaboration, and finish with sensitive data, policy as code and the testing framework - those topics are easiest to absorb once the earlier mechanics are automatic.

Skipping hands-on state work, memorising syntax instead of understanding why an expression or constraint behaves as it does, never using HCP Terraform beyond a free trial workspace, and ignoring the native test framework entirely. Another frequent miss is not reading stems carefully - many wrong answers are correct Terraform that does not satisfy the stated requirement.

Not strictly, but the collaboration domain assumes familiarity with workspaces, VCS-driven runs, variable sets, run triggers and the difference between CLI-driven and remote execution. A free-tier HCP Terraform organisation plus a throwaway GitHub repository and a toy provider gets you most of that experience in a weekend.

Rules differ by delivery method and are stated in HashiCorp's candidate handbook. Read that document before your appointment rather than assuming either way, and prepare as though no reference material is available - the exam rewards recall of behaviour and trade-offs, not fast lookup.

Retake waiting periods and recertification requirements are set and published by HashiCorp, and they have changed over time. Check the official certification site for the current policy before scheduling a second attempt or planning renewal, so you are not working from outdated forum posts.