Interview Infrastructure as Code (Terraform, Ansible)

What is Infrastructure as Code, and what problems does it solve over click-ops?

Infrastructure as Code (Terraform, Ansible) · Basic level

Answer

Infrastructure as Code is the practice of defining infrastructure in version-controlled files instead of creating it manually through consoles. It solves inconsistent environments, undocumented click-ops, poor auditability, slow provisioning, and configuration drift by making infrastructure repeatable, reviewable, and automated.

Technical explanation

Click-ops is fast for experiments but weak for production because it leaves no reproducible desired state.

IaC gives code review, peer approval, rollback history, automated validation, and consistent environment creation.

The value is not just speed; it is operational control, auditability, and the ability to rebuild after failure.

Keep Terraform's ownership boundary clear: one state should own a resource or field, and other tools should consume published outputs instead of modifying it.

Use fmt, validate, linting, policy checks, plan review, and state locking before production applies.

Design for small blast radius by splitting state around lifecycle, permissions, and recovery boundaries.

Hands-on example

1. Build a small IaC workflow for: What is Infrastructure as Code, and what problems does it solve over click-ops?

2. Create a Git repository with folders terraform/network and ansible/web. Put cloud resources in Terraform and host configuration in Ansible.

3. Add a minimal Terraform resource and run the standard workflow:

cd terraform/network

terraform init

terraform fmt -check

terraform validate

terraform plan -out=tfplan

terraform apply tfplan

4. Commit the plan output summary to the pull request, require approval, then use Ansible after infrastructure exists:

ansible-inventory -i inventory/aws_ec2.yml --graph

ansible-playbook -i inventory/aws_ec2.yml ansible/web/site.yml --check --diff

ansible-playbook -i inventory/aws_ec2.yml ansible/web/site.yml

5. Prove the benefit by rebuilding a dev environment from Git and confirming there are no manual console steps.

Preparing for an interview?

Check how well your resume matches the role with our free resume checker— match score, ATS check, and the skills you're missing.

More Infrastructure as Code (Terraform, Ansible) interview questions

← All Infrastructure as Code (Terraform, Ansible) questions