Which statement describes a goal of infrastructure as code?

Which statement describes a goal of infrastructure as code?

• A. A pipeline process to test and deliver software
• B. Defining a vendor-agnostic API
• C. Write once, run anywhere
• D. The programmatic configuration of resources

Answer: (D)

Infrastructure as code treats infrastructure configuration as software, allowing you to define and manage resources through code so they can be provisioned, versioned, and reproduced automatically. The goal is the programmatic configuration of resources—describe what exists (servers, networks, storage, policies) in configuration files and have a tool create and maintain the real-world infrastructure to match that declaration. This enables repeatable, automated provisioning with an auditable history and reduces manual, error-prone steps. Other options describe related ideas but not the core aim: a pipeline for software delivery focuses on CI/CD workflows; defining a vendor-agnostic API is about interoperability rather than provisioning infrastructure; and write-once, run-anywhere is a broad portability claim that isn’t the primary objective of IaC.

Infrastructure as code treats infrastructure configuration as software, allowing you to define and manage resources through code so they can be provisioned, versioned, and reproduced automatically. The goal is the programmatic configuration of resources—describe what exists (servers, networks, storage, policies) in configuration files and have a tool create and maintain the real-world infrastructure to match that declaration. This enables repeatable, automated provisioning with an auditable history and reduces manual, error-prone steps.

Other options describe related ideas but not the core aim: a pipeline for software delivery focuses on CI/CD workflows; defining a vendor-agnostic API is about interoperability rather than provisioning infrastructure; and write-once, run-anywhere is a broad portability claim that isn’t the primary objective of IaC.