Q: An engineer ran `terraform apply` with the wrong AWS profile and created resources in the wrong account. How do you reduce the chance of this happening again?
Make the account context explicit in CI and local workflows. Use assume_role with fixed account IDs, print the current caller identity in pipeline logs, and prefer OIDC or dedicated roles over manually exported credentials.
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
Make the account context explicit in CI and local workflows. Use assume_role with fixed account IDs, print the current caller identity in pipeline logs, and prefer OIDC or dedicated roles over manually exported credentials. Some teams also add validation checks that compare the expected account ID against data.aws_caller_identity.current.account_id and fail if they do not match.
- Immediate Triage: Make the account context explicit in CI and local workflows. Use assume_role with fixed account
- 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 wrong 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 wrong 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 wrong 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 wrong Unpinned provider versions automatically download breaking major upgrades during CI runs, introducing unexpected schema validation failures.