⚡ ~/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 42 of 179 in AWS & Cloud Architecture
Senior DevOps / SRE [L2] AWS Monitoring & CloudWatch Production Scenario [L2]
🎯 Target Role / Context: AWS Scenario #40 (L2) · Monitoring & CloudWatch

Q: What is AWS CloudTrail and how is it different from CloudWatch?

CloudTrail — records API calls made to AWS. Who did what, when, from where. "Audit trail." Example: who deleted that S3 bucket? Who changed that Security Group?

#AWS #Monitoring & CloudWatch #L2 #Cloud #Infrastructure #EC2
🎙️ Candidate Opening & Architectural Context
""AWS reliability requires differentiating between AWS control plane limits and host-level resource exhaustion. 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: "AWS reliability requires differentiating between AWS control plane limits and host-level resource exhaustion. 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

CloudTrail logs: Bob assumed the role AdminRole at 3:47 PM and called ec2:TerminateInstances on i-123456.

  • CloudTrail — records API calls made to AWS. Who did what, when, from where. "Audit trail." Example: who deleted that S3 bucket? Who changed that Security Group?
  • CloudWatch — operational monitoring. Metrics, logs, alarms. How is the system performing right now?
2️⃣

Remediation & Permanent Safeguards

CloudWatch logs: App server error rate is 5.2% for the last 10 minutes. Use CloudTrail for: security investigations, compliance auditing, change tracking. Enable in all regions. Store logs in S3 with immutable retention (S3 Object Lock) for compliance.

💡 The Senior SRE Gold Nugget (Key Architectural Takeaway)
"Pro-Tip: CloudTrail — records API calls made to AWS. Who did what, when, from where. "Audit trail." Example: who deleted that S3 bucket? Wh."
⚡ 60-Second Elevator Pitch Talking Points
  • CloudTrail — records API calls made to AWS. Who did what, when, from where. "Audit trail." Exampl...
  • CloudWatch — operational monitoring. Metrics, logs, alarms. How is the system performing right now?
⛔ 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 CloudTrail different CloudWatch 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 CloudTrail different CloudWatch 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 CloudTrail different CloudWatch 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 CloudTrail different CloudWatch 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 →