Which approach makes infrastructure repeatable and reviewable?
Why B is the answer
Terraform
Terraform defines infrastructure as code, which makes it repeatable and reviewable.
In detail
- Terraform defines infrastructure as reviewable code.
- Keep the state file safe.
Use case
An illustrative scenario, not a real incident.
A team defines its network in Terraform, and reviews each change.
See it in different ways
sequenceDiagram participant D as Developer participant P as CI/CD pipeline participant C as Canary participant U as All users D->>P: Reviewed change P->>C: Small share of traffic C-->>P: Alerts on user-facing symptoms P->>U: Complete the rollout, or roll back
flowchart LR S0["Write"] --> S1["Review"] --> S2["Plan"] --> S3["Apply"]
Key point: Terraform makes infrastructure repeatable.
Why the other options are wrong
- A. Console changes with written notes
- Notes are not code.
- C. Clicking in the console
- Clicks are not repeatable.
- D. Editing VMs by hand
- Hand edits are not repeatable.