Infrastructure as Code Concepts and Terraform's Purpose
This chapter establishes what Infrastructure as Code means, why organizations adopt it, and where Terraform fits among provisioning and configuration management tools. These foundational ideas frame every practical task in the exam.
What Infrastructure as Code means
Infrastructure as Code defines infrastructure in machine-readable configuration files rather than through manual console clicks. Because the configuration is code, it can be stored in version control, peer-reviewed, reused, and applied repeatably. This brings software-engineering practices such as change review and history to infrastructure management.
Declarative provisioning
Terraform is declarative: you describe the desired end state, and Terraform figures out the create, update, or destroy actions needed to reach it by comparing your configuration to recorded state. This makes runs idempotent, so applying the same configuration repeatedly converges on the same result rather than repeating actions blindly.
Terraform's place among tools
Terraform is primarily a provisioning tool that manages infrastructure resources across many providers through one workflow and one language (HCL). Configuration management tools such as Ansible, Chef, and Puppet focus on configuring software on existing systems, so they often complement Terraform rather than replace it. Terraform unifies the workflow across clouds without erasing each cloud's own semantics.