Rationale for Correct Answer: A major IaC advantage is declarative desired state: you describe what you want, and the tool figures out the necessary create/update/delete API calls to converge infrastructure to that end state. This reduces manual API orchestration and makes changes repeatable and reviewable.
Analysis of Incorrect Options (Distractors):
A: Incorrect—IaC reduces the need to write individual API calls; that’s the point.
B: Incorrect—IaC tools typically use provider plugins and APIs; efficiency is not about “calling CLI tools.”
C: Incorrect—IaC configurations define desired state; “current state” is discovered via refresh/state, not defined as the goal.
Key Concept: Declarative IaC: define end state, tool determines API actions.
[Reference: Terraform Objectives — Understand Infrastructure as Code (IaC) Concepts; Understand Terraform’s Purpose and Use Cases., , ]
Contribute your Thoughts:
Chosen Answer:
This is a voting comment (?). You can switch to a simple comment. It is better to Upvote an existing comment if you don't have anything to add.
Submit