⚡ ~/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 Databases & Storage Interview Questions Scenario 1 of 54 in Databases & Storage
Senior DevOps / SRE [L2] Database RDS & Databases Production Scenario [L2]

Q: Your RDS instance is using 100% CPU. What do you do?

1. Identify the culprit — use RDS Performance Insights to find the top SQL queries consuming CPU.

#AWS #RDS & Databases #L2 #Cloud #Infrastructure
🎙️ Candidate Opening & Architectural Context
""In a previous role, our monitoring paged me for a similar incident across our AWS VPC infrastructure. 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? KodeKloud's PostgreSQL Database Administration & High Availability Course covers this exact problem with hands-on terminal drills.

🛠️ Production Runbook & Step-by-Step Resolution

Direct Answer: "In a previous role, our monitoring paged me for a similar incident across our AWS VPC infrastructure. 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

  • Identify the culprit — use RDS Performance Insights to find the top SQL queries consuming CPU.
  • Look for slow queries — enable slow query log. Check for missing indexes.
  • Check for lock contention — queries waiting for locks show high CPU wait.
  • Scale vertically — stop the RDS instance, change instance class to a larger one (more CPU), restart.
2️⃣

Remediation & Permanent Safeguards

Execute the resolution runbook and verify workload health:

  • Read replicas — offload read queries to a read replica. Add a read replica and point your app's read traffic there.
  • Query optimization — add indexes for slow queries found in Performance Insights.
  • Connection pool — if too many connections are opening/closing rapidly, it causes CPU overhead. Use RDS Proxy.
💡 The Senior SRE Gold Nugget (Key Architectural Takeaway)
"Pro-Tip: Identify the culprit — use RDS Performance Insights to find the top SQL queries consuming CPU.."
⚡ 60-Second Elevator Pitch Talking Points
  • Identify the culprit — use RDS Performance Insights to find the top SQL queries consuming CPU.
  • Look for slow queries — enable slow query log. Check for missing indexes.
  • Check for lock contention — queries waiting for locks show high CPU wait.
⛔ 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. Applying exclusive-lock DDL table migrations on live production databases during peak traffic windows when configuring instance using 100% DDL migrations that acquire an exclusive table lock block all concurrent queries, queuing connections until the database connection pool exhausts.
  2. Allowing high-frequency queries to trigger full table scans without appropriate composite indexing when configuring instance using 100% Sequential table scans saturate database CPU and disk I/O, evicting frequently queried data from the buffer cache and causing cascading timeouts.
  3. Disabling referential integrity constraints during bulk ETL imports without post-import consistency validation when configuring instance using 100% Skipping relational consistency checks risks introducing orphaned records and referential integrity violations into production tables.
  4. Relying on database snapshot backups that have never been verified through automated restoration drills when configuring instance using 100% Backups that have never been tested with automated restore verification frequently fail during real disaster recovery scenarios.
Advertisement
Want more Databases & Storage scenarios?
Explore our complete collection of scenario-based Databases & Storage interview runbooks.
Browse All Databases & Storage Questions →