Mastering Terraform

In the modern cloud, you never click buttons in the Azure or AWS portal to create a server. You write Terraform. It allows you to define your entire Infrastructure as Code (IaC).

1. Declarative vs Imperative

Terraform is Declarative. You describe the "End State" (e.g., "I want 3 VMs and a Load Balancer"). You don't tell it HOW to build them. Terraform calculates the minimum number of steps to reach that state. This is safer than scripts that might fail halfway through.

2. Providers & Resources

Terraform uses Providers (plugins) to talk to AWS, Azure, GCP, or even GitHub. You define **Resources** (the things you want to create) and **Data Sources** (things that already exist). This makes your infrastructure reusable and version-controlled.

4. Interview Mastery

Q: "What is the 'Terraform Plan' and why is it mandatory?"

Architect Answer: "`terraform plan` is a 'Dry Run.' It shows you exactly what Terraform will Create, Modify, or Delete before it actually does it. For an architect, this is the most important step. It prevents accidental deletions of production databases by showing you the impact of your code change before you commit to it."