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 is about describing and provisioning infrastructure through code, so you manage resources programmatically. That aligns with defining the desired state of your resources in configuration files and using a tool to create or update the actual infrastructure to match that declaration. This approach enables versioning, repeatability, automation, and easier collaboration across environments.

The other ideas aren’t the primary aim: a pipeline to test and deliver software points to CI/CD processes rather than how infrastructure is defined; a vendor-agnostic API is about interfaces rather than the practice of defining resources; and write-once, run-anywhere speaks to portability in a broader sense, not the specific practice of configuring infrastructure with code.