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

Q: You enabled AWS CloudTrail across your organization. However, when you search the logs to find out who uploaded a specific image `logo.png` into an S3 bucket, nothing appears. You only see bucket creation events. Where is the log?

By default, CloudTrail only records Management Events (Control Plane actions). These include creating infrastructure (CreateBucket, RunInstances, UpdateSecurityGroup).

#AWS #Cost & Architecture #L2 #Cloud #Infrastructure #S3
🎙️ Candidate Opening & Architectural Context
""AWS reliability requires differentiating between AWS control plane limits and host-level resource exhaustion. The interviewer is testing: Management Events vs Data Events.. 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? 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. The interviewer is testing: Management Events vs Data Events.. I structure my answer around systematic triage first, root cause analysis second, and permanent remediation third."

1️⃣

Production Solution & Architecture

By default, CloudTrail only records Management Events (Control Plane actions). These include creating infrastructure (CreateBucket, RunInstances, UpdateSecurityGroup). It natively ignores Data Events (Data Plane actions) like s3:GetObject, s3:PutObject, or dynamodb:PutItem because logging trillions of them would result in astronomical CloudTrail bills. To see the logo.png upload, you must explicitly edit the CloudTrail configuration and opt-in to paying to record Data Events specifically targeting that S3 bucket.

💡 The Senior SRE Gold Nugget (Key Architectural Takeaway)
"Pro-Tip: By default, CloudTrail only records Management Events (Control Plane actions). These include creating infrastructure (CreateBucket."
⚡ 60-Second Elevator Pitch Talking Points
  • Immediate Triage: By default, CloudTrail only records Management Events (Control Plane actions). These include cr
  • Run targeted verification commands before modifying configuration.
  • Automate permanent guardrails (CI check, alerts, IaC policy) to prevent recurrence.
⛔ 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. Relying on legacy bucket ACLs instead of modern S3 Block Public Access and IAM bucket policies when configuring enabled CloudTrail across AWS recommends disabling ACLs (Bucket Owner Enforced) in favor of centralized declarative bucket policies and account-level Block Public Access controls.
  2. Confusing SSE-S3 encryption with KMS customer-managed key (SSE-KMS) authorization policies when configuring enabled CloudTrail across Accessing SSE-KMS encrypted objects requires both s3:GetObject and kms:Decrypt permissions; neglecting KMS key policies causes silent 403 Forbidden errors.
  3. Using sequential timestamps or predictable prefixes for high-throughput S3 read and write keys when configuring enabled CloudTrail across Sequential key prefixes limit S3 horizontal partitioning; randomized hash prefixes distribute workloads across partitions to achieve 3,500 PUT and 5,500 GET requests/sec.
  4. Failing to audit S3 object delete markers when troubleshooting missing versioned objects when configuring enabled CloudTrail across Issuing a DELETE on a versioned bucket only adds a delete marker; engineers must retrieve previous versions or purge markers to restore data.
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 →