⚡ ~/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 Linux & SRE Interview Questions Scenario 130 of 135 in Linux & SRE
Staff SRE / Principal Architect Linux & SRE Blameless Culture & Postmortems Top 10 Toughest
🎯 Target Role / Context: Principal SRE / Staff Platform Engineer Interview

Q: Tell me a real scenario where YOU introduced a failure in infrastructure. What happened, what did you learn, and what changed after?

Master-level behavioral and technical narrative answering the classic senior interview question: 'Tell me about a time you broke production, what you learned, and what changed.'

#Linux & SRE #DevOps Culture #Postmortem #Blameless Culture #Human Error #Blast Radius #SRE #Top 10 Toughest #Toughest Questions #Production Scenarios
🎙️ Candidate Opening & Architectural Context
"Senior interviewers ask this question not to penalize failure, but to measure accountability, crisis composure, and engineering maturity. Junior engineers blame others or claim they've never broken production. Senior engineers candidly describe a complex production outage they triggered, walk through the fast recovery, and explain the automated guardrails they built to make that failure class impossible for anyone in the future."
Advertisement
⚡ Recommended Practice Lab

Want to master this scenario in a live sandbox? The Linux Foundation's Certified System Administrator (LFCS) & SRE Track covers this exact problem with hands-on terminal drills.

🛠️ Production Runbook & Step-by-Step Resolution

Direct Answer: Senior interviewers ask this question not to penalize failure, but to measure accountability, crisis composure, and engineering maturity. Junior engineers blame others or claim they've never broken production. Senior engineers candidly describe a complex production outage they triggered, walk through the fast recovery, and explain the automated guardrails they built to make that failure class impossible for anyone in the future.

1

The Situation & The Incident (What I Broke)

During a routine Terraform refactoring of our AWS networking layer, I was renaming a security group module to follow new company naming standards. While terraform plan showed changes to security group descriptions and tags, I missed that changing the resource identifier in HCL caused Terraform to plan a destructive replacement (destroy and then create) of the primary Redis ElastiCache security group instead of an in-place update. Upon running apply, Terraform dropped the existing security group before the replacement provisioned, instantly severing 40,000 active web client connections and causing 500 Internal Server Errors across checkout.

2

Immediate Actions & Blast Radius Containment

I did not panic or attempt a convoluted rollback. I immediately joined the incident channel, announced: 'I just ran a Terraform apply on the Redis security group that destroyed the ingress rule; I am manually attaching the prior security group right now.' Using AWS CLI, I re-attached the legacy security group to the ElastiCache cluster within 90 seconds, restoring customer checkout. Total outage duration: 2 minutes 15 seconds.

Advertisement
3

Root Cause Analysis (Why the Failure Occurred)

The failure was not merely 'human error.' The systemic weaknesses were: 1. Terraform lacked create_before_destroy = true lifecycle rules on networking dependencies. 2. CI pipeline did not enforce automated plan checking for destructive actions (- or - / +). 3. Applying Terraform changes to production was permitted from local engineer workstations rather than strictly through an automated GitOps pipeline with approval gates.

4

What Changed After: Systemic Guardrails Implemented

I authored a blameless post-mortem and implemented three permanent platform safeguards: 1. Policy as Code (OPA Conftest / Sentinel): Blocked any PR from merging if the plan contains destructive replacements of stateful resources (aws_security_group, aws_db_instance, aws_elasticache_cluster). 2. Mandatory State Move Procedures: Established runbooks requiring terraform state mv when renaming resources to guarantee in-place refactoring. 3. Atlantis GitOps Gateways: Revoked local AWS apply permissions; all production Terraform changes now run strictly via Atlantis with two peer approvals.

Pro Tip: Interview Golden Standard: Own the mistake completely, focus on systemic organizational improvements rather than personal blame, and demonstrate how you made the system permanently safer.
💡 The Senior SRE Gold Nugget (Key Architectural Takeaway)
"Engineering maturity is measured by ownership and architectural remediation. Frame your failure around: 1) What broke and why, 2) Fast containment, 3) Systemic root causes, 4) Automated guardrails (Policy as Code, GitOps gates) implemented."
⚡ 60-Second Elevator Pitch Talking Points
  • Own the mistake transparently without shifting blame to teammates or ambiguous tools.
  • Highlight immediate crisis composure: quickly diagnosing the break and restoring service within minutes.
  • Perform a deep systemic root cause analysis: look at CI/CD gaps, missing lifecycle policies, and lack of guardrails.
  • Demonstrate permanent platform impact: implement Policy as Code (OPA/Conftest) and GitOps controls so the entire organization is protected from that failure mode forever.
⛔ 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. Issuing immediate kill -9 (SIGKILL) commands rather than allowing graceful termination via kill -15 (SIGTERM) when configuring Describe Real Incident SIGKILL immediately halts execution without allowing processes to flush memory buffers, commit database transactions, or remove stale PID locks.
  2. Overlooking file system inode exhaustion (df -i) when diagnosing 'No space left on device' errors when configuring Describe Real Incident Millions of small files or unrotated session tokens can exhaust available file system inodes even when standard disk storage (df -h) shows ample free space.
  3. Exhausting open file descriptor allocations (ulimit -n) under intensive concurrent socket connections when configuring Describe Real Incident Reaching file descriptor exhaustion throws 'Too many open files' errors, preventing services from accepting new TCP client socket connections.
  4. Permitting defunct zombie processes to accumulate without fixing parent process SIGCHLD waitpid reaping when configuring Describe Real Incident Zombie processes consume process table entries; accumulating zombies can exhaust the system maximum PID limit (pid_max).
Advertisement
Want more Linux & SRE scenarios?
Explore our complete collection of scenario-based Linux & SRE interview runbooks.
Browse All Linux & SRE Questions →