⚡ ~/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 13 of 135 in Linux & SRE
Staff SRE / Principal Architect [L3] General DevOps General DevOps — Scenario-Based Interview Questions Staff SRE Scenario [L3]
🎯 Target Role / Context: General DevOps Scenario #7 (L3) · General DevOps — Scenario-Based Interview Questions

Q: Your company’s primary region (`us-east-1`) completely goes offline (a major AWS outage affecting the whole region). You are tasked with deciding when to trigger the Disaster Recovery failover to `us-west-2`. What metrics/business factors dictate this decision?

A regional failover is the most destructive action an SRE can take; it risks massive data loss, split-brain scenarios, and hours of complex resolution. It should not be triggered lightly.

#General DevOps #L3 #DevOps #SRE #Architecture
🎙️ Candidate Opening & Architectural Context
""We faced this organizational and technical challenge while scaling our engineering teams. The interviewer is testing: RTO, RPO, split-brain, cost of failover vs cost of downtime.. I structure my answer around systematic triage first, root cause analysis second, and permanent remediation third.""
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: "We faced this organizational and technical challenge while scaling our engineering teams. The interviewer is testing: RTO, RPO, split-brain, cost of failover vs cost of downtime.. I structure my answer around systematic triage first, root cause analysis second, and permanent remediation third."

1️⃣

Initial Diagnostics & Root Cause Analysis

A regional failover is the most destructive action an SRE can take; it risks massive data loss, split-brain scenarios, and hours of complex resolution. It should not be triggered lightly.

  • Is the outage estimated to last longer than our business-defined RTO? (e.g., if RTO is 4 hours, and AWS says it's an hour fix, we wait. If AWS says ETA unknown, we fail over).
  • What is the state of the cross-region database replication? If the replication lag was 2 hours behind when the region died, failing over now guarantees 2 hours of permanent data loss (violating a strict 1-hour RPO).
  • We must ensure the us-east-1 environment is completely fenced off (DNS isolated) to prevent a "split-brain" where systems come back online and start writing conflicting data to the old primary database while the new us-west-2 primary is active.
2️⃣

Remediation & Permanent Safeguards

The decision is governed by RTO (Recovery Time Objective) and RPO (Recovery Point Objective):

💡 The Senior SRE Gold Nugget (Key Architectural Takeaway)
"Pro-Tip: Is the outage estimated to last longer than our business-defined RTO? (e.g., if RTO is 4 hours, and AWS says it's an hour fix, we ."
⚡ 60-Second Elevator Pitch Talking Points
  • Is the outage estimated to last longer than our business-defined RTO? (e.g., if RTO is 4 hours, a...
  • What is the state of the cross-region database replication? If the replication lag was 2 hours be...
  • We must ensure the us-east-1 environment is completely fenced off (DNS isolated) to prevent a "sp...
⛔ 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. Engineering bespoke in-house developer tools instead of adopting standardized platform Golden Paths when configuring General company’s primary Bespoke internal tools create long-term maintenance debt and fragmented workflows, whereas standardized Golden Paths accelerate delivery.
  2. Overlooking infrastructure cost visibility and FinOps allocation tagging across multi-tenant environments when configuring General company’s primary Without granular resource tagging, engineering organizations cannot attribute cloud infrastructure costs to specific teams or business units.
  3. Failing to define explicit Service Level Objectives (SLOs) and Error Budgets to balance feature velocity with reliability when configuring General company’s primary Without agreed SLOs, engineering and product teams lack an objective data-driven framework to prioritize technical debt over new features.
  4. Neglecting automated continuous drift detection between declarative configuration and deployed cloud state when configuring General company’s primary Unmanaged drift accumulates over time, causing future automated deployments to fail or overwrite emergency manual adjustments.
Advertisement
Want more Linux & SRE scenarios?
Explore our complete collection of scenario-based Linux & SRE interview runbooks.
Browse All Linux & SRE Questions →