What is a principle of Infrastructure as Code?

The correct answer is C. It encourages repeatable processes. Infrastructure as Code (IaC) is the practice of managing and provisioning infrastructure through machine-readable configuration files rather than manual processes. A core principle is repeatability (and idempotency): the same code, run multiple times, produces the same…

Infrastructure and Automation

Question

Options

AIt requires manual resource provisioning.
BIt encourages overlaps in services.
CIt encourages repeatable processes.
DIt requires the use of large components.

How the community answered

(22 responses)

C
95% (21)
D
5% (1)

Explanation

Infrastructure as Code (IaC) is the practice of managing and provisioning infrastructure through machine-readable configuration files rather than manual processes. A core principle is repeatability (and idempotency): the same code, run multiple times, produces the same infrastructure state consistently. This eliminates configuration drift and allows environments (dev, staging, prod) to be reliably reproduced. Option A is incorrect - IaC replaces manual provisioning with automation. Option B is incorrect - IaC promotes single-responsibility and DRY (Don't Repeat Yourself) principles, avoiding service overlaps. Option D is incorrect - IaC favors modular, composable components, not large monolithic ones.

Topics

#Infrastructure as Code (IaC)#Automation Principles#Repeatability

Community Discussion

No community discussion yet for this question.

Full 200-901 Practice