Detailed Explanation:
Rationale for Correct Answer: Infrastructure as Code (IaC) focuses on defining and managing infrastructure using configuration files and automation, rather than manual processes. While IaC provides benefits like automation, reusability, and version control, it does not inherently provide a GUI. In fact, IaC is typically CLI-driven and code-centric, which is the opposite of relying on graphical interfaces.
Analysis of Incorrect Options (Distractors):
A. Reusability of code Incorrect because IaC enables reusable modules and templates, which is a key benefit.
B. Automation Incorrect because IaC automates infrastructure provisioning and management.
D. Versioning Incorrect because IaC configurations can be stored in version control systems (e.g., Git), enabling tracking and rollback.
Key Concept: IaC emphasizes automation, consistency, reusability, and version control, not graphical interfaces.
[Reference: Terraform Objective Domain: Understand Infrastructure as Code (IaC) Concepts, , , , , ]