Kubernetes and Cloud Native Associate (KCNA)Cloud Native DeliveryMedium
A startup is building a new application and wants to automate the process of provisioning the underlying cloud infrastructure (e.g., virtual machines, networks, databases) consistently and repeatedly. They aim to treat infrastructure like application code, storing its definition in a version control system. Which approach aligns with this goal?
- AContainerization of infrastructure services
- BShell scripting for one-time setup
- CManual provisioning via cloud provider console
- DInfrastructure as Code (IaC)
Show answer & explanationAnswer & explanation
Correct answer: D. Infrastructure as Code (IaC)
Infrastructure as Code (IaC) is the practice of managing and provisioning computing infrastructure through machine-readable definition files, rather than physical hardware configuration or interactive configuration tools. It enables version control, automation, and consistent environments.
Why the other options are wrong
- A. Containerization is for applications, not the underlying infrastructure provisioning itself.
- B. Shell scripting can automate some tasks but often lacks the declarative nature and idempotency of IaC.
- C. Manual provisioning is error-prone and lacks repeatability and version control.
Infrastructure as Code (IaC)
The practice of managing and provisioning computing infrastructure (e.g., networks, virtual machines, load balancers) using machine-readable definition files, rather than manual configuration or interactive tools.
- Treats infrastructure configuration like application code.
- Enables version control, automation, and repeatability.
- Promotes consistency and reduces configuration drift.
Memory trick: IaC builds your cloud empire from a blueprint.