Q: You want `terraform destroy` to remove a temporary application stack but keep the shared DNS zone and shared VPC. How should the state be structured?
Shared infrastructure should live in separate root modules and state files from temporary application environments.
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: "In our enterprise Terraform repository, we designed reusable modules and remote backends to prevent this exact issue. 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
Shared infrastructure should live in separate root modules and state files from temporary application environments. The app stack can read shared IDs through data sources, SSM parameters, or remote outputs, but it should not own those shared resources. Add prevent_destroy on critical shared resources as a guardrail, but rely primarily on state boundaries.
- Immediate Triage: Shared infrastructure should live in separate root modules and state files from temporary appli
- 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 want terraform destroy 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 want terraform destroy 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 want terraform destroy 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 want terraform destroy Unpinned provider versions automatically download breaking major upgrades during CI runs, introducing unexpected schema validation failures.