Which statement describes a goal of infrastructure as code?

• A. An abstraction from vendor specific APIs
• B. Write once, run anywhere
• C. A pipeline process to test and deliver software
• D. The programmatic configuration of resources

Answer: (D)

Infrastructure as code means describing the desired state of infrastructure through code so it can be stored, reviewed, and applied automatically. The essence is to configure resources programmatically—defining what resources exist, how they are configured, and how they relate to each other, and then using tooling to provision and manage them to match that configuration. This enables repeatable environments, consistent deployments, and auditable changes, because the same code runs to create, update, or destroy resources across environments. Other descriptions touch on related ideas—such as wrapping vendor APIs in an abstraction, portability of software, or pipelines for delivering software—but they don't capture the core practice of expressing infrastructure as code and letting automation enforce the desired state. Therefore, describing the programmatic configuration of resources best captures the goal of infrastructure as code.