1.2. Why IaC Changes How Teams Operate
💡 First Principle: Once infrastructure is text under version control, it inherits every collaboration tool software teams already trust — pull requests, code review, history, rollback, CI — so the benefits of IaC are mostly the benefits of treating operations like software engineering.
Why care: The advantages here are exactly what the exam's Objective 1 asks you to articulate ("describe the advantages of IaC patterns"). More practically, they are the reasons your organization would choose to adopt Terraform at all, and being able to name them is a recurring question theme.
The mental model: Picture two restaurants. One keeps recipes in the head chef's memory; quality swings wildly and a sick chef means chaos. The other writes every recipe down, version-controls them, and reviews changes before they hit the menu. IaC is the second restaurant — consistency comes from the written, reviewed recipe, not from any individual.
⚠️ Common Misconception: People assume the main benefit of IaC is speed. Speed is a nice side effect, but the durable wins are consistency, reviewability, and recoverability. A team can be slower to write Terraform than to click once — but it is dramatically faster and safer the tenth time, in the second region, or during a 2 a.m. recovery.
