Infrastructure as Code (IaC) is the practice of managing and provisioning infrastructure through machine-readable definition files, rather than physical hardware configuration or interactive configuration tools. The core benefits of this approach are rooted in treating infrastructure definitions like software code. This enables versioning, reusability, and automation. A Graphical User Interface (GUI) is not an inherent benefit of IaC; in fact, IaC is often adopted to move away from manual, error-prone GUI-based management towards a more programmatic and automated workflow driven by a Command Line Interface (CLI).

A. Versioning: This is incorrect. Storing infrastructure configurations in a version control system (like Git) to track changes, collaborate, and revert to previous states is a primary benefit of IaC.

C. Reusability of code: This is incorrect. IaC promotes the creation of modular and reusable components (e.g., Terraform modules), which is a key advantage for maintaining consistency and efficiency.

D. Automation: This is incorrect. Automating the entire lifecycle of infrastructure—provisioning, updating, and decommissioning—is a fundamental goal and benefit of adopting IaC.

1. HashiCorp Learn. (n.d.). What is Infrastructure as Code with Terraform?. HashiCorp. Retrieved from https://developer.hashicorp.com/terraform/intro.

Section: Why Infrastructure as Code? This section explicitly lists benefits such as "Improved speed and consistency" (related to Automation and Reusability) and "Improved collaboration" (related to Versioning). It makes no mention of a GUI as a benefit of the IaC practice itself.

2. HashiCorp Documentation. (n.d.). Introduction to Terraform. HashiCorp. Retrieved from https://www.terraform.io/intro.

Section: What is Terraform? This page describes Terraform's workflow as "Write, Plan, and Apply," which is a code-centric, CLI-driven process. The benefits highlighted, such as execution plans and change automation, are direct results of the code-based approach, not a GUI.