⚡ ~/naveed Interview Prep
⚡ Portfolio Home 👤 About Naveed Bio & Credentials 📫 Contact Naveed Get In Touch ✍️ Engineering Blog Deep Dives 🎯 Interview Hub 1,000+ Scenarios ☸️ Kubernetes Mastery Hub 24 Modules 🎮 DevOps Arcade & Quizzes Subnet Blitz ⚡ 🗺️ DevOps Roadmaps PDFs & Guides 🤖 Morpheus Analysis AI Quant ↗ 🛠️ Developer Tools Utilities 🧪 Labs & Experiments 📄 Interactive CV & Certs 🔗 All Links & Socials ⚡ Join The Dispatch (Weekly SRE Newsletter) →
← Back to All Terraform & IaC Interview Questions Scenario 15 of 120 in Terraform & IaC
Staff SRE / Principal Architect [L3] Terraform Modules & Structure Staff SRE Scenario [L3]
🎯 Target Role / Context: Terraform Scenario #10 (L3) · Modules & Structure

Q: Your Terraform plan wants to destroy and recreate a production RDS instance because you changed the instance identifier. How do you prevent the destroy?

Changing identifier for RDS forces replacement — Terraform deletes the old and creates a new one. That means downtime and potential data loss.

#Terraform #Modules & Structure #L3 #IaC #Cloud Infrastructure #Terraform State
🎙️ Candidate Opening & Architectural Context
""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.""
Advertisement
⚡ Recommended Practice Lab

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."

1️⃣

Initial Diagnostics & Root Cause Analysis

Changing identifier for RDS forces replacement — Terraform deletes the old and creates a new one. That means downtime and potential data loss.

  • Lifecycle ignore_changes:
  • lifecycle prevent_destroy:
  • terraform state mv — rename the resource in state without destroying:
2️⃣

Remediation & Permanent Safeguards

Prevent destruction: This tells Terraform to ignore changes to the identifier field. Terraform will throw an error if anything tries to destroy this resource. Hard safety net. Update the config, then plan — Terraform sees the state and config match, no destroy needed.

lifecycle {
  ignore_changes = [identifier]
}
💡 The Senior SRE Gold Nugget (Key Architectural Takeaway)
"Pro-Tip: Lifecycle ignore_changes:."
⚡ 60-Second Elevator Pitch Talking Points
  • Lifecycle ignore_changes:
  • lifecycle prevent_destroy:
  • terraform state mv — rename the resource in state without destroying:
⛔ Critical Candidate Mistakes to Avoid in This Scenario

Senior hiring managers and bar raisers evaluate how you prioritize during outages. Avoid these common anti-patterns:

  1. Executing Terraform applies without inspecting '# forces replacement' warnings in plan output when configuring Terraform plan wants Attributes that force resource replacement destroy and recreate critical infrastructure (databases, load balancers), inducing unannounced production outages.
  2. Omitting remote state locking mechanisms (DynamoDB or backend native locks) for shared state files when configuring Terraform plan wants Without state locking, concurrent CI/CD pipeline executions or team applies create race conditions that corrupt the state file.
  3. Structuring entire enterprise cloud footprints into a single monolithic Terraform root module when configuring Terraform plan wants Monolithic state files slow plan execution dramatically, increase blast radius during failed applies, and create severe pipeline locking contention.
  4. Failing to pin required_providers versions, causing breaking provider upgrades in CI pipelines when configuring Terraform plan wants Unpinned provider versions automatically download breaking major upgrades during CI runs, introducing unexpected schema validation failures.
Advertisement
Want more Terraform & IaC scenarios?
Explore our complete collection of scenario-based Terraform & IaC interview runbooks.
Browse All Terraform & IaC Questions →