⚡ ~/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 100 of 135 in Linux & SRE
Senior DevOps / SRE [L2] Linux Linux / SRE — Scenario-Based Interview Questions Production Scenario [L2]
🎯 Target Role / Context: Linux Scenario #60 (L2) · Linux / SRE — Scenario-Based Interview Questions

Q: A server has two network interfaces but traffic to a specific subnet is going out the wrong interface. How do you diagnose and fix the routing?

Linux maintains a routing table that determines which interface handles traffic to each destination.

#Linux #L2 #SRE #Systems #Troubleshooting
🎙️ Candidate Opening & Architectural Context
""Never reboot a server blindly; always capture top process telemetry, lsof descriptors, and thread dumps first. The interviewer is testing: Linux routing table, ip route, policy-based routing.. 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: "Never reboot a server blindly; always capture top process telemetry, lsof descriptors, and thread dumps first. The interviewer is testing: Linux routing table, ip route, policy-based routing.. I structure my answer around systematic triage first, root cause analysis second, and permanent remediation third."

1️⃣

Initial Diagnostics & Root Cause Analysis

Linux maintains a routing table that determines which interface handles traffic to each destination.

  • View the routing table: ip route show displays all routes, including default gateway and subnet-specific routes.
  • Check which route applies: ip route get 10.20.30.40 shows exactly which interface and gateway will be used for a specific destination.
  • Add a specific route:
2️⃣

Remediation & Permanent Safeguards

Diagnosis: Fix: This forces all traffic to 10.20.0.0/16 through eth1 via gateway 192.168.1.1. For complex multi-homed setups, Linux policy-based routing with ip rule allows routing decisions based on source IP, not just destination.

ip route add 10.20.0.0/16 via 192.168.1.1 dev eth1
  • Delete the incorrect route:
  • Persist the route: Add to /etc/sysconfig/network-scripts/route-eth1 (RHEL) or /etc/netplan/*.yaml (Ubuntu):
💡 The Senior SRE Gold Nugget (Key Architectural Takeaway)
"Pro-Tip: View the routing table: ip route show displays all routes, including default gateway and subnet-specific routes.."
⚡ 60-Second Elevator Pitch Talking Points
  • View the routing table: ip route show displays all routes, including default gateway and subnet-s...
  • Check which route applies: ip route get 10.20.30.40 shows exactly which interface and gateway wil...
  • Add a specific route:
⛔ 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 server network interfaces 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 server network interfaces 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 server network interfaces 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 server network interfaces 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 →