AWS Certified DevOps Engineer – ProfessionalSDLC AutomationEasy
A large enterprise is migrating its legacy applications to AWS. They need a standardized and repeatable way to provision and manage their infrastructure across multiple AWS accounts and regions. The solution must support version control, prevent configuration drift, and integrate with their existing CI/CD pipelines. Which AWS service or approach should they adopt?
- ADevelop custom shell scripts to provision resources.
- BImplement Infrastructure as Code (IaC) using AWS CloudFormation or Terraform.
- CManually provision resources using the AWS Management Console.
- DUse AWS Service Catalog to provide pre-approved products to users.
Show answer & explanationAnswer & explanation
Correct answer: B. Implement Infrastructure as Code (IaC) using AWS CloudFormation or Terraform.
Infrastructure as Code (IaC) using tools like AWS CloudFormation or Terraform allows infrastructure to be defined in code, enabling version control, automated provisioning, and preventing configuration drift, which are critical for standardization and integration with CI/CD.
Why the other options are wrong
- A. Custom scripts can provision but lack built-in version control, drift detection, and declarative management.
- C. Manual provisioning is error-prone, not repeatable, and doesn't support version control or prevent drift.
- D. Service Catalog provides curated products but doesn't define or manage the underlying infrastructure as code directly.
Infrastructure as Code (IaC)
Managing and provisioning computer data centers through machine-readable definition files, rather than physical hardware configuration or interactive configuration tools. The IT infrastructure is treated like software.
- Defines infrastructure in code (e.g., JSON, YAML, HCL).
- Enables version control, automation, and repeatability.
- Prevents configuration drift.
- Tools include AWS CloudFormation, Terraform, Ansible.
Memory trick: IaC: Code builds the cloud, no more manual clicks.