⚡ ~/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 36 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 #33 (L3) · General DevOps — Scenario-Based Interview Questions

Q: Your auto-scaling group scales out based purely on CPU utilization crossing 80%. An intensive marketing email blast goes out at exactly 9:00 AM, causing traffic to spike 10x instantly. The servers crash before new instances can boot. How do you handle this?

Threshold-based CPU scaling is Reactive. By the time CPU hits 80%, the application is already stressed.

#General DevOps #L3 #DevOps #SRE #Architecture
🎙️ Candidate Opening & Architectural Context
""In our engineering organization, DevOps culture meant aligning developer speed with site reliability. The interviewer is testing: Reactive vs Proactive scaling, predictive scaling, scheduled actions.. 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: "In our engineering organization, DevOps culture meant aligning developer speed with site reliability. The interviewer is testing: Reactive vs Proactive scaling, predictive scaling, scheduled actions.. I structure my answer around systematic triage first, root cause analysis second, and permanent remediation third."

1️⃣

Initial Diagnostics & Root Cause Analysis

Threshold-based CPU scaling is Reactive. By the time CPU hits 80%, the application is already stressed. Booting EC2 instances takes minutes—by the time they are ready, the initial servers have already collapsed under the instant 10x spike.

  • Scheduled Scaling: Apply an ASG Scheduled Action to artificially inflate the minimum capacity from 2 to 20 instances at 8:45 AM, giving them 15 minutes to comfortably boot and register before the 9:00 AM blast.
  • Predictive Scaling: Use AWS Predictive Scaling, which uses Machine Learning to analyze historical daily/weekly traffic patterns and pre-warms capacity automatically before anticipated spikes occur.
2️⃣

Remediation & Permanent Safeguards

To handle known traffic spikes, you must use Proactive Scaling:

💡 The Senior SRE Gold Nugget (Key Architectural Takeaway)
"Pro-Tip: Scheduled Scaling: Apply an ASG Scheduled Action to artificially inflate the minimum capacity from 2 to 20 instances at 8:45 AM, g."
⚡ 60-Second Elevator Pitch Talking Points
  • Scheduled Scaling: Apply an ASG Scheduled Action to artificially inflate the minimum capacity fro...
  • Predictive Scaling: Use AWS Predictive Scaling, which uses Machine Learning to analyze historical...
⛔ 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 auto scaling 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 auto scaling 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 auto scaling 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 auto scaling 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 →