Which is not a benefit of adopting infrastructure as code?

Which is not a benefit of adopting infrastructure as code?

• A. Interpolation
• B. Reusability of code
• C. Versioning
• D. Automation

Answer: (A)

Infrastructure as code delivers repeatable, automated deployments, versioned configurations, and reusable components. You can store your desired state in a version control system, build modular pieces you can reuse across projects, and automate the provisioning process to ensure consistent environments and reduce drift. Interpolation is a language feature that lets you compute values by referencing variables or other attributes within your configuration. While useful for constructing strings or deriving values, it isn’t a benefit introduced by adopting IaC itself—it's simply a technique you use inside the code. So the option that isn’t a benefit of adopting infrastructure as code is interpolation.

Infrastructure as code delivers repeatable, automated deployments, versioned configurations, and reusable components. You can store your desired state in a version control system, build modular pieces you can reuse across projects, and automate the provisioning process to ensure consistent environments and reduce drift. Interpolation is a language feature that lets you compute values by referencing variables or other attributes within your configuration. While useful for constructing strings or deriving values, it isn’t a benefit introduced by adopting IaC itself—it's simply a technique you use inside the code. So the option that isn’t a benefit of adopting infrastructure as code is interpolation.