⚡ ~/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 Observability & Monitoring Interview Questions Scenario 2 of 116 in Observability & Monitoring
Junior / Associate DevOps [L1] Observability Core Fundamentals [L1]
🎯 Target Role / Context: Observability Scenario #1 (L1) · Observability

Q: Your application latency has suddenly spiked but CPU, Memory, and Network I/O metrics remain normal. What do you check first?

If the application instance's local resources are fine, the latency is almost certainly caused by an external downstream dependency.

#Observability #L1 #Monitoring #Prometheus #SRE
🎙️ Candidate Opening & Architectural Context
""During a high-traffic production event, our observability stack proved essential in isolating this latency surge. The interviewer is testing: Understanding of external dependencies and basic troubleshooting workflow.. 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 Prometheus Certified Associate (PCA) & Monitoring Labs covers this exact problem with hands-on terminal drills.

🛠️ Production Runbook & Step-by-Step Resolution

Direct Answer: "During a high-traffic production event, our observability stack proved essential in isolating this latency surge. The interviewer is testing: Understanding of external dependencies and basic troubleshooting workflow.. I structure my answer around systematic triage first, root cause analysis second, and permanent remediation third."

1️⃣

Initial Diagnostics & Root Cause Analysis

If the application instance's local resources are fine, the latency is almost certainly caused by an external downstream dependency.

  • Database query latency (e.g., table locks, missing indexes).
  • Third-party API timeouts or throttling (e.g., Stripe, SendGrid).
  • Cache latency (e.g., Redis cluster eviction policies taking too long or connection exhaustion).
2️⃣

Remediation & Permanent Safeguards

I would check APM (Application Performance Monitoring) distributed traces or dependency metrics. I am looking for: If external telemetry indicates they are fast, the application might be experiencing thread pool exhaustion or garbage collection (GC) pauses internally, which APM thread/GC metrics would reveal despite low host CPU.

💡 The Senior SRE Gold Nugget (Key Architectural Takeaway)
"Pro-Tip: Database query latency (e.g., table locks, missing indexes).."
⚡ 60-Second Elevator Pitch Talking Points
  • Database query latency (e.g., table locks, missing indexes).
  • Third-party API timeouts or throttling (e.g., Stripe, SendGrid).
  • Cache latency (e.g., Redis cluster eviction policies taking too long or connection exhaustion).
⛔ 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. Injecting high-cardinality label dimensions (such as user IDs or request UUIDs) into Prometheus metrics when configuring Observability application latency High-cardinality label values cause exponential time-series growth, consuming gigabytes of TSDB memory and crashing Prometheus servers.
  2. Evaluating application performance solely through arithmetic mean or p50 latency while ignoring tail latency (p99) when configuring Observability application latency Averages hide catastrophic tail latency outages where 1% of high-value user transactions suffer severe timeouts.
  3. Failing to inject and extract W3C distributed trace context across message brokers and RPC calls when configuring Observability application latency Breaking distributed trace context propagation fragments end-to-end transaction waterfalls into disconnected, un-correlatable trace segments.
  4. Configuring alert rule evaluation intervals without sufficient duration damping (for: 5m), inducing alert flap when configuring Observability application latency Instant alerts triggered by transient sub-second CPU or latency blips page on-call engineers unnecessarily and dilute response urgency.
Advertisement
Want more Observability & Monitoring scenarios?
Explore our complete collection of scenario-based Observability & Monitoring interview runbooks.
Browse All Observability & Monitoring Questions →