Which of the following is true about Terraform's implementation of infrastructure as code? (Choose two.)
Which of the following is true about Terraform's implementation of infrastructure as code? (Choose two.)
Terraform’s implementation of infrastructure as code allows you to version your infrastructure configuration and automate infrastructure provisioning. You can version your infrastructure configuration, enabling you to track changes and maintain a history of configurations. Additionally, Terraform allows automation of infrastructure provisioning, reducing the need for manual configuration and ensuring consistency and repeatability in infrastructure management.
A- It soupports hundresds of providers B- You can have version number on your files D-- manual provisioning defeats the very purpose of IaC
I go for CE.
It has to be CE.
C, E are correct
C. You can version your infrastructure configuration. E. It allows you to automate infrastructure provisioning. Terraform's implementation of infrastructure as code has the following characteristics: Option C is true - you can version your infrastructure configuration using version control systems like Git. Terraform supports multiple version control backends such as Git, Subversion, and Mercurial, and allows users to manage multiple versions of infrastructure code in the same repository. Option E is true - Terraform allows you to automate infrastructure provisioning. Terraform uses configuration files to describe the desired state of infrastructure, and then automatically provisions and configures the infrastructure to match that state.
C. You can version your infrastructure configuration E. It allows you to automate infrastructure provisioning The following is true about Terraform's implementation of infrastructure as code: C. You can version your infrastructure configuration: Terraform uses configuration files written in HashiCorp Configuration Language (HCL) to define infrastructure resources. These files can be versioned using a version control system (VCS) such as Git, allowing you to track changes to your infrastructure over time and roll back to previous versions if necessary. E. It allows you to automate infrastructure provisioning: Terraform's infrastructure as code approach allows you to automate the provisioning of infrastructure resources. By defining the desired state of your infrastructure in code, you can use Terraform to create, modify, and delete resources in an automated and repeatable way.
C and E for sure
No doubt about it