Hashicorp Certified Terraform Associate 003 · Free Practice Question Easy
Question 10
Infrastructure as Code (IaC) offers many benefits to help organizations deploy application infrastructure faster than manually clicking through the console. Which of the following is NOT a benefit of Infrastructure as Code (IaC)?
-
A
allows infrastructure to be versioned
-
B
creates self-documenting infrastructure
-
C
eliminates API communication to the target platform
-
D
code can easily be shared and reused
Reveal correct answer
Correct answer: C
Explanation
Eliminating API communication to the target platform is NOT a benefit of IaC. In fact, Terraform likely increases communication with the backend platform since Terraform uses the platform's API to build and manage infrastructure.
Remember that Terraform providers/plugins are essentially the features that enable communication with the platform's API on your behalf.
WRONG ANSWERS:
All of the wrong answers are essentially direct benefits of using Terraform.
https://learn.hashicorp.com/tutorials/terraform/infrastructure-as-code
A. One of the key benefits of Infrastructure as Code (IaC) is the ability to version infrastructure configurations just like code. This allows teams to track changes, revert to previous versions if needed, and collaborate more effectively on infrastructure changes.
B. Infrastructure as Code (IaC) enables the creation of self-documenting infrastructure by defining infrastructure configurations in code. This means that the code itself serves as documentation for the infrastructure, making it easier to understand, maintain, and troubleshoot.
C. Infrastructure as Code (IaC) actually relies on API communication to the target platform to automate the provisioning and management of infrastructure. By using APIs, IaC tools can interact with cloud providers and other platforms to create, update, and manage resources. Eliminating API communication would hinder the automation capabilities of IaC.
D. With Infrastructure as Code (IaC), code that defines infrastructure can easily be shared and reused across teams and projects. This promotes consistency, reduces duplication of effort, and accelerates the deployment of infrastructure by leveraging existing code modules and templates.
Discussion
Think the marked answer is wrong, or have a better explanation? Share it below — comments appear after review.
