Q: You need one Terraform pipeline to deploy only the modules that changed in a monorepo. How would you design that?
Split the repo into independent root modules, each with its own backend key and pipeline target. In CI, detect changed paths, map them to affected root modules, and run terraform plan only for those modules.
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: "Treat Terraform code with the same rigor as application code: pre-merge plans, state locks, and automated drift detection. 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
Split the repo into independent root modules, each with its own backend key and pipeline target. In CI, detect changed paths, map them to affected root modules, and run terraform plan only for those modules. Keep shared modules versioned or at least include dependency rules so that a shared module change triggers plans for all consumers. This scales much better than one giant root module with a single state file.
- Immediate Triage: Split the repo into independent root modules, each with its own backend key and pipeline target
- 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 need Terraform pipeline 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 need Terraform pipeline 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 need Terraform pipeline 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 need Terraform pipeline Unpinned provider versions automatically download breaking major upgrades during CI runs, introducing unexpected schema validation failures.