Terraform Associate
HashiCorp
Complete guide to passing the Terraform Associate exam on your first attempt.
$70.50
~70%
2 years
Global
HashiCorp
$100k-$150k
Are you ready for Terraform Associate?
Loading quiz...
Complete Overview
The HashiCorp Certified: Terraform Associate (004) is a one-hour, multiple-choice certification exam that validates foundational Infrastructure as Code skills with Terraform, and HashiCorp prices it at $70.50 USD plus locally applicable taxes and fees. It is written for cloud engineers, platform engineers, and system administrators who already write Terraform configuration, and HashiCorp lists only two prerequisites: basic terminal skills and an understanding of on-premises and cloud architecture. Version 004 replaced version 003 and tests against Terraform 1.12. HashiCorp publishes eight objective areas covering 37 numbered sub-objectives, running from explaining what Infrastructure as Code is through to organising HCP Terraform workspaces and projects. Four topics are new in 004: depends_on and create_before_destroy lifecycle rules, validating configuration with custom conditions, ephemeral values and write-only arguments, and HCP Terraform workspace and project organisation. The exam is delivered online with a live proctor through Certiverse, in English only, and the credential expires two years after issuance. Two numbers candidates ask about are not available. HashiCorp does not publish the question count for the Terraform Associate exam, and its knowledge base states plainly that it does not publish passing scores. The exam results report shows your performance on each objective area but not your percentage score or the threshold you needed to clear. Because HashiCorp publishes no domain weights either, you cannot allocate study hours by percentage the way you would for an AWS or Microsoft blueprint. What you can do is count sub-objectives: the Terraform configuration area lists eight, the core workflow area lists seven, and four areas list four each, which is a defensible proxy for coverage. Question types are true or false, single-answer multiple choice, and multiple answer. HashiCorp states on its sample questions page that the exam questions are not intended to trick you and that the exam tests Terraform knowledge rather than spelling or obscure detail. Its exam content list page adds that provider-specific knowledge is not necessary for the exam, so AWS, Azure, and Google Cloud service trivia are outside scope even though the listed tutorials use those providers to demonstrate concepts. The exam is closed book: no Terraform documentation, no CLI, no notes, no second monitor. Pass or fail status appears inside Certiverse immediately after you submit, and the objective-level report lands in the HashiCorp Certification Exam Portal 48 hours later. Retake rules are strict and worth reading before you book. Associate appointments do not include a free retake, you must wait seven days between attempts, and you may sit an exam at most four times in a rolling 365-day period. Passing locks you out of retaking that exam until the credential expires. Recertification eligibility begins 18 months after issuance, and passing the same exam again before expiry extends the credential by two years from the new pass date. The alternative route is passing the Terraform Authoring and Operations Professional exam, which both extends the Associate credential and earns a separate professional badge.
Why Get Terraform Associate Certified?
The exam fee is $70.50 USD plus locally applicable taxes, one of the cheapest vendor certifications in the infrastructure tooling market.
The whole appointment takes one hour, so the time cost of a first attempt is a single morning rather than a full test-centre day.
Version 004 tests Terraform 1.12, which means the blueprint covers current language features including ephemeral values, write-only arguments, and custom validation conditions.
HashiCorp publishes the complete list of 37 sub-objectives with a direct mapping from each one to a documentation page or tutorial, so there is no guesswork about what is in scope.
The credential lasts two years and recertification eligibility opens at 18 months, giving a six-month window to renew without a gap.
Objective area 8 covers HCP Terraform, so the exam doubles as structured preparation for the collaboration and governance features many teams adopt after outgrowing local state.
Passing the Terraform Authoring and Operations Professional exam extends the Associate credential by two years, so the Associate is a costed step on a two-exam ladder rather than a dead end.
Exam Format & Structure
Duration
60 minutes
Questions
HashiCorp does not publish the question count for the Terraform Associate 004 exam
Passing Score
Not published. The HashiCorp Certifications knowledge base states that HashiCorp does not publish passing scores, and the results report withholds both your percentage and the scoring threshold.
Question Types
- True or false
- Multiple choice with one correct answer
- Multiple answer, where the question states how many responses to select
Delivery Method
Online proctored through Certiverse, taken on your own machine with a live proctor who verifies identity, explains the rules, and monitors the session
- Product Version Tested: Terraform 1.12
- Open Book: Closed book. No Terraform documentation, CLI, notes, or reference material are permitted.
- Exam Version: 004, which replaced version 003
How scoring works
Score scale
Not published. HashiCorp does not disclose a score scale for the Terraform Associate exam.
Score needed to pass
Not published. The HashiCorp Certifications knowledge base states that the company does not publish its passing scores.
When results arrive
Pass or fail appears inside Certiverse immediately on submitting the exam. The objective-level results report becomes downloadable in the HashiCorp Certification Exam Portal 48 hours after the appointment, with an email notification when it is ready. Digital badges and certificates are issued through Credly.
How the scale is built
HashiCorp releases no information about how the Terraform Associate is scored. What is documented is what candidates see: an immediate pass or fail decision in Certiverse, followed 48 hours later by a report showing performance on each objective area with no percentage attached. HashiCorp states directly that it does not share your score percentage or its scoring threshold. No penalty for wrong answers is published, so an unanswered item cannot beat a guess.
Pacing and time budget
not published by HashiCorp questions in 60 minutes gives you Cannot be calculated, because HashiCorp does not publish an item count. Pace by fraction of the item set completed against minutes elapsed rather than by seconds per question. per question.
15
About one quarter of the item set, with no item yet costing more than 90 seconds
30
About half the item set, and every long HCL snippet question either answered or flagged
45
About three quarters of the item set, leaving 15 minutes for flagged items
52
Every item answered at least provisionally, so nothing is left blank if you run out of time
58
All flagged items revisited once. Stop changing answers and submit.
| At this point | You should have answered |
|---|---|
| 15 | About one quarter of the item set, with no item yet costing more than 90 seconds |
| 30 | About half the item set, and every long HCL snippet question either answered or flagged |
| 45 | About three quarters of the item set, leaving 15 minutes for flagged items |
| 52 | Every item answered at least provisionally, so nothing is left blank if you run out of time |
| 58 | All flagged items revisited once. Stop changing answers and submit. |
- True or false items should take under 20 seconds. If one takes longer, the ambiguity is usually in your reading rather than in the statement, so pick the reading HashiCorp's documentation would support and move on.
- Multiple-answer items always state how many responses to select. Count your selections before advancing, because a partially correct selection earns nothing.
- Questions that display an HCL snippet cost the most time. Read the block type and the argument being asked about first, then read the snippet, rather than parsing the whole configuration line by line.
- HashiCorp states on its sample questions page that the exam is not intended to trick you and does not test obscure details. If an answer looks like the plain documented behaviour, it usually is, and re-reading a fourth time rarely changes a correct first instinct.
- One hour is short enough that you will not have time for a full second pass over every item. Budget the last eight minutes for flagged items only.
Where the marks are
Terraform configuration: resources, data, variables, expressions, conditions, sensitive data
not published (8 of the 37 published sub-objectives)
The largest objective area. Expect map and list indexing syntax, implicit versus explicit dependencies, variable validation blocks, and the fact that sensitive values still land in state as plain text.
Core Terraform workflow: init, validate, plan, apply, destroy, fmt
not published (7 of the 37 published sub-objectives)
Questions ask which command refreshes state automatically, what a saved plan file changes about apply behaviour, and what terraform validate catches that terraform plan does not.
Terraform fundamentals: providers, versioning, and the purpose of state
not published (4 of the 37 published sub-objectives)
Expect required_providers syntax, version constraint operators including the tilde-greater form, provider aliases for multiple instances, and why Terraform keeps state at all.
Terraform state management: backends, locking, drift
not published (4 of the 37 published sub-objectives)
Questions cover which backends support locking, what terraform init -migrate-state does, and how refresh-only mode reports drift separately from configuration changes.
Terraform modules: sourcing, variable scope, versioning
not published (4 of the 37 published sub-objectives)
Expect the source and version arguments in a module block, the rule that child modules do not inherit parent variables, and the difference between registry, Git, and local path sources.
HCP Terraform: workspaces, projects, governance
not published (4 of the 37 published sub-objectives)
Expanded in the 004 revision. Questions distinguish Enterprise and paid-tier features from Community edition, and cover run triggers, variable sets, and how projects group workspaces.
Infrastructure as Code concepts and multi-cloud workflows
not published (3 of the 37 published sub-objectives)
Conceptual and quick to answer. Covers the advantages of declarative desired state, versioned infrastructure, and why a service-agnostic tool differs from a single-vendor one.
Maintaining infrastructure: import, state inspection, verbose logging
not published (3 of the 37 published sub-objectives)
Expect terraform import and import blocks, which state subcommands touch only the state file, and the TF_LOG environment variable and its levels.
| Topic | Weight | Why it scores |
|---|---|---|
| Terraform configuration: resources, data, variables, expressions, conditions, sensitive data | not published (8 of the 37 published sub-objectives) | The largest objective area. Expect map and list indexing syntax, implicit versus explicit dependencies, variable validation blocks, and the fact that sensitive values still land in state as plain text. |
| Core Terraform workflow: init, validate, plan, apply, destroy, fmt | not published (7 of the 37 published sub-objectives) | Questions ask which command refreshes state automatically, what a saved plan file changes about apply behaviour, and what terraform validate catches that terraform plan does not. |
| Terraform fundamentals: providers, versioning, and the purpose of state | not published (4 of the 37 published sub-objectives) | Expect required_providers syntax, version constraint operators including the tilde-greater form, provider aliases for multiple instances, and why Terraform keeps state at all. |
| Terraform state management: backends, locking, drift | not published (4 of the 37 published sub-objectives) | Questions cover which backends support locking, what terraform init -migrate-state does, and how refresh-only mode reports drift separately from configuration changes. |
| Terraform modules: sourcing, variable scope, versioning | not published (4 of the 37 published sub-objectives) | Expect the source and version arguments in a module block, the rule that child modules do not inherit parent variables, and the difference between registry, Git, and local path sources. |
| HCP Terraform: workspaces, projects, governance | not published (4 of the 37 published sub-objectives) | Expanded in the 004 revision. Questions distinguish Enterprise and paid-tier features from Community edition, and cover run triggers, variable sets, and how projects group workspaces. |
| Infrastructure as Code concepts and multi-cloud workflows | not published (3 of the 37 published sub-objectives) | Conceptual and quick to answer. Covers the advantages of declarative desired state, versioned infrastructure, and why a service-agnostic tool differs from a single-vendor one. |
| Maintaining infrastructure: import, state inspection, verbose logging | not published (3 of the 37 published sub-objectives) | Expect terraform import and import blocks, which state subcommands touch only the state file, and the TF_LOG environment variable and its levels. |
The numbers
$70.50 USD plus locally applicable taxes and fees, free retake not included
Exam fee
Source: HashiCorp Developer, Infrastructure Automation Certifications page
1 hour
Exam duration
Source: HashiCorp Developer, Infrastructure Automation Certifications page
Terraform 1.12 for exam version 004
Product version tested
Source: HashiCorp Developer, Infrastructure Automation Certifications page
8 objective areas containing 37 numbered sub-objectives
Published exam objectives
Source: HashiCorp Developer, Terraform Associate 004 exam content list
7 days between attempts, maximum 4 attempts in a rolling 365-day period
Retake restrictions
Source: HashiCorp Certifications knowledge base, What are the HashiCorp exam retake rules
2 years from issuance, with recertification eligibility opening at 18 months
Credential validity and recertification window
Source: HashiCorp Certifications knowledge base, Recertification policies and processes
If you fail
Wait before retaking
7 days between exam attempts
Attempt limit
4 attempts in a rolling 365-day period. After a fourth failed attempt you must wait until 365 days after your first attempt before trying again, and each subsequent attempt unlocks on the anniversary of the corresponding earlier attempt.
Retake fee
Full price again, $70.50 USD plus locally applicable taxes. HashiCorp states that Associate appointments do not include a free retake and that each purchase pays for a single appointment.
Missing an appointment counts the same as taking it: the fee is forfeited and you must buy a new appointment, though HashiCorp invites a support ticket if you missed it for a documented emergency. Once you have passed, you cannot retake the same exam until your credential expires, and recertification eligibility opens only 18 months after issuance. Holding more than one valid credential for the same exam is not permitted, and HashiCorp warns that using multiple accounts to work around the rules may result in a ban.
Exam Domains & Topics
Objective area 4, the largest area by sub-objective count with eight of the 37 published sub-objectives. Covers resource and data blocks, cross-resource references, variables and outputs, complex types, expressions and functions, dependency declaration, custom conditions, and sensitive data handling.
Key Topics to Master:
- Differentiating resource blocks from data blocks
- Resource addressing and references to named values
- Input variables, output values, and locals
- Complex types: list, set, map, object, tuple
- Built-in functions and dynamic expressions
- depends_on and the create_before_destroy lifecycle rule
- Custom conditions: variable validation, preconditions, postconditions
- Sensitive data, ephemeral values, write-only arguments, and the Vault provider
Objective area 3, seven sub-objectives. Covers the write, plan, apply loop end to end plus the supporting commands that sit around it.
Key Topics to Master:
- The write, plan, apply workflow
- terraform init and the dependency lock file
- terraform validate
- terraform plan and the resource graph
- terraform apply
- terraform destroy
- terraform fmt for formatting and style
Objective area 2, four sub-objectives. Covers how providers are installed, versioned, and used, and how Terraform uses state at a conceptual level.
Key Topics to Master:
- Installing and versioning providers
- How Terraform uses providers and the plugin architecture
- Writing configuration that uses multiple providers and provider aliases
- required_providers and the terraform settings block
- The purpose of Terraform state
Objective area 5, four sub-objectives. Covers where modules come from, how values move in and out of them, and how versions are pinned.
Key Topics to Master:
- Module sources: local paths, registry, Git, HTTP
- Variable scope inside modules and why parent variables are not inherited
- Calling registry modules in configuration
- The version argument in a module block
- Passing values out with module outputs
Objective area 6, four sub-objectives. Covers backends, locking, and drift, which is where a large share of real operational trouble lives.
Key Topics to Master:
- The local backend and terraform.tfstate
- State locking and which backends support it
- Configuring remote state with the backend block
- terraform init -migrate-state and -reconfigure
- Resource drift and refresh-only mode
Objective area 8, four sub-objectives, expanded in the 004 revision. Covers the hosted product formerly named Terraform Cloud.
Key Topics to Master:
- Creating infrastructure through HCP Terraform
- Collaboration and governance features including policy as code
- Organising workspaces and projects
- Run triggers and variable sets
- VCS-driven, CLI-driven, and API-driven run workflows
Objective area 1, three sub-objectives. Conceptual questions about what Infrastructure as Code is and why teams adopt it.
Key Topics to Master:
- Defining Infrastructure as Code
- Advantages of IaC patterns: repeatability, versioning, review, reduced drift
- Multi-cloud, hybrid cloud, and service-agnostic workflows
- Why a declarative desired state differs from imperative scripting
Objective area 7, three sub-objectives. Covers bringing existing resources under management, inspecting state, and debugging.
Key Topics to Master:
- terraform import and import blocks
- terraform state list, show, mv, rm
- TF_LOG levels and TF_LOG_PATH for verbose logging
- When verbose logging helps and when it just produces noise
Recommended Study Plan
- 1Install Terraform 1.12 or later so your local behaviour matches the version the 004 exam tests
- 2Create a free HCP Terraform account at app.terraform.io, since objective area 8 is examinable
- 3Read the Introduction to Infrastructure as Code tutorial on HashiCorp Developer, which maps to sub-objectives 1b and 1c
- 4Bookmark the Terraform Associate 004 exam content list page and copy the 37 sub-objectives into a checklist you tick off
- 5Create your HashiCorp Certification Exam Portal account through GitHub now, and check the names on it match your photo ID exactly
- 1Work through the Initialize Terraform Configuration tutorial and inspect the .terraform directory it creates
- 2Read the Provider Requirements and Provider Configuration pages in the Terraform language documentation
- 3Write a configuration that declares two provider instances with aliases and target a resource at one of them
- 4Experiment with version constraint operators in required_providers: exact, >=, ~>, and ranges
- 5Delete .terraform.lock.hcl, run terraform init again, and compare the regenerated file
- 1Run the full init, validate, plan, apply, destroy cycle at least five times on throwaway resources
- 2Save a plan to a file with terraform plan -out and apply that saved plan, then explain why the saved plan is not re-refreshed
- 3Read the Command: plan, Command: apply, and Command: destroy documentation pages and note the flags each accepts
- 4Deliberately break formatting in a file and fix it with terraform fmt, then run terraform fmt -check to see the exit code
- 5Introduce a syntax error and a type error, and note which one terraform validate catches and which one only surfaces at plan
- 1Complete the Customize Terraform Configuration with Variables tutorial
- 2Build a configuration using a list, a set, a map, and an object variable, and read each one with the right index or key syntax
- 3Practise the map lookup form var.name["key"], which appears in HashiCorp's own published sample question
- 4Read the Query Data Sources tutorial and write a configuration where a data block feeds a resource argument
- 5Write resource dependencies both implicitly through references and explicitly with depends_on, then compare the plan output
- 1Add a validation block to an input variable and trigger the failure message
- 2Add a precondition and a postcondition to a resource lifecycle block and make each one fail
- 3Read the Manage Sensitive Data documentation and confirm for yourself that a sensitive variable still appears in plain text inside terraform.tfstate
- 4Read the ephemeral values and write-only arguments documentation, which is new in the 004 blueprint
- 5Apply create_before_destroy to a resource that forces replacement and watch the ordering change in the plan
- 1Complete the Build and Use a Local Module tutorial
- 2Consume a module from registry.terraform.io using the source and version arguments
- 3Prove to yourself that a variable declared in the root module is not visible inside a child module unless passed explicitly
- 4Refactor a flat configuration of at least six resources into two modules with clear inputs and outputs
- 5Pin a module to an exact version, then to a ~> constraint, and observe what terraform init downloads each time
- 1Configure a remote backend, then migrate an existing local state to it with terraform init -migrate-state
- 2Read the State Storage and Locking documentation and note which backends support locking
- 3Change a managed resource outside Terraform, then run terraform plan -refresh-only to see the drift reported separately from configuration changes
- 4Practise terraform state list, terraform state show, terraform state mv, and terraform state rm on a throwaway workspace
- 5Confirm that state subcommands change only the state file and never call the provider to modify infrastructure
- 1Create a resource outside Terraform and bring it under management with an import block, then run terraform plan -generate-config-out
- 2Compare the import block workflow against the older terraform import command
- 3Set TF_LOG=TRACE and TF_LOG_PATH, run a plan, and read the provider request and response lines in the log
- 4Work through the five TF_LOG levels and note which one you would actually use to chase a provider error
- 5Use terraform apply -replace on a healthy resource to force recreation, which is the supported replacement for the old taint workflow
- 1Complete the HCP Terraform Get Started collection on HashiCorp Developer
- 2Create two workspaces inside one project and move a workspace between projects
- 3Configure a variable set at organisation level and confirm it applies to more than one workspace
- 4Set up a run trigger so a successful apply in one workspace queues a run in another
- 5Read the policy as code and governance documentation so you can distinguish Community edition features from paid tiers
- 1Walk the exam content list and mark each of the 37 sub-objectives as confident, shaky, or untouched
- 2Rewrite from memory the exact syntax for a provider block, a module block, a backend block, and a variable validation block
- 3Attempt HashiCorp's published sample questions on the associate-questions-004 page and read the explanations for the ones you miss
- 4List every CLI subcommand you have run this course and write one sentence on what each does
- 5Re-read the Purpose of Terraform State documentation, the single topic that touches the most objective areas
- 1Spend the whole week only on sub-objectives you marked shaky in week 10
- 2Run the Certiverse network test and system check on the exact machine and network you will use on exam day
- 3Confirm you can sign in to the correct GitHub account on that machine, since the Exam Portal is tied to it
- 4Book the appointment, noting that cancellation or rescheduling must happen at least 24 hours ahead
- 5If you need an accommodation, submit the request at least three full business days before the appointment
- 1Do one timed 60-minute run through a third-party question bank purely to rehearse pace, not to learn new facts
- 2Re-read the four topics new to 004: depends_on and create_before_destroy, custom conditions, ephemeral and write-only values, and HCP Terraform projects
- 3Clear your desk and test the room the day before, since the proctor scans the environment before unlocking the exam
- 4Photograph your unexpired physical government photo ID and check the name matches your portal account character for character
- 5Stop learning new material 24 hours out and review only your own written command notes
Ready to pass Terraform Associate?
Get 500+ practice questions, video walkthroughs, and a pass guarantee.
Best Study Resources
Terraform Associate 004 exam content list
Official blueprintMaps every one of the 37 published sub-objectives to a specific documentation page or tutorial. This is the single most useful page for exam preparation because it removes any argument about scope.
Free
Terraform Associate 004 learning path
Official tutorialsHashiCorp's start-to-finish ordered tutorial sequence for the 004 exam, arranged by level rather than by objective number.
Free
Terraform Associate 004 sample questions
Official practiceHashiCorp's own worked examples of the three question types, including a map indexing question and two multiple-answer questions with explained answers.
Free
Terraform language documentation
DocumentationThe reference for blocks, expressions, functions, complex types, meta-arguments, and the lifecycle rules that objective area 4 tests.
Free
Terraform CLI documentation
DocumentationPer-command reference pages for init, validate, plan, apply, destroy, fmt, import, state, and workspace, including the flags each accepts.
Free
HCP Terraform free tier
Hands-on platformA free account at app.terraform.io lets you practise workspaces, projects, variable sets, run triggers, and remote state, which objective area 8 covers.
Free tier available
Terraform Registry
ReferenceWhere module sources, provider documentation, and version constraints are looked up in practice. Objective 5a and 5d ask about sourcing and versioning modules from here.
Free
Terraform: Up and Running by Yevgeniy Brikman
BookThe most widely used practical Terraform book. It goes beyond the exam blueprint into production patterns, which helps most with the modules and state areas.
Paid, published by O'Reilly
HashiCorp Certifications knowledge base
Policy referenceThe authority for retake rules, exam appointment rules, identification requirements, results timing, and recertification. Read the exam appointment rules article before booking.
Free
Certiverse system requirements and network test
Technical checkHashiCorp delivers the exam through Certiverse and requires your machine to pass its system requirements and network test. HashiCorp notes that its exams do not use Certiverse's Safe Exam Browser.
Free
Common Mistakes to Avoid
Studying a 003-era blueprint that no longer matches the exam
Version 004 added four topics that 003 did not test: depends_on and create_before_destroy lifecycle rules, validating configuration with custom conditions, ephemeral values and write-only arguments, and organising HCP Terraform workspaces and projects. Any study guide that does not mention those four is out of date.
Trying to allocate study time by domain percentage
HashiCorp publishes no domain weights for the Terraform Associate. Use sub-objective counts instead as a rough proxy: configuration lists eight, core workflow lists seven, and fundamentals, modules, state, and HCP Terraform list four each.
Still practising terraform taint and untaint as the way to force recreation
The 004 objective list does not mention taint. The current supported route is terraform apply -replace=ADDRESS. Learn the -replace flag and treat taint as legacy trivia rather than exam content.
Calling the hosted product Terraform Cloud
Objective area 8 is titled HCP Terraform. The naming matters because exam wording follows current documentation, and the 004 revision expanded this area to include projects alongside workspaces.
Assuming sensitive variables are protected inside state
HashiCorp's own published sample question asserts that usernames and passwords referenced in Terraform code, even as variables, end up in plain text in the state file. The sensitive argument suppresses CLI output only. Protect state itself with a secure remote backend.
Ignoring the dependency lock file
Sub-objective 3b maps directly to the dependency lock file documentation. Know that .terraform.lock.hcl records provider selections, that it belongs in version control, and that terraform init -upgrade is what changes it.
Never configuring a remote backend because local state works fine on a laptop
Objective 6c asks you to configure remote state with the backend block, and 6b asks about locking. Migrate at least one real project with terraform init -migrate-state so you have seen the prompt and the flags.
Learning Terraform only through one cloud provider's resources and revising that provider's services
HashiCorp states on the exam content list page that provider-specific knowledge is not necessary for the exam, even though its tutorials use specific providers. Time spent memorising AWS instance families or Azure SKU names earns nothing here.
Skipping the count of required answers on multiple-answer questions
HashiCorp's sample questions show the instruction Pick the 2 correct responses below. Selecting one correct answer out of two required answers earns nothing, and the exam gives you the number every time.
Creating the certification portal account with a GitHub login you cannot reach on exam day
The HashiCorp Certification Exam Portal is tied to a GitHub account. Signing in with a different GitHub account creates a duplicate portal account that can break access to your appointment, your results, and your Credly badge. Use a personal account you keep after changing employer.
Exam Day Tips
- 1
Bring one unexpired physical government-issued photo ID. HashiCorp explicitly does not accept digital IDs, and an expired card ends the appointment.
- 2
Check that every name on your ID appears in your Exam Portal account, in the same language and characters. Name changes must be requested at least three business days before the appointment.
- 3
Sign in to the correct GitHub account on your exam machine the day before, because the Exam Portal authenticates through GitHub and a second account creates a duplicate profile.
- 4
Run the Certiverse network test and system check on the exact machine and network you will use. HashiCorp recommends Google Chrome as the least likely browser to cause screen-share problems.
- 5
Use one monitor only. If you use an external monitor, your laptop lid must be closed and the external display needs its own webcam that stays on for the whole session.
- 6
Clear your desk and work area completely. The proctor scans the room by webcam looking for places a recording device could sit, so less clutter means a faster check-in.
- 7
Remove phones, smartwatches, and headphones from the room, and make sure any other electronics in the room are switched off. Nobody else may be present for the duration.
- 8
Keep drinks in a clear container with no writing on it, stay in your seat for the full hour, and keep your head and shoulders in frame. Reading or mouthing questions counts as prohibited communication.
- 9
Treat this as a closed-book hour: no Terraform CLI, no registry, no documentation tab. Memorise block syntax and command flags in advance.
- 10
Reschedule or cancel at least 24 hours ahead if plans change. Missing the appointment forfeits the fee and forces a new $70.50 purchase.
- 11
Expect pass or fail immediately inside Certiverse when you submit, and expect the objective-by-objective report in the Exam Portal roughly 48 hours later.
Career Paths & Salary Ranges
Cloud systems administrator
Runs day-to-day cloud and on-premises systems, increasingly through Terraform rather than consoles. The US Bureau of Labor Statistics reported a median annual wage of $96,800 for network and computer systems administrators in May 2024, with industry medians ranging from $83,620 in education to $101,600 in management of companies and enterprises.
$83,620 to $101,600 depending on industry
DevOps engineer
Builds delivery pipelines and provisions the infrastructure they deploy to. The role maps most closely to the BLS software developers category, where May 2024 industry medians ran from $129,890 in computer systems design services to $149,990 in software publishing.
$129,890 to $149,990 depending on industry
Cloud network architect
Designs the network and connectivity layer that Terraform modules then codify. BLS reported a May 2024 median of $130,390 for computer network architects, with industry medians from $105,810 in education to $137,770 in management of companies and enterprises. BLS projects 12 percent employment growth for this occupation from 2024 to 2034.
$105,810 to $137,770 depending on industry
Platform security engineer
Owns policy as code, secret handling, and state security, which is exactly what sub-objective 4h and the HCP Terraform governance topics cover. BLS reported a May 2024 median of $124,910 for information security analysts and projects 29 percent growth from 2024 to 2034, the fastest of the occupations listed here.
$120,050 to $136,390 depending on industry
Cloud migration analyst
Assesses existing estates and plans the move into managed infrastructure, often starting with terraform import on resources nobody codified. BLS reported a May 2024 median of $103,790 for computer systems analysts, with industry medians from $97,430 in government to $109,210 in management of companies and enterprises.
$97,430 to $109,210 depending on industry
Infrastructure engineering manager
Leads the team that sets module standards and workspace structure. BLS reported a May 2024 median of $171,200 for computer and information systems managers, with industry medians from $171,250 in computer systems design services to $196,060 in the information sector, and projects 15 percent growth from 2024 to 2034.
$171,250 to $196,060 depending on industry
Prerequisites & Requirements
- There are no formal prerequisites. HashiCorp does not require a prior certification, a degree, or documented work experience to sit the Terraform Associate exam.
- HashiCorp lists two recommended skills: basic terminal skills, and an understanding of on-premises and cloud architecture.
- Professional experience is recommended but not required. HashiCorp states you can prepare by practising the exam objectives in a personal demo setup.
- You need a HashiCorp Certification Exam Portal account, which is created through and permanently tied to a GitHub account.
- You need one unexpired physical government-issued photo ID whose names exactly match the names in your portal account. Digital IDs are not accepted.
- You need a machine that passes the Certiverse system requirements and network test, a single monitor, a working webcam, and a private room you can occupy alone for the appointment.
- Exam fee: $70.50 USD plus locally applicable taxes and fees. A free retake is not included with the Associate exam.
Frequently Asked Questions
How many questions are on the Terraform Associate exam?
HashiCorp does not publish the question count. Its certification pages state the assessment type as multiple choice and the duration as one hour, but no official page gives a number of items. Counts circulating on third-party blogs, including the figure of 57, are not confirmed by HashiCorp for the 004 version, so plan by pace rather than by item count.
What is the passing score?
HashiCorp does not publish it. The HashiCorp Certifications knowledge base article titled What is the passing score answers that the company does not publish passing scores at this time. The results report you receive afterwards deliberately omits both your percentage and the threshold, showing only performance per objective area.
How long do I have to wait before retaking the exam if I fail?
Seven days between attempts. HashiCorp also caps you at four attempts in a rolling 365-day period, and if you use all four, your fifth attempt is only allowed 365 days after your first attempt. Passing the exam blocks you from retaking it until your credential expires.
Is a retake free?
No. HashiCorp states that Associate exam appointments do not include a free retake and that your purchase pays for a single appointment, so a second attempt means paying $70.50 again plus local taxes. Only the professional-level exams, Terraform Authoring and Operations Professional and Vault Operations Professional, include one free retake voucher, and that voucher must be requested within three months of the failed attempt.
Does the exam fee change by region?
The base price is the same worldwide at $70.50 USD, but HashiCorp adds locally applicable taxes and fees on top, so the amount charged in a VAT or GST jurisdiction is higher than $70.50. The exam is delivered online everywhere, so there is no test-centre surcharge that varies by country.
What happens if I miss my appointment?
You forfeit the fee and must buy a new appointment. HashiCorp requires cancellation or rescheduling at least 24 hours in advance, and states that missing an appointment without documentation may result in loss of exam fees. The retake rules also apply to missed appointments. If you missed it because of a documented emergency, HashiCorp asks you to submit a support ticket.
When do I get my results?
Pass or fail status appears in Certiverse immediately when you finish the exam. The detailed results report, which breaks your performance down by objective area, becomes available in the HashiCorp Certification Exam Portal 48 hours after the appointment, and HashiCorp emails you when it is ready. Professional-level exams instead email results within 48 hours.
How does the scoring work?
HashiCorp keeps the mechanism private. It does not disclose a scale, a raw-to-scaled conversion, or the cut score, and the results report shows objective-level performance rather than a number. There is no published penalty for wrong answers, so leaving an item blank cannot score better than a guess.
What ID do I need on exam day?
One unexpired government-issued photo ID in physical card form. HashiCorp does not accept digital IDs. Every name on the ID must appear in your Exam Portal account, in the same language and characters, and if your ID shows all names on a single line you may split them across the first and last name fields in any order as long as none is missing.
What are the online proctoring rules?
You take the exam alone in a private, well-lit, quiet room with a clear desk, and you scan the environment on webcam before the exam unlocks. No other person may be present, no phones, smartwatches, or headphones are allowed in the room, other electronics must be non-operational, only one monitor may be used, and you may not leave your seat during the hour. Beverages are allowed only in clear containers with no writing on them.
Can I use documentation, a terminal, or a calculator during the exam?
No. The Terraform Associate is closed book, with no access to Terraform documentation, the Terraform CLI, the registry, notes, or any reference material. There is no arithmetic in the exam that would need a calculator, so you should expect to recall block syntax, command names, and flag behaviour from memory.
Are accommodations available?
Yes. HashiCorp asks you to submit an accommodation request at least three full business days before your appointment, and states it cannot guarantee accommodations requested with less notice. The knowledge base gives worked examples including candidates who cannot remove a head covering and candidates who need a female proctor, and invites requests for any documentable reason affecting the room or behaviour rules.
How long is the certification valid and how do I renew?
Two years from issuance. There is no continuing-education or CE credit path with HashiCorp: renewal means passing an exam. You become eligible to retake the same exam 18 months after earning the credential, and passing before expiry extends your expiration by two years from the new pass date. HashiCorp emails reminders at six months, three months, and one month before expiry.
What are my options if my certification has already expired?
Retake the current version of the Terraform Associate exam at any time, or take a newer exam version if one has been released. Either route issues a new set of credentials with a new expiration date, and your expired credentials remain unchanged rather than being revived. There is no penalty period after expiry.
I hold a 002 or 003 Terraform Associate credential. What happens when I pass 004?
You receive a new, separate set of credentials with a new expiration date, and your original credentials keep their existing expiration date rather than being extended. That differs from holders of an unexpired 004 credential, for whom passing 004 again within six months of expiry extends the same credential. The three-digit version code on your badge and certificate tells you which case applies to you.
Which Terraform version does the 004 exam test?
Terraform 1.12. HashiCorp lists the product version tested on the certification page, and the 004 revision moved it forward while adding four topics: depends_on and create_before_destroy lifecycle rules, custom validation conditions, ephemeral values and write-only arguments, and HCP Terraform workspace and project organisation.
Do I need to know AWS, Azure, or Google Cloud?
No. The exam content list page states directly that although the linked tutorials use specific cloud providers to introduce the learning objectives, provider-specific knowledge is not necessary for the exam. You do need a provider to practise against, so a free tier account helps, but memorising service names or SKUs earns nothing.
How does the Terraform Associate compare with the Terraform Authoring and Operations Professional exam?
The Professional exam is four hours including a 15-minute break, is lab-based as well as multiple choice, costs $295 USD, includes a free retake, and tests Terraform 1.6. It expects advanced production experience with module authoring, dynamic HCL, and collaborative workflows, and HashiCorp strongly recommends holding the Associate first. Passing the Professional also extends an unexpired Associate credential by two years.
Is the Terraform Associate worth taking alongside a cloud provider certification?
They test different things and do not overlap much. A cloud provider associate certification covers that vendor's service catalogue, quotas, and pricing model. The Terraform Associate covers a workflow and a configuration language that work across providers, and HashiCorp explicitly keeps provider-specific knowledge out of scope. Candidates commonly hold one of each.
Can I take the exam at a test centre instead of online?
No. HashiCorp states that all certification exams are taken online with a live proctor. There is no test-centre option, which means your machine, your network, and your room all have to meet the requirements, and a failed network test on the day is your problem rather than the venue's.
Success Stories
“The HashiCorp Learn tutorials are gold. Combined with the practice exam, I passed on the first try. Focus on state management and modules - lots of questions there.”
Alex K.
DevOps Engineer
“Coming from CloudFormation, Terraform concepts clicked quickly. The exam tested practical knowledge well. Make sure you practice the CLI commands hands-on.”
Priya M.
Cloud Engineer
“I used Terraform daily but still learned from studying for the cert. The exam covers features you might not use regularly. The official practice exam was very representative.”
Marcus T.
SRE
Pass Terraform Associate, Guaranteed
94% pass rate on first attempt
One-time • Lifetime access