Which of the following is a key feature of Terraform's infrastructure as code?

Which of the following is a key feature of Terraform's infrastructure as code?

• A. Manual configuration of each resource
• B. Automated dependency resolution
• C. Direct manipulation of cloud service provider APIs
• D. Real-time updates to live infrastructure

Answer: (B)

Automated dependency resolution is a key feature of Terraform's infrastructure as code because it allows Terraform to understand the relationships and dependencies between different resources. This means that when you define multiple interrelated resources in your configuration, Terraform automatically determines the order of operations needed to create, update, or delete them. For example, if one resource depends on another, Terraform will ensure that the dependent resource is created only after its parent resource is successfully created, even if they are defined in the same configuration file. This feature enhances the reliability and efficiency of infrastructure management, as users do not need to manually manage the order of resource operations. Terraform's ability to automate these dependencies minimizes the likelihood of errors and improves the overall deployment process. In contrast, features such as manual configuration of each resource undermine the automated and declarative nature of Terraform. Direct manipulation of cloud service provider APIs details a more hands-on, imperative approach rather than leveraging Terraform's abstraction layer, and real-time updates to live infrastructure suggest modifications that could disrupt the existing state rather than adhering to a defined configuration model. These options do not embody the strengths and purpose of Terraform's design principles.

Automated dependency resolution is a key feature of Terraform's infrastructure as code because it allows Terraform to understand the relationships and dependencies between different resources. This means that when you define multiple interrelated resources in your configuration, Terraform automatically determines the order of operations needed to create, update, or delete them. For example, if one resource depends on another, Terraform will ensure that the dependent resource is created only after its parent resource is successfully created, even if they are defined in the same configuration file.

This feature enhances the reliability and efficiency of infrastructure management, as users do not need to manually manage the order of resource operations. Terraform's ability to automate these dependencies minimizes the likelihood of errors and improves the overall deployment process.

In contrast, features such as manual configuration of each resource undermine the automated and declarative nature of Terraform. Direct manipulation of cloud service provider APIs details a more hands-on, imperative approach rather than leveraging Terraform's abstraction layer, and real-time updates to live infrastructure suggest modifications that could disrupt the existing state rather than adhering to a defined configuration model. These options do not embody the strengths and purpose of Terraform's design principles.