What provisioning architecture uses declarative configuration files and code to automate deployment of resources?

What provisioning architecture uses declarative configuration files and code to automate deployment of resources?

• A. Infrastructure as Code
• B. Platform as a Service
• C. Configuration Management
• D. Orchestration

Answer: (A)

Infrastructure as Code is the approach that uses declarative configuration files and code to automate the provisioning and deployment of resources. It lets you describe the desired infrastructure state in machine-readable files, and an automation tool applies those files to create, update, or delete resources to match that state. This brings benefits like version control, repeatability, auditable changes, and easier rollback, making infrastructure provisioning as reliable and testable as software development. Platform as a Service provides a managed runtime environment and abstracts away infrastructure, but it isn’t defined by declarative provisioning files for deploying resources. Configuration management focuses on bringing already provisioned systems to a desired state (configuring software and settings) rather than provisioning the underlying infrastructure from scratch. Orchestration coordinates sequences of tasks across systems, which can include deployment steps, but it isn’t primarily the mechanism for defining and provisioning resources via declarative infrastructure files.

Infrastructure as Code is the approach that uses declarative configuration files and code to automate the provisioning and deployment of resources. It lets you describe the desired infrastructure state in machine-readable files, and an automation tool applies those files to create, update, or delete resources to match that state. This brings benefits like version control, repeatability, auditable changes, and easier rollback, making infrastructure provisioning as reliable and testable as software development.

Platform as a Service provides a managed runtime environment and abstracts away infrastructure, but it isn’t defined by declarative provisioning files for deploying resources. Configuration management focuses on bringing already provisioned systems to a desired state (configuring software and settings) rather than provisioning the underlying infrastructure from scratch. Orchestration coordinates sequences of tasks across systems, which can include deployment steps, but it isn’t primarily the mechanism for defining and provisioning resources via declarative infrastructure files.