← DevOps tools
Infrastructure / Practice

Infrastructure as Code

The practice of defining infrastructure in versioned, declarative or procedural code instead of configuring it manually.

Why it exists.

It solves environment drift and makes infrastructure changes reviewable, repeatable, and recoverable.

Where it shines.

Cloud and platform environments that need reproducible environments, peer review, and automated provisioning.

Where not to use it.

Do not automate unclear architecture or treat stateful production changes as disposable without a migration and recovery plan.

What it is made of.

  • Configuration files
  • State
  • Providers or APIs
  • Plan and apply workflow
  • Modules

How it works.

  1. Code describes the desired infrastructure
  2. A plan previews the difference
  3. Changes are reviewed and approved
  4. Automation applies and records the new state
Questions and answers.Open the interview practice set for Infrastructure as Code.
Search