What artifact is persisted by the default local backend to track the current state?

What artifact is persisted by the default local backend to track the current state?

• A. tfplan files
• B. Terraform binary
• C. Provider plugins
• D. State file

Answer: (D)

Terraform keeps a record of what exists in your real infrastructure in a state file. The default local backend writes this state to a local file on disk, typically named terraform.tfstate. This file stores the mapping between your configuration and the actual resources (including IDs, attributes, and dependencies), so Terraform can determine what has drifted or what changes are needed on each apply. A backup of the previous state is also kept as terraform.tfstate.backup to help recover if something goes wrong. This state file is not the same as a plan file (which is generated by running plan to preview changes) and it isn’t the Terraform binary or provider plugins, which are separate components. Keeping the state file locally allows Terraform to perform incremental updates and maintain consistency between your configuration and your deployed infrastructure.

Terraform keeps a record of what exists in your real infrastructure in a state file. The default local backend writes this state to a local file on disk, typically named terraform.tfstate. This file stores the mapping between your configuration and the actual resources (including IDs, attributes, and dependencies), so Terraform can determine what has drifted or what changes are needed on each apply. A backup of the previous state is also kept as terraform.tfstate.backup to help recover if something goes wrong. This state file is not the same as a plan file (which is generated by running plan to preview changes) and it isn’t the Terraform binary or provider plugins, which are separate components. Keeping the state file locally allows Terraform to perform incremental updates and maintain consistency between your configuration and your deployed infrastructure.