Q: `terraform plan` takes 45 minutes because it reads hundreds of data sources across accounts and regions. How would you improve it?
First identify the slow resources and data sources from provider logs or CI timing.
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: "When terraform plan shows unexpected changes, my golden rule is: never apply blindly. Investigate the diff first. 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
First identify the slow resources and data sources from provider logs or CI timing. Replace broad data-source lookups with explicit inputs where possible, split unrelated infrastructure into separate state files, and avoid refreshing stacks that do not need to change. For shared IDs like VPCs or subnets, publish stable values through SSM Parameter Store or a controlled output contract instead of scanning cloud APIs every plan.
- Immediate Triage: First identify the slow resources and data sources from provider logs or CI timing. Replace bro
- 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 plan takes 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 plan takes 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 plan takes 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 plan takes Unpinned provider versions automatically download breaking major upgrades during CI runs, introducing unexpected schema validation failures.