⚡ ~/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 10 of 120 in Terraform & IaC
Senior DevOps / SRE [L2] Terraform State & Locking Production Scenario [L2]
🎯 Target Role / Context: Terraform Scenario #5 (L2) · State & Locking

Q: `terraform plan` shows changes to a resource that you didn't touch. Why might this happen?

Several reasons:

#Terraform #State & Locking #L2 #IaC #Cloud Infrastructure #Terraform State
🎙️ Candidate Opening & Architectural Context
""Managing infrastructure as code across multiple teams requires disciplined state management and locking. 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: "Managing infrastructure as code across multiple teams requires disciplined state management and locking. 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

Several reasons:

  • Provider upgrade — a newer provider version may compute resource attributes differently.
  • Drift — someone changed the resource manually in the console. Plan detects the difference.
  • Sensitive attribute — some resources always show as changed due to how Terraform handles sensitive fields (passwords, keys).
  • Computed values — some attributes are computed by the cloud provider and Terraform can't know them until apply time. Shows as (known after apply).
2️⃣

Remediation & Permanent Safeguards

Check terraform show to see what the current state says vs what the config says.

  • Timestamp/random changes — some providers generate new values on each plan.
  • Deprecated attribute — provider changed default for an attribute.
💡 The Senior SRE Gold Nugget (Key Architectural Takeaway)
"Pro-Tip: Provider upgrade — a newer provider version may compute resource attributes differently.."
⚡ 60-Second Elevator Pitch Talking Points
  • Provider upgrade — a newer provider version may compute resource attributes differently.
  • Drift — someone changed the resource manually in the console. Plan detects the difference.
  • Sensitive attribute — some resources always show as changed due to how Terraform handles sensitiv...
⛔ 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 shows 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 shows 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 shows 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 shows in terraform-q005-terraform-plan-shows-changes-to-a-r 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 →