Q: You ran `terraform apply` and now the state file shows resources that no longer exist in the cloud. How do you fix this?
Use terraform refresh to sync state with actual infrastructure, or more precisely terraform plan -refresh-only to see what would change.
Want to master this scenario in a live sandbox? KodeKloud's HashiCorp Certified Terraform Associate (003) Interactive Labs covers this exact problem with hands-on terminal drills.
🛠️ Production Runbook & Step-by-Step Resolution
Direct Answer: "Managing infrastructure as code across multiple teams requires disciplined state management and locking. When addressing this question, I walk the interviewer through our production incident runbook: isolating the blast radius, checking diagnostic logs and metrics, and applying a safe fix."
Production Solution & Architecture
Use terraform refresh to sync state with actual infrastructure, or more precisely terraform plan -refresh-only to see what would change. For specific resources: terraform state rm removes them from state without deleting the actual resource. Useful when a resource was deleted manually from the console. Then run terraform plan — it will show what needs to be created to reach desired state.
- Immediate Triage: Use terraform refresh to sync state with actual infrastructure, or more precisely terraform pla
- Run targeted verification commands before modifying configuration.
- Automate permanent guardrails (CI check, alerts, IaC policy) to prevent recurrence.
Senior hiring managers and bar raisers evaluate how you prioritize during outages. Avoid these common anti-patterns:
- Executing Terraform applies without inspecting '# forces replacement' warnings in plan output when configuring terraform apply state Attributes that force resource replacement destroy and recreate critical infrastructure (databases, load balancers), inducing unannounced production outages.
- Omitting remote state locking mechanisms (DynamoDB or backend native locks) for shared state files when configuring terraform apply state Without state locking, concurrent CI/CD pipeline executions or team applies create race conditions that corrupt the state file.
- Structuring entire enterprise cloud footprints into a single monolithic Terraform root module when configuring terraform apply state Monolithic state files slow plan execution dramatically, increase blast radius during failed applies, and create severe pipeline locking contention.
- Failing to pin required_providers versions, causing breaking provider upgrades in CI pipelines when configuring terraform apply state Unpinned provider versions automatically download breaking major upgrades during CI runs, introducing unexpected schema validation failures.