HashiCorp Certified: Terraform Associate free question 1 / 10 · Domain 1: Infrastructure as Code (IaC) with Terraform
An architect is explaining to a security team how Terraform actually reaches the platforms it manages. Which explanation matches the Terraform introduction?
- Terraform logs in to each platform console and drives it the way an operator would.
- Terraform works through the platform APIs, using providers written for each platform.
- Terraform connects to each server over SSH and edits configuration files on the host.
- Terraform sends change requests by e-mail to the platform team, who apply them by hand.
Show the answer and explanation
Answer: B
Why this is correct
Under "How does Terraform work?", the introduction states that Terraform creates and manages resources on cloud platforms and other services through their application programming interfaces (APIs). It continues that providers enable Terraform to work with virtually any platform or service with an accessible API, and that HashiCorp and the community have written thousands of providers, all publicly listed on the Terraform Registry. This is also why Terraform is not limited to one vendor: if a service exposes an API and a provider exists for it, the same tool and workflow can manage it.
Why the other options are wrong
"Terraform logs in to each platform console and drives it the way an operator would." … The introduction names the path: Terraform creates and manages resources on cloud platforms and other services through their application programming interfaces (APIs), and providers enable it to work with virtually any platform or service with an accessible API. A console is the screen a person uses; the API is what the provider calls.
"Terraform connects to each server over SSH and edits configuration files on the host." … Logging in to hosts and editing files describes server configuration, not how Terraform reaches platforms. The documented path is the platform API, reached through a provider for that platform or service.
"Terraform sends change requests by e-mail to the platform team, who apply them by hand." … Terraform applies the changes itself. After approval it performs the proposed operations in the correct order; a manual hand-off to another team is the ticket-based process that the use cases describe replacing with automation.
The chain to remember
Configuration, then Terraform, then a provider, then the platform API. Questions that ask how Terraform "talks to" AWS, Azure, GitHub, or a SaaS product are asking about this chain.