Terraform

Infrastructure as Code & State Management Guide with Terraform

What is Infrastructure as Code (IaC), and what actual problems does it solve for an operations team?

💬Answer

Infrastructure as Code (IaC) is the practice of provisioning, managing, and configuring IT infrastructure (servers, network topologies, storage, load balancers) using machine-readable configuration files or scripts ("code"), rather than relying on manual server configuration, physical hardware setups, or interactive GUI dashboard configurations.

# Key Benefits:

How do you choose between a provisioning tool like Terraform and a configuration management tool like Ansible?

Walk me through the standard Terraform core workflow. What happens under the hood during each phase?

What is the difference between count and for_each? In what scenarios is for_each the safer choice?

How do dynamic blocks work in Terraform, and can you give me an example of when they are necessary?

How do you distinguish between input variables and local values? When should we use locals?

Can you explain the difference between a resource block and a data source block?

What is the purpose of the Terraform state file, and what strategies do you implement to secure it in production?

Q10

# Production Security Hardening:

Q11

If our remote state file gets corrupted or accidentally deleted, how would you recover it?

Q12

If our Terraform codebase grows into a monolithic state file, how would you split it into modular configurations?

Q13

How do you safely migrate a Terraform state file from a local backend to a remote backend?

Q14

How do tools like Terragrunt, Terraform Cloud, and Atlantis help scale Terraform in an enterprise?

Q15

What is your approach to implementing a GitOps model for infrastructure delivery using Terraform?

Q16

How does Terraform compare to AWS CloudFormation, and why might you prefer one over the other?

Created by

Apurv Gujjar

DevOps & Cloud Engineer

Specialized in:DevOpsAWSGCPKubernetesTerraformDocker

View Portfolio