Define the purpose of state in Terraform.

• A. State stores variables and lets you quickly reuse existing code
• B. State enforces resource configurations that relate to compliance policies
• C. State codifies the dependencies of related resources
• D. State maps real world resources to your configuration and keeps track of metadata

Answer: (D)

Terraform state serves as the mapping between what you define in your configuration and the real-world resources those definitions create or manage, while also storing metadata about those resources. This is what lets Terraform know which objects exist, their provider IDs (like an AWS instance ID), and attributes needed to perform updates, destroy resources, or read outputs across executions. The state file is the single source of truth Terraform uses to plan changes, detect drift, and apply updates in a safe, incremental way. Keeping this information in a centralized or remote state also enables collaboration and locking so multiple team members don’t step on each other’s changes.

Variables are inputs and don’t by themselves track real resources or their IDs. Policy enforcement is handled by separate mechanisms (policy as code) rather than the state file. The dependency graph is primarily determined from how resources reference each other in your configuration, not directly codified in state, though the state does record the resource mappings and metadata that result from those relationships.