Knowing what IaC is gets you halfway; the exam also expects you to explain why organizations adopt it. Each benefit follows directly from the fact that infrastructure is described in files that a tool applies.
Repeatability means you can run the same configuration again and get the same result. Need a new environment for a customer, a region or a test? Apply the same files with different input values. Consistency is the related promise that development, staging and production are built from the same definitions, so a bug that appears in production can be reproduced in staging because the two are genuinely alike rather than approximately alike.
Code review is possible because changes are text diffs. A teammate can read a pull request, see that a security group now allows traffic from anywhere, and ask why before anything reaches a live system. Terraform strengthens this with terraform plan, whose output can be attached to the review so reviewers see not just the code change but the exact infrastructure change it will cause.
Audit history comes from version control. Every commit records who changed the infrastructure definition, when, and with what message. When an auditor asks when encryption was enabled on a storage bucket, you can point to the commit. Combined with pipeline logs, you get a trail that manual console work rarely produces.
Automation means the apply step can run in a CI/CD (continuous integration and continuous delivery) pipeline or in HCP Terraform instead of on someone's laptop. Humans approve; machines execute. This removes waiting for a specific person, and it makes policy checks and tests part of the path to production.
Fewer configuration errors is the payoff of all of the above. Typos in a console cannot be reviewed or tested; typos in code can be caught by terraform validate, by reviewers, by policy checks and by trying the change in a lower environment first. Manual steps done at 2 a.m. during an outage are where mistakes happen, and IaC reduces how many manual steps exist.
IaC also helps with disaster recovery and cost control: you can recreate infrastructure from code, and you can destroy temporary environments completely when you are done because the tool knows everything it created.
Key terms
- Repeatability
- The ability to produce the same infrastructure again from the same code and inputs.
- Consistency
- Environments built from the same definitions match each other, reducing works-in-staging-but-not-production surprises.
- Audit trail
- The record, from version control and pipeline logs, of who changed infrastructure, when and why.
- CI/CD
- Continuous integration and continuous delivery; automated pipelines that test and deploy changes.
A security reviewer spots in a pull request that a new database would be publicly accessible. Because the change is code, she comments on the line, the author fixes it, and the corrected plan is approved. In a console-driven team the same mistake might only be found by a later scan, or by an attacker.
Check yourself
Which IaC advantage lets a teammate catch an insecure change before it is applied?
Code review: changes are text diffs, often with plan output attached, that can be reviewed in a pull request before apply.
How does IaC help create a new test environment quickly?
Repeatability: you apply the same configuration with different input values instead of rebuilding by hand.