Which statement about Terraform's approach to infrastructure as code is true?

Which statement about Terraform's approach to infrastructure as code is true?

• A. You can version your infrastructure configuration
• B. You cannot reuse infrastructure configuration
• C. It requires manual configuration of infrastructure resources
• D. It does not support automation

Answer: (A)

Terraform lets you describe your infrastructure as code using plain text configuration files. Because these files are just text, you can put them under version control, track changes over time, review diffs with teammates, and revert to earlier states when needed. This is why versioning your infrastructure configuration is the natural outcome of Terraform’s approach. In practice, you describe the desired end state, and Terraform computes what must change to reach that state, then applies those changes automatically. That declarative, plan-and-apply workflow is what enables automation and repeatable provisioning. You can also reuse configurations through modules and variables, making it easy to share and compose infrastructure pieces. So while automation, reuse, and a declarative approach are all supported, the ability to version your infrastructure configuration is the clear, true aspect here.

Terraform lets you describe your infrastructure as code using plain text configuration files. Because these files are just text, you can put them under version control, track changes over time, review diffs with teammates, and revert to earlier states when needed. This is why versioning your infrastructure configuration is the natural outcome of Terraform’s approach.

In practice, you describe the desired end state, and Terraform computes what must change to reach that state, then applies those changes automatically. That declarative, plan-and-apply workflow is what enables automation and repeatable provisioning. You can also reuse configurations through modules and variables, making it easy to share and compose infrastructure pieces. So while automation, reuse, and a declarative approach are all supported, the ability to version your infrastructure configuration is the clear, true aspect here.