What is the primary purpose of the Terraform state file?

What is the primary purpose of the Terraform state file?

• A. To log changes to resources
• B. To map real-world resources to Terraform resources in your configuration and store metadata
• C. To validate configurations
• D. To store modules

Answer: (B)

The key idea is that Terraform state records the actual resources that exist in your environment and links them to the corresponding resources defined in your configuration. The state file maps each real-world resource to its Terraform resource block and stores important metadata like resource IDs, attributes, and dependencies. This snapshot lets Terraform know what it should manage, what already exists, and how resources relate to one another, so it can plan and apply changes accurately. With this state in hand, Terraform can determine what needs to be created, updated, or destroyed, and it can perform updates in the right order based on dependencies. It also enables drift detection by comparing the real resources in the provider with what's stored in state, so you can see what has diverged from your configuration. The state file isn’t used for logging changes, validating configurations, or storing modules; those responsibilities come from other parts of the Terraform workflow and tooling. For teams and collaborative setups, state can be stored remotely with locking to prevent conflicting changes.

The key idea is that Terraform state records the actual resources that exist in your environment and links them to the corresponding resources defined in your configuration. The state file maps each real-world resource to its Terraform resource block and stores important metadata like resource IDs, attributes, and dependencies. This snapshot lets Terraform know what it should manage, what already exists, and how resources relate to one another, so it can plan and apply changes accurately.

With this state in hand, Terraform can determine what needs to be created, updated, or destroyed, and it can perform updates in the right order based on dependencies. It also enables drift detection by comparing the real resources in the provider with what's stored in state, so you can see what has diverged from your configuration. The state file isn’t used for logging changes, validating configurations, or storing modules; those responsibilities come from other parts of the Terraform workflow and tooling. For teams and collaborative setups, state can be stored remotely with locking to prevent conflicting changes.