⚡ ~/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 47 of 179 in AWS & Cloud Architecture
Staff SRE / Principal Architect [L3] AWS Cost & Architecture Staff SRE Scenario [L3]
🎯 Target Role / Context: AWS Scenario #45 (L3) · Cost & Architecture

Q: Your AWS bill doubled this month unexpectedly. How do you investigate?

1. AWS Cost Explorer — open it, filter by service. Which service increased?

#AWS #Cost & Architecture #L3 #Cloud #Infrastructure #EC2
🎙️ Candidate Opening & Architectural Context
""In our AWS cloud environment, we managed high-traffic microservices where this exact scenario occurred. 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: "In our AWS cloud environment, we managed high-traffic microservices where this exact scenario occurred. 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

  • AWS Cost Explorer — open it, filter by service. Which service increased?
  • Filter by time — compare this month vs last month. Find the day the cost jumped.
  • Cost and Usage Report (CUR) — most granular billing data. Query with Athena if needed.
  • Check for data transfer — inter-region, internet egress. A new service sending data outside AWS is expensive.
  • Check EC2 instances — a runaway Auto Scaling group could have spawned many instances.
2️⃣

Remediation & Permanent Safeguards

Execute the resolution runbook and verify workload health:

  • Check NAT Gateway — NAT Gateway charges per GB. A bug causing high-volume traffic through NAT is a common culprit.
  • Check CloudWatch — too many custom metrics or log ingestion.
  • Enable AWS Budgets — set alerts to catch this earlier next time.
  • Enable Cost Anomaly Detection — ML-based alerts for unusual spend patterns.
💡 The Senior SRE Gold Nugget (Key Architectural Takeaway)
"Pro-Tip: AWS Cost Explorer — open it, filter by service. Which service increased?."
⚡ 60-Second Elevator Pitch Talking Points
  • AWS Cost Explorer — open it, filter by service. Which service increased?
  • Filter by time — compare this month vs last month. Find the day the cost jumped.
  • Cost and Usage Report (CUR) — most granular billing data. Query with Athena if needed.
⛔ 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 bill doubled month 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 bill doubled month 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 bill doubled month 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 bill doubled month 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 →