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

Q: The system is experiencing unexplained network latency. `ping` times internally jump from 1ms to 200ms periodically. How do you isolate the problem?

Intermittent high latency is tricky. My workflow would be:

#Linux #L3 #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: Advanced network troubleshooting, packet capture, kernel networking stack.. 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: Advanced network troubleshooting, packet capture, kernel networking stack.. I structure my answer around systematic triage first, root cause analysis second, and permanent remediation third."

1️⃣

Initial Diagnostics & Root Cause Analysis

Intermittent high latency is tricky. My workflow would be:

  • Scope: Is it affecting all instances? One AZ? One specific app? I'd ping the default gateway and another instance in the same subnet to isolate whether it's the host network stack or the physical network/hypervisor.
  • Host metrics: Check dmesg or journalctl for NIC errors, ring buffer drops, or nf_conntrack table full messages.
  • Traffic Analysis: Use mtr to track packet loss at hops. To capture the issue, I'd run tcpdump -i eth0 -w capture.pcap during the latency spikes.
2️⃣

Remediation & Permanent Safeguards

Based on the finding, I might tune ring buffers (ethtool -G), adjust sysctl buffers, or escalate to the cloud provider if the host metrics check out perfectly.

  • Kernel Drops: Use netstat -su to see if UDP/TCP packets are being dropped by the kernel due to full receive buffers. I'd verify top to check if a specific CPU core handling NIC interrupts (ksoftirqd) is pinned at 100%, causing a processing bottleneck.
💡 The Senior SRE Gold Nugget (Key Architectural Takeaway)
"Pro-Tip: Scope: Is it affecting all instances? One AZ? One specific app? I'd ping the default gateway and another instance in the same subn."
⚡ 60-Second Elevator Pitch Talking Points
  • Scope: Is it affecting all instances? One AZ? One specific app? I'd ping the default gateway and ...
  • Host metrics: Check dmesg or journalctl for NIC errors, ring buffer drops, or nf_conntrack table ...
  • Traffic Analysis: Use mtr to track packet loss at hops. To capture the issue, I'd run tcpdump -i ...
⛔ 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 system experiencing unexplained 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 system experiencing unexplained 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 system experiencing unexplained 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 system experiencing unexplained 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 →