Terraform Associate · Domain 1 of 8

Terraform Associate Domain 1: Infrastructure as Code (IaC) with Terraform

This domain covers the conceptual foundation of Terraform: what infrastructure as code is, the advantages of IaC patterns such as declarative configuration and version control, and how Terraform provides a consistent multi-cloud, hybrid-cloud and service-agnostic workflow.

Exam weight estimate
Not published
Official objectives
3
Estimated questions estimate
~5
Suggested study time estimate
5–10 hrs

About 10 min read Reviewed October 2026

Overview

Infrastructure as Code with Terraform is the conceptual starting point of the Terraform Associate exam. It has three objectives. Explaining what IaC is covers defining infrastructure as code: managing and provisioning infrastructure through machine-readable configuration files rather than manual processes. Describing the advantages of IaC patterns covers the benefits, repeatability, consistency, version control, automation, reduced human error and self-documenting infrastructure. Explaining Terraform's workflows covers how Terraform works across multiple cloud providers, hybrid environments and many services through a single, consistent, provider-agnostic workflow.

Though weights are not published, this domain is foundational and sets up everything else. The exam rewards understanding why IaC matters and what makes Terraform distinctive: a declarative, cloud-agnostic tool that manages infrastructure consistently across providers. These concepts underpin the fundamentals, workflow, configuration, modules and state topics that follow.

How it's tested

Terraform Associate questions are concept and workflow based, testing understanding rather than provider-specific trivia. In this domain they describe an infrastructure-management situation and ask which IaC concept, advantage or Terraform characteristic applies, favoring the declarative, cloud-agnostic model. Read the scenario for the principle it illustrates.

  • Identify the IaC concept

    A situation is described, and you identify infrastructure as code or the declarative approach it illustrates.

  • Name the advantage

    A benefit is described, and you choose the IaC advantage such as repeatability or version control.

  • Terraform's workflow

    A multi-provider or consistency need is described, and you identify Terraform's cloud-agnostic workflow.

Reasoning it through

A team manages servers by clicking through a cloud console, and environments drift apart over time. Continuing manual setup repeats the problem. Defining the infrastructure in Terraform configuration files, applied consistently, makes every environment reproducible from the same code and eliminates drift from manual changes, which is the infrastructure-as-code advantage the exam expects over manual provisioning.

Objectives 3

Official objectives from the HashiCorp outline, in outline order.

1a Explain what IaC isManaging infrastructure through machine-readable configuration files.
What it means
This covers defining infrastructure as code: provisioning and managing infrastructure through declarative, machine-readable configuration files that are version-controlled, rather than through manual console clicks or ad hoc scripts.
What to understand
Infrastructure as code expresses the desired state of infrastructure in files that a tool applies. Terraform is declarative, meaning you describe what you want and Terraform determines how to achieve it, rather than imperative step-by-step instructions. The code is the source of truth and can be versioned, reviewed and reused.
How it shows up
A provisioning situation is described, and you must identify it as infrastructure as code or the declarative model.
Common confusion
Confusing declarative with imperative; declarative describes the desired end state, while imperative specifies each step to reach it.
1b Describe the advantages of IaC patternsRepeatability, consistency, version control and reduced error.
What it means
This covers the benefits of IaC patterns: repeatable and consistent provisioning, version control and change history, automation, reduced human error, easier collaboration, and infrastructure that is self-documenting through its code.
What to understand
IaC makes infrastructure reproducible, so the same code yields the same environment, and version control tracks every change for review and rollback. Automation removes manual, error-prone steps, and the code documents the infrastructure. These advantages are why organizations adopt IaC.
How it shows up
A benefit or pain point is described, and you must name the IaC advantage that addresses it.
Common confusion
Treating IaC as only automation; it also provides version control, consistency, reviewability and self-documentation.
1c Explain how Terraform manages multi-cloud, hybrid cloud, and service-agnostic workflowsA single consistent workflow across providers and services.
What it means
This covers how Terraform works across multiple cloud providers, hybrid cloud and on-premises environments, and many services, using one consistent workflow and configuration language regardless of the underlying provider.
What to understand
Terraform uses providers to interact with different platforms, so the same workflow, write, plan, apply, manages AWS, Azure, Google Cloud, on-premises systems and SaaS services. This provider-agnostic approach avoids being locked into one cloud's tooling and lets a single configuration span multiple providers.
How it shows up
A multi-provider or consistency requirement is described, and you must identify Terraform's cloud-agnostic workflow.
Common confusion
Thinking Terraform is tied to one cloud; it is provider-agnostic and manages many platforms through providers.

High-yield concepts

The terms, rules and formulas this domain turns into questions most often.

  • Infrastructure as code

    Managing infrastructure through configuration files.

    Remember
    The code is the source of truth.
    Tested as
    Foundational concept questions.
    Trap
    Confusing it with manual scripting.

  • Declarative vs. imperative

    Describing the desired state versus each step.

    Remember
    Terraform is declarative.
    Tested as
    Concept questions.
    Trap
    Confusing the two approaches.

  • Desired state

    The end state the configuration describes.

    Remember
    Terraform reconciles reality to it.
    Tested as
    Concept questions.
    Trap
    Thinking in steps rather than end state.

  • Repeatability

    Same code yields the same environment.

    Remember
    Eliminates environment drift from manual work.
    Tested as
    Advantage questions.
    Trap
    Overlooking it as a key benefit.

  • Version control for infrastructure

    Tracking infrastructure changes in source control.

    Remember
    Enables review, history and rollback.
    Tested as
    Advantage questions.
    Trap
    Not versioning infrastructure code.

  • Reduced human error

    Automation removes manual, error-prone steps.

    Remember
    Consistency comes from automation.
    Tested as
    Advantage questions.
    Trap
    Relying on manual provisioning.

  • Self-documenting infrastructure

    The code describes the infrastructure.

    Remember
    Configuration is the documentation.
    Tested as
    Advantage questions.
    Trap
    Keeping separate, stale documentation.

  • Provider-agnostic workflow

    One workflow across many platforms.

    Remember
    Write, plan, apply works everywhere.
    Tested as
    Workflow questions.
    Trap
    Thinking Terraform is one-cloud only.

  • Multi-cloud and hybrid

    Managing several clouds and on-premises together.

    Remember
    A single configuration can span providers.
    Tested as
    Workflow questions.
    Trap
    Assuming separate tools per cloud.

  • Providers

    Plugins that let Terraform manage a platform.

    Remember
    They enable the cloud-agnostic workflow.
    Tested as
    Workflow questions.
    Trap
    Overlooking the role of providers.

Side by side

Concepts candidates mix up, compared on the point that decides the answer.

Declarative vs. imperative

ConceptMeaningKey differenceCommon trap
Declarative Describe the desired end state Tool decides the steps Confusing with imperative
Imperative Specify each step to execute You control the steps Confusing with declarative

IaC vs. manual provisioning

ConceptMeaningKey differenceCommon trap
Infrastructure as code Configuration files applied by a tool Repeatable, versioned, consistent Treating it as just scripting
Manual provisioning Console clicks or ad hoc commands Error-prone, drifts, undocumented Assuming it scales

Single-cloud tool vs. Terraform

ConceptMeaningKey differenceCommon trap
Single-cloud tool Tied to one provider One platform only Assuming Terraform is like this
Terraform Provider-agnostic workflow Many platforms, one workflow Thinking it is one-cloud

Exam traps

Each trap is an answer that looks right. Learn the clue that should change your mind.

  1. Imperative is declarative

    What candidates pick
    Describe Terraform as specifying each step to build infrastructure.
    Why it looks right
    Scripting is familiar.
    Why it's wrong
    Terraform is declarative: you describe the desired state and it determines the steps.

    Clue to watch for The question contrasts describing the end state with scripting steps.

  2. IaC is just automation

    What candidates pick
    Say the only benefit of IaC is automating provisioning.
    Why it looks right
    Automation is the obvious benefit.
    Why it's wrong
    IaC also provides version control, repeatability, consistency, reviewability and self-documentation.

    Clue to watch for The question asks for advantages beyond speed.

  3. Terraform is one-cloud

    What candidates pick
    Assume Terraform only manages a single cloud provider.
    Why it looks right
    Many tools are provider-specific.
    Why it's wrong
    Terraform is provider-agnostic and manages multiple clouds, hybrid and services through providers with one workflow.

    Clue to watch for The scenario spans multiple providers or on-premises.

  4. Manual is fine at scale

    What candidates pick
    Continue manual console provisioning for consistency across environments.
    Why it looks right
    It works for a single environment.
    Why it's wrong
    Manual provisioning drifts and is error-prone; IaC makes environments repeatable and consistent.

    Clue to watch for Environments drift or must be reproduced reliably.

  5. Docs separate from code

    What candidates pick
    Maintain separate documents to describe the infrastructure.
    Why it looks right
    Documentation seems like a separate task.
    Why it's wrong
    IaC is self-documenting: the configuration itself describes the infrastructure, avoiding stale separate docs.

    Clue to watch for The need is accurate, current infrastructure documentation.

Answer framework

For any Domain 1 concept scenario, use these steps to find the answer the exam expects.

  1. Determine whether the question is about what IaC is, an advantage of IaC, or Terraform's workflow.
  2. For the concept, recognize infrastructure as code as managing infrastructure through declarative configuration files, with the code as the source of truth.
  3. For advantages, name the specific benefit, repeatability, consistency, version control, automation, reduced error or self-documentation, that the scenario needs.
  4. For Terraform's workflow, recognize its provider-agnostic nature: one consistent write, plan, apply workflow across clouds, hybrid and services.
  5. Prefer the declarative, cloud-agnostic, version-controlled answer over manual, imperative or single-cloud alternatives. Where two options seem to fit, choose the one that most precisely matches the Terraform behavior the scenario describes.

Practice question

A team currently provisions its cloud infrastructure by manually clicking through a web console, and finds that their development, staging and production environments have drifted apart over time. How does adopting infrastructure as code with Terraform BEST address this?

Want more like this? The Terraform Associate practice test has questions for every domain.

Checklist

0 of 10

Tick each one you can do without notes. Your ticks stay in this browser.

Study strategy

Treat this domain as learning the vocabulary and value proposition that the whole exam assumes. Start with the core concept: infrastructure as code means managing infrastructure through declarative configuration files, with the code as the source of truth, and fix firmly the declarative-versus-imperative distinction since Terraform is declarative.

Next, learn the advantages of IaC thoroughly, repeatability, consistency, version control, automation, reduced error and self-documentation, because the exam asks you to match a benefit to a situation. Then understand what makes Terraform distinctive: its provider-agnostic workflow that manages many clouds, hybrid environments and services through providers with one consistent write, plan, apply cycle.

Although this is conceptual, grounding it in a little hands-on practice, writing a tiny configuration and running it, makes the ideas concrete. Afterwards, move to Domain 2, Terraform fundamentals, which introduces providers and state. Because the exam rewards practical familiarity, write small configurations and run the workflow in a demo environment rather than only reading, and review missed practice questions by objective to find weak spots.

FAQ

Does HashiCorp publish weights for the Terraform Associate domains?

No. HashiCorp lists the exam objectives but does not publish a percentage weight per objective group. These pages therefore show each weight as Not published; the question estimates are planning figures only.

What is infrastructure as code?

Managing and provisioning infrastructure through machine-readable, version-controlled configuration files rather than manual console actions, so the code becomes the source of truth for the infrastructure.

What is the difference between declarative and imperative?

Declarative means you describe the desired end state and the tool works out the steps, which is how Terraform operates. Imperative means you specify each step to execute yourself.

What are the main advantages of IaC?

Repeatability and consistency, version control with history and rollback, automation that reduces human error, easier collaboration, and self-documenting infrastructure through the configuration itself.

Is Terraform tied to a single cloud?

No. Terraform is provider-agnostic. Through providers it manages AWS, Azure, Google Cloud, on-premises systems and many services using one consistent workflow, which is a key reason to use it.

Which Terraform version does the current exam test?

The current Terraform Associate exam is the 004 version, which tests against Terraform 1.12. It replaced the 003 version on 8 January 2026.

How does Domain 1 connect to the rest of the exam?

These IaC and workflow concepts underpin the fundamentals, core workflow, configuration, modules, state and HCP Terraform topics in the later domains.

Other Cloud Computing certifications

Where the same subject shows up in other exams. Cards marked "Same subject" open the matching domain.

Test your Domain 1 knowledge

You have covered what infrastructure as code is, its advantages, and Terraform's provider-agnostic workflow. Test whether you can identify the right IaC concept under exam conditions.

Take the Terraform Associate practice test Check your Terraform Associate readiness

Keep going