⚡ ~/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 AWS & Cloud Architecture Interview Questions Scenario 9 of 179 in AWS & Cloud Architecture
Senior DevOps / SRE [L2] AWS EC2 & Compute Production Scenario [L2]
🎯 Target Role / Context: AWS Scenario #2 (L2) · EC2 & Compute

Q: Your EC2 instance is showing high CPU and your application is slow. What steps do you take?

1. CloudWatch metrics — check CPU utilization over time. Is it sustained or spiky?

#AWS #EC2 & Compute #L2 #Cloud #Infrastructure #EC2
🎙️ Candidate Opening & Architectural Context
""When an interviewer asks how I troubleshoot this in AWS, I frame it through my hands-on production experience. When addressing this question, I walk the interviewer through our production incident runbook: isolating the blast radius, checking diagnostic logs and metrics, and applying a safe fix.""
Advertisement
⚡ Recommended Practice Lab

Want to master this scenario in a live sandbox? Stephane Maarek's AWS Certified DevOps Engineer Professional Masterclass on Udemy covers this exact problem with hands-on terminal drills.

🛠️ Production Runbook & Step-by-Step Resolution

Direct Answer: "When an interviewer asks how I troubleshoot this in AWS, I frame it through my hands-on production experience. When addressing this question, I walk the interviewer through our production incident runbook: isolating the blast radius, checking diagnostic logs and metrics, and applying a safe fix."

1️⃣

Initial Diagnostics & Root Cause Analysis

  • CloudWatch metrics — check CPU utilization over time. Is it sustained or spiky?
  • SSH in and check — top or htop to see which process is consuming CPU.
  • Check for runaway processes — a stuck process, an infinite loop, a cron job misfiring.
  • Check memory — sometimes high CPU is actually a memory issue causing constant swap. Check free -m and vmstat.
2️⃣

Remediation & Permanent Safeguards

Execute the resolution runbook and verify workload health:

  • Scale vertically — if it's a legitimate load, stop the instance, change instance type to a larger one, restart.
  • Scale horizontally — add it to an Auto Scaling Group, put a Load Balancer in front, scale out.
  • Right-sizing — use AWS Compute Optimizer recommendations.
💡 The Senior SRE Gold Nugget (Key Architectural Takeaway)
"Pro-Tip: CloudWatch metrics — check CPU utilization over time. Is it sustained or spiky?."
⚡ 60-Second Elevator Pitch Talking Points
  • CloudWatch metrics — check CPU utilization over time. Is it sustained or spiky?
  • SSH in and check — top or htop to see which process is consuming CPU.
  • Check for runaway processes — a stuck process, an infinite loop, a cron job misfiring.
⛔ 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. Purging compromised IAM user credentials immediately prior to querying CloudTrail forensic event logs when configuring instance showing high Deactivating a compromised key prevents abuse while preserving identity records for CloudTrail forensic queries to assess blast radius.
  2. Conflating local IAM Permissions Boundaries with organizational Service Control Policies (SCPs) when configuring instance showing high SCPs define maximum permission guards at the AWS Organization level across accounts, whereas permission boundaries limit delegate privileges within a single account.
  3. Deploying single-AZ cloud infrastructure for production workloads without multi-AZ failover resilience when configuring instance showing high Availability Zone hardware failures or localized network partitions cause complete service downtime when resources are not distributed across >=2 AZs.
  4. Jumping straight to SSH or instance restarts without reviewing CloudWatch metrics and AWS Systems Manager logs when configuring instance showing high Senior SREs triage control plane and hypervisor metrics via CloudWatch and SSM Session Manager before executing invasive host-level actions.
Advertisement
Want more AWS & Cloud Architecture scenarios?
Explore our complete collection of scenario-based AWS & Cloud Architecture interview runbooks.
Browse All AWS & Cloud Architecture Questions →