Question

A platform team manages a large Terraform configuration with hundreds of resources spanning several cloud services. During each `terraform plan`, engineers notice that Terraform does not query every provider API from scratch to rebuild the full picture of what exists; instead it uses recorded resource metadata and can process independent resources concurrently. Which benefit of Terraform state is primarily responsible for this behavior?

Accepted Answer

State stores resource metadata and dependency information, letting Terraform improve performance and determine what can be operated on in parallel without re-reading every attribute from the provider.

Answer

State encrypts all provider credentials so that API calls are authenticated faster on subsequent runs.

Answer

State converts the declarative configuration into an imperative execution script that runs faster each time.

Answer

State disables provider API calls entirely, so Terraform never contacts the cloud during a plan.