Terraform Associate certification exam
Online live-proctored multiple-choice assessment
- Type
- Written
- Delivery
- Online
- Duration
- 60 min
Exam sections
Infrastructure as Code with Terraform
Within Terraform Associate, “Infrastructure as Code with Terraform” examines reliable repetition, step sequencing, inputs, idempotence, exceptions, rollback, and controlled change. Candidates must show that the workflow reaches the intended state consistently across reruns and exposes failure in a recoverable form. It leads into “Terraform fundamentals” in the published outline.
Question notes
Knowing the heading “Infrastructure as Code with Terraform” is not sufficient; the best response should remain consistent with product architecture and operational safety. The principal risk is hidden dependency order, unsafe repeated execution, exceptions that are hidden or mishandled, or an incomplete reversal. The response should be supported by execution history, state comparison, error output, recovery record, and a successful repeat run. The record contains no separate provider figure for item volume or objective-level timing.
Preparation tips
Make preparation for “Infrastructure as Code with Terraform” observable. Practical exercise: Map triggers, inputs, dependencies, and outputs before implementing the automation; then test normal, exception, and retry paths. Ask a reviewer to test for hidden dependency order, unsafe repeated execution, poor exception behavior, or recovery that leaves partial state behind. Give the reviewer recorded sequence of execution, state comparison, error output, recovery record, and a successful repeat run. Document any dependency the selected approach creates for “Terraform fundamentals”.
Terraform fundamentals
The “Terraform fundamentals” portion of Terraform Associate focuses on the required inputs, accountable work, dependencies, and proof of completion unique to “Terraform fundamentals”. A complete response should explain the purpose of “Terraform fundamentals,” identify its dependencies, then support the selected action or conclusion with suitable evidence. In the published sequence, it follows “Infrastructure as Code with Terraform” and precedes “Core Terraform workflow”.
Question notes
The assessment may connect “Terraform fundamentals” with other objectives: the best response should remain consistent with product architecture and operational safety. A weak result can be exposed by a plausible “Terraform fundamentals” response that does not remain defensible after its inputs, effects, and support are reviewed. A complete result leaves a trace connecting the “Terraform fundamentals” requirement, chosen response, and independently reviewed result. Because no published weight is stored, the prose makes no claim about exact assessment allocation.
Preparation tips
Rehearse “Terraform fundamentals” under a realistic constraint. Use this exercise: Create two contrasting examples for “Terraform fundamentals,” explain why the stronger example meets the objective and how the weaker case can be disproved. Then test treating “Terraform fundamentals” as terminology recall but overlooks the dependency or condition that determines the result. Decide what must change by inspecting before-and-after observations for “Terraform fundamentals,” accompanied by the recorded rationale and the evidence required for acceptance. Finish with a handoff checklist for “Core Terraform workflow”.
Core Terraform workflow
For “Core Terraform workflow,” the relevant professional context is predictable re-execution, step sequencing, inputs, idempotence, exceptions, rollback, and controlled change. The candidate is expected to show that the workflow reaches the expected outcome on successive attempts, while making failures visible and recoverable, rather than answer from keyword familiarity alone. In the published sequence, it follows “Terraform fundamentals” and precedes “Terraform configuration”.
Question notes
Knowing the heading “Core Terraform workflow” is not sufficient; a scenario may ask about both expected product behavior and the safest operational choice. The principal risk is hidden execution order, a rerun that changes the result, unhandled exceptions, or a recovery path that does not return to a safe state. The response should be supported by workflow record, state comparison, error output, evidence of restored state, and a successful repeat run. This note leaves both stand-alone duration and question quantity unspecified.
Preparation tips
For “Core Terraform workflow,” use an explain–perform–verify loop. Exercise: Run the workflow from a clean starting point, repeat it, fail one step deliberately, and prove that recovery leaves no partial state. Explain how this evidence confirms the “Core Terraform workflow” result: recorded sequence of execution, state comparison, error output, recovery record, and a successful repeat run. Also test for hidden step sequencing, a rerun that changes the result, weak failure management, or rollback behavior that leaves the workflow inconsistent. Use the completed work to challenge a decision in “Terraform configuration”.
Terraform configuration
“Terraform configuration” tests whether a candidate understands consistent reruns, execution order, explicit inputs, safe reruns, exception behavior, recovery, and governed change. That understanding must support an ability to show that the workflow reaches the target condition more than once, with failure behavior that can be seen and corrected. In the published sequence, it follows “Core Terraform workflow” and precedes “Terraform modules”.
Question notes
Question or task wording for “Terraform configuration” may hide its decisive constraint because questions or tasks may expose dependencies between this area and the wider product workflow. Required negative check: hidden step sequencing, a rerun that changes the result, poor exception behavior, or recovery that leaves partial state behind. Supporting evidence: recorded sequence of execution, state comparison, error output, recovery record, and a successful repeat run. No independent timing or assessment inventory is attributed to this objective.
Preparation tips
Keep a short decision journal for “Terraform configuration.” Complete this exercise: Run the workflow from a clean starting point, repeat it, fail one step deliberately, and prove that recovery leaves no partial state. Record whether you detected or prevented hidden ordering, non-idempotent behavior, inadequate handling of failure, or a rollback that does not restore the prior condition. Attach workflow record, state comparison, error output, recovery record, and a successful repeat run. Explain which assumptions this leaves for “Terraform modules”.
Terraform modules
Within Terraform Associate, “Terraform modules” examines organization of the implementation, connected components, validation, security by default, release evidence, and sustainable implementation. Candidates must produce a working implementation, challenge its assumptions with tests, deploy it, and investigate observed failure. In the published sequence, it follows “Terraform configuration” and precedes “Terraform state management”.
Question notes
Knowing the heading “Terraform modules” is not sufficient; questions or tasks may expose dependencies between this area and the wider product workflow. The principal risk is untested edge behavior, unstated dependency assumptions, unsafe starting configuration, or an implementation that cannot be supported. The response should be supported by tests, compiler or packaging results, runtime observations, deployment history, and traceable design decisions. Prepare the complete objective because the payload does not assume how many tasks or questions represent it.
Preparation tips
Rehearse “Terraform modules” under a realistic constraint. Use this exercise: Build the smallest working implementation, add boundary tests, deploy it, and diagnose one deliberately introduced defect. Then test behavior outside the tested path, implicit dependencies, weak secure-by-default behavior, or code that cannot evolve safely. Decide what must change by inspecting tests, build records, observed runtime behavior, release evidence, and a documented explanation of the design. Finish with a handoff checklist for “Terraform state management”.
Terraform state management
At the center of “Terraform state management” is data shape, ownership, lifecycle, consistency, and downstream effects of a change. The credential therefore evaluates whether a candidate can show how state is created, accessed, transformed, maintained, consumed, and eventually retired. In the published sequence, it follows “Terraform modules” and precedes “Maintain infrastructure with Terraform”.
Question notes
The assessment may connect “Terraform state management” with other objectives: candidates should expect the surrounding workflow to determine which product feature is appropriate. A weak result can be exposed by undetected loss, old information, poor stewardship, or undocumented expectations about schema and lifecycle. A complete result leaves a recorded state comparison, provenance records, consistency checks, and results captured by a dependent system. Neither isolated timing nor item volume is inferred for this part of the outline.
Preparation tips
Make preparation for “Terraform state management” observable. Practical exercise: Test an update, an access change, and a retirement case while checking lineage, integrity, and consumer behavior. Ask a reviewer to test for hidden information loss, old information, poor stewardship, or undocumented expectations about schema and lifecycle. Give the reviewer before-and-after state, a data-path trace, reconciliation evidence, and behavior recorded by a later process. Explain which assumptions this leaves for “Maintain infrastructure with Terraform”.
Maintain infrastructure with Terraform
“Maintain infrastructure with Terraform” tests whether a candidate understands the decisions and dependencies unique to “Maintain infrastructure with Terraform,” together with evidence that makes the professional outcome visible. That understanding must support an ability to move through “Maintain infrastructure with Terraform” from context and decision to execution, communication, or confirmation as appropriate. In the published sequence, it follows “Terraform state management” and precedes “HCP Terraform”.
Question notes
The assessment may connect “Maintain infrastructure with Terraform” with other objectives: candidates should expect the surrounding workflow to determine which product feature is appropriate. A weak result can be exposed by treating “Maintain infrastructure with Terraform” as terminology recall and misses the operating condition on which the result depends. A complete result leaves a repeatable “Maintain infrastructure with Terraform” result, reasoning another practitioner can follow, and proof that the objective was satisfied. Coverage is preserved without inventing numerical emphasis, assessment inventory, or a time block.
Preparation tips
Rehearse “Maintain infrastructure with Terraform” under a realistic constraint. Use this exercise: Turn “Maintain infrastructure with Terraform” into a realistic case, state the expected result, complete it independently, and preserve the verification. Then test accepting work on “Maintain infrastructure with Terraform” while its reasoning or result still cannot be reproduced. Decide what must change by inspecting a trace connecting the “Maintain infrastructure with Terraform” requirement, chosen response, and independently reviewed result. Finish with a handoff checklist for “HCP Terraform”.
HCP Terraform
For “HCP Terraform,” the relevant professional context is what initiates the work, who is responsible, what it depends on, and how completion is shown for “HCP Terraform”. The candidate is expected to apply “HCP Terraform” with one new limitation and document which decisions transfer and which do not, without treating isolated vocabulary as proof of competence. It draws on work established in “Maintain infrastructure with Terraform”.
Question notes
Before acting on “HCP Terraform,” read the full scenario; the assessment can require interpretation of behavior rather than recall of one command. Test the response for a plausible “HCP Terraform” response that has no adequate defense after an independent review of inputs, effects, and verification. Confirm the outcome with before-and-after observations for “HCP Terraform,” plus a traceable decision record and proof that acceptance conditions were met. This objective has no separately claimed time allowance or item quantity.
Preparation tips
Build preparation for “HCP Terraform” around context, action, failure, and proof. Exercise: Practice “HCP Terraform” against a second constraint and compare the new reasoning with the original approach. The checklist must expose accepting work on “HCP Terraform” until another practitioner can repeat the logic and inspect the final result. Required proof: before-and-after observations for “HCP Terraform,” alongside documented reasoning and any stakeholder or technical acceptance evidence. Compare the result with the assumptions established during “Maintain infrastructure with Terraform”.