Question

A DevOps engineer notices that when they run 'terraform plan' after provisioning infrastructure, Terraform correctly reports 'No changes' even though the configuration files contain resources that already exist in AWS. A new team member asks how Terraform knows which real-world AWS resources correspond to the resources declared in the configuration without re-querying and re-creating everything. What is the correct explanation?

Accepted Answer

Terraform maintains a state file that stores the mapping between configuration resources and the real infrastructure objects, along with their attributes.

Answer

Terraform tags every real resource with a hidden metadata label and scans all cloud accounts on each plan to rebuild the mapping.

Answer

Terraform relies entirely on the AWS provider's live API to infer which resources belong to the configuration during each run.

Answer

Terraform embeds resource identifiers directly inside the .tf configuration files so no separate tracking mechanism is needed.