What is true about the Terraform state file?

• A. It is optional and not used by the engine
• B. It stores the current state of managed resources
• C. It contains only configuration data
• D. It is generated by the cloud provider

Answer: (B)

Terraform state file holds the known real-world state of the infrastructure Terraform manages. It records the current state of all resources under management, including provider-assigned IDs and the attributes Terraform has learned. This snapshot lets Terraform map your configuration to what exists in your cloud accounts, figure out what needs to be created, changed, or destroyed, and apply those changes in a deterministic way. The engine relies on this state during planning and applying, so the state is essential rather than optional. It isn’t generated by the cloud provider; Terraform writes it (locally by default or in a remote backend you configure). It also isn’t just configuration data—the configuration defines what you want, while the state file captures what Terraform has actually deployed. Because the state can contain sensitive information, it should be stored and access-controlled securely.