Terraform Associate (003): Exam Scope, Scoring, and Registration Guide

Terraform Associate (003) is an associate-level exam that validates your ability to apply Terraform to the fundamentals of infrastructure automation. Most topics map directly to day-to-day operations, so studying for it builds real-world skill at the same time.

This article uses the official exam domains as the backbone for setting study priorities, then summarizes how scoring works, the registration and exam-day process, and the workflow essentials from an exam-prep angle. Exact percentages and operational policies can change, so always check the latest official HashiCorp information before exam day.

Exam Overview

Terraform Associate (003) is a multiple-choice exam that broadly covers Terraform fundamentals, the CLI workflow, the configuration language, state management, modules, and the basics of Terraform Cloud/Enterprise. There are no prerequisites; the main audience is infrastructure engineers, SREs, cloud platform engineers, and developers adopting IaC.

The exam focuses on concepts that are stable in the Terraform 1.x line: the init/plan/apply workflow, state files and backends, providers, modules, variables and outputs, and the core features of Terraform Cloud. Operational details (question count, time limit, supported languages, etc.) can change, so review the official exam guide and testing terms right before you book.

• Level: Associate (entry-level through solid fundamentals)
• Format: a mix of single-answer multiple choice, multi-select, and scenario-based questions
• Audience: IaC practitioners, and individuals or teams rolling out Terraform

Exam Domains and Study Priorities

The official exam blueprint defines learning objectives and weighting hints for each domain. The exact question counts and strict weights are not published, but the blueprint is still useful for budgeting study time. The list below shows representative domains tied to stable Terraform concepts, with priorities reflecting real-world importance. Treat the percentages as a reference range for study allocation, and always defer to the latest official information.

The CLI workflow, state management, and the HCL configuration language come up constantly in real work and are repeatedly targeted on the exam, so studying them pays off. Terraform Cloud/Enterprise has a wide feature surface, but for the Associate exam it is most efficient to focus on the overview and basic operations: remote execution, VCS integration, workspaces, and variable management.

• Core IaC and Terraform concepts and use cases
• The CLI workflow (init/validate/plan/apply/destroy) and key flags
• HCL syntax: resources, data sources, variables, outputs, locals, count/for_each, and dynamic blocks
• State management: state, backends, remote locking, and drift detection
• Modules: reuse, inputs/outputs, and reading the Registry
• Terraform Cloud/Enterprise basics: workspaces, remote execution, VCS integration, and the policy model

Question Format and Scoring

Questions are mostly multiple choice (single or multi-select) and scenario-based. Items often include Terraform's standard CLI output or HCL snippets and check whether you can read them correctly. Word problems about CLI behavior (plan vs apply, what each flag does) and state-management behavior (locking, backend configuration) come up frequently.

Pass/fail is determined by a scaled score, and per-question weighting and partial credit are not published. To preserve time for pacing and review, lock in the questions you are confident about first, flag the ones you are unsure of, and circle back at the end.

• Multi-select questions include "choose all that apply" items, so watch for option independence and overlap
• On CLI output reading questions, accurately distinguish between the diff/plan contents (Add/Change/Destroy) and warnings vs errors
• Terraform Cloud questions tend to test feature overviews and when to apply them — do not over-study detailed operational options

From Registration to Exam Day

You register through the HashiCorp certification portal, which schedules through an exam vendor (usually an online-proctoring provider). After creating an account, select Terraform Associate (003), choose a time slot and delivery format (online proctoring is most common), and pay. The operator, vendor, and procedural details can change, so always follow the current instructions on the official site.

Online exams require government-issued photo ID, a quiet testing environment, and a working camera, microphone, and stable internet connection. At check-in you will photograph your ID, do a room scan, and run a system check on your testing device. Reschedule and cancellation deadlines, how to get a receipt, and tax handling all follow the exam vendor's terms.

• High-level steps: create a HashiCorp ID → pick the exam in the certification portal → schedule a slot → pay → run the pre-exam system check → take the exam
• What you need: photo ID, camera/mic, a stable internet connection, and a quiet private room
• Exam day: complete check-in before starting and follow the proctor's instructions (personal items and notes on the desk are generally not permitted)

Terraform Workflow Essentials for the Exam and the Job

What pays off most on the Associate exam is being able to clearly explain the init → validate → plan → apply loop and articulate state management and the meaning of plan diffs. Practical topics like backends (local vs remote), locking, drift detection, import, and -refresh-only also become scoring opportunities once you understand the concept and when to apply each one.

The key value of Terraform Cloud's remote execution is managing variables and VCS integration per workspace, plus the ability to retain plan/apply history and an approval flow. If you are running OSS-only, get clear on concurrent-execution protection with setups like S3 + DynamoDB locking, state partitioning and naming conventions, and operating via the state command (list/show/mv/rm) — that knowledge makes a real difference on scenario questions.

• plan is a "proposal of what will happen"; apply is the "actual change"
• Understand -var/-var-file, environment variables (TF_VAR_), and variable precedence
• Changing a backend involves state migration, so be able to articulate the procedure and the blast radius
• Terraform Cloud: understand the existence and role of VCS integration, manual triggers, queued runs, and policy checks

Core Terraform workflow

┌───────────┐      terraform init       ┌────────────┐
│ .tf / modules │ ───────────────────────▶ │ Provider取得│
└──────┬──────┘                          └──────┬─────┘
       │ terraform validate                     │
       └────────────────────────────────────────┤
                                                │
       terraform plan (-out=planfile)           │ 認証/Backend設定
┌──────▼──────┐                           ┌──────▼─────┐
│ 計画差分    │ ◀──────────────────────── │ Backend     │
│ (+/-/~)     │  state参照・drift検出       │ (local/remote)│
└──────┬──────┘                           └──────┬─────┘
       │ terraform apply planfile               │ ロック/並行制御
       ▼                                        ▼
┌────────────┐                         ┌────────────┐
│ 実インフラ  │  ◀────────────────────── │ state(.tfstate)│
└────────────┘      更新・反映           └────────────┘
             （Terraform Cloudの場合: VCS連携/リモート実行/承認）

A typical CLI sequence (local, then mixed with remote)

# 初期化と整形/検証
terraform fmt -check
terraform init -upgrade
terraform validate

# 計画と適用（明示的なplanfileを使うと安全）
terraform plan -var-file=env/dev.tfvars -out=tfplan
terraform apply tfplan

# 状態の点検とメンテ
terraform state list
terraform state show aws_instance.web
# リソース移動（モジュール化などのリファクタ時）
terraform state mv aws_instance.web module.web.aws_instance.web

# ワークスペース（環境の分離運用に利用。ただし用途は明確に）
terraform workspace new dev
terraform workspace select dev

# Terraform Cloudの利用（認証とリモート実行の切替）
terraform login
# backend設定にcloud {} を用いてリモート実行/状態管理を有効化

Study Plan and Last-Mile Prep

If you want the shortest path to passing, anchor your prep on the official docs and tutorials, and reproduce the full workflow hands-on. HCL sticks far better when you write many small samples than when you read about it. Get firsthand experience with safe state migration and backend design through a mini-project (for example, migrating from local to S3+DynamoDB) — it dramatically lowers cognitive load on exam day.

Right before the exam, prepare a short reference sheet you can run through quickly: reading error and warning messages, interpreting plan diffs, variable precedence, and the Terraform Cloud workspace model and VCS integration flow. It steadies you on test day.

• Official tutorials: Get Started and Use Cases at developer.hashicorp.com/terraform
• Language reference: HCL blocks/expressions, count/for_each, dynamic blocks, and conditionals
• Operations: S3+DynamoDB locking, state mv/import, refresh-only, and the caveats around -target (do not overuse it)
• Terraform Cloud: the full picture of workspaces, variables/variable sets, remote execution, and VCS triggers

Check Your Understanding

Frequently Asked Questions