What is the primary benefit of using Infrastructure as Code (IaC) tooling like Terraform?

What is the primary benefit of using Infrastructure as Code (IaC) tooling like Terraform?

• A. Declarative, repeatable provisioning of infrastructure with versioned plans
• B. Manual configuration tracking
• C. Real-time monitoring of infrastructure
• D. Automatic software packaging

Answer: (A)

Defining infrastructure as code means expressing the desired state of your resources (servers, networks, permissions, and more) in a reproducible, declarative form. The tooling then brings the actual environment into alignment with that state, making provisioning repeatable and predictable each time you apply the configuration. Because the configuration lives in code and plans can be versioned, you can review, share, and audit changes, and you can reproduce or rollback environments exactly as needed. This approach greatly reduces human error and drift from ad hoc setups, delivering consistent infrastructure across development, testing, and production. Real-time monitoring or automatic packaging are valuable in their own right, but they address different needs; the primary benefit here is the reliable, repeatable provisioning driven by versioned plans.

Defining infrastructure as code means expressing the desired state of your resources (servers, networks, permissions, and more) in a reproducible, declarative form. The tooling then brings the actual environment into alignment with that state, making provisioning repeatable and predictable each time you apply the configuration. Because the configuration lives in code and plans can be versioned, you can review, share, and audit changes, and you can reproduce or rollback environments exactly as needed. This approach greatly reduces human error and drift from ad hoc setups, delivering consistent infrastructure across development, testing, and production. Real-time monitoring or automatic packaging are valuable in their own right, but they address different needs; the primary benefit here is the reliable, repeatable provisioning driven by versioned plans.