Exam-Day Guide

Registration (do this on Day 27 if you pass go/no-go)

  1. Sign in to HashiCorp's certification portal and choose Terraform Associate (004).
  2. Pay the fee ($70.50 USD at the time of writing), then pick a date and time. Choose the time of day when you usually study best.
  3. Read the confirmation email for the check-in window, the ID requirements, and the system-check link.

48 hours before

  • Run the official system check on the exact computer and network you'll use. A work laptop's VPN, security agent, or locked-down browser often blocks proctoring software. A personal machine is usually safer.
  • Confirm your government-issued photo ID is current, and that the name matches your registration exactly.
  • Choose a private, quiet room with a door. Clear the desk completely: no notes, extra monitors, phones, or smart watches within reach.
  • Plan for a stable wired connection, or position yourself close to the Wi-Fi router.

Exam morning

  • 60 minutes before: use the restroom and get water if it's allowed. You can't leave during the exam.
  • 30 minutes before: close every application, and turn off notifications and automatic updates. Unplug second monitors.
  • Check in early. The ID check and room scan take time and don't count toward the exam clock.

Time management (1 hour; HashiCorp doesn't publish the question count)

Divide the time into three passes:

Pass Time Goal
1. Sweep First ~35 min Answer every question you're confident about in under a minute. Flag anything that needs more thought, and move on.
2. Return Next ~15 min Work through flagged questions using elimination.
3. Review Last ~10 min Re-read the multi-select questions and anything you changed. Only change an answer if you find a concrete reason.
  • When you first see the questions, note how many there are and set checkpoints at the ¼, ½, and ¾ marks. For example, by the 15-minute mark you should be roughly a quarter of the way through.
  • Never leave a question blank. There's no known penalty for guessing, so pick your best elimination answer and flag it.

Question-reading strategy

  1. Read the last sentence first. It tells you what's being asked, for example "Which command…" or "What happens…".
  2. Note the selection count. "Select TWO" means exactly two.
  3. Find the deciding detail. Common ones:
    • CLI vs. HCP Terraform workspace
    • Saved plan vs. new plan
    • State vs. infrastructure vs. configuration
    • Root vs. child module
    • Registry vs. Git source
    • sensitive vs. ephemeral
    • Error vs. warning
  4. Eliminate by misconception. Distractors usually encode one of the Exam Traps from the modules. Name the trap, and the option falls away.
  5. Distrust absolutes. "Always," "never," "automatically," and "any cloud" are usually wrong, unless they describe genuinely absolute behavior such as "terraform import never creates infrastructure."
  6. Answer for Terraform 1.12 and current HashiCorp guidance. Prefer -replace over taint, moved/removed/import blocks over CLI state surgery, use_lockfile over DynamoDB, the cloud block over backend "remote", and terraform_data over null_resource.

Flag-and-return technique

If the exam interface offers flagging and a review screen:

  • Flag a question if you can't eliminate down to one option within about 60 seconds. Write down your current best guess first.
  • On the return pass, start with the flagged questions where you'd narrowed it to two options. Those give the best return on time.
  • Later questions sometimes jog your memory for earlier ones. Note this, but don't hunt for it.

If the interface turns out not to allow returning to questions, switch strategy: answer each question as you go, with a 90-second ceiling per question.

The ten traps most worth re-reading the night before

  1. Variable precedence: default < TF_VAR_ < terraform.tfvars < *.auto.tfvars (lexical order) < -var/-var-file.
  2. ~> 1.2 allows up to < 2.0. ~> 1.2.0 allows up to < 1.3.0.
  3. The lock file records providers only, never modules. Commit it.
  4. version works only on registry module sources. Git sources use ?ref=.
  5. sensitive hides output but still stores the value in state. Ephemeral and write-only values aren't stored.
  6. A check block warns. Validation, preconditions, and postconditions error.
  7. apply -refresh-only updates state. To keep a manual change permanently, update the configuration too.
  8. state rm with the block still present means the next plan creates a duplicate. Use removed { lifecycle { destroy = false } } instead.
  9. CLI workspaces share one backend and configuration. HCP Terraform workspaces have their own variables, permissions, and run history.
  10. VCS-connected workspaces reject a CLI apply. Pull requests get speculative plans that can never be applied.