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

Q: What is the difference between Kinesis Data Streams and SQS?

Kinesis: ordered stream, multiple consumers can read same data, data retained 24h-365 days, good for analytics and fan-out.

#AWS #Cost & Architecture #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? 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 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️⃣

Production Solution & Architecture

Kinesis: ordered stream, multiple consumers can read same data, data retained 24h-365 days, good for analytics and fan-out. SQS: queue, message deleted after consumed, at-least-once delivery, simpler programming model, good for decoupling services. Use Kinesis for streaming analytics, SQS for task queues.

💡 The Senior SRE Gold Nugget (Key Architectural Takeaway)
"Pro-Tip: Kinesis: ordered stream, multiple consumers can read same data, data retained 24h-365 days, good for analytics and fan-out. SQS: q."
⚡ 60-Second Elevator Pitch Talking Points
  • Immediate Triage: Kinesis: ordered stream, multiple consumers can read same data, data retained 24h-365 days, goo
  • 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. Subscribing an Amazon SQS queue to an SNS topic without attaching an explicit queue access policy when configuring difference Kinesis Data SNS lacks permission to write to SQS by default; without an IAM resource policy granting sqs:SendMessage to the topic ARN, messages drop silently.
  2. Confusing standard SQS queues with FIFO queues regarding strict ordering and deduplication when configuring difference Kinesis Data Standard SQS provides at-least-once delivery with best-effort ordering; strict FIFO ordering requires MessageGroupId and deduplication IDs.
  3. Using short polling instead of SQS long polling (WaitTimeSeconds: 20) in high-volume consumers when configuring difference Kinesis Data Short polling queries single partition subsets and returns empty responses, dramatically inflating AWS API billing and consumer CPU usage.
  4. Failing to monitor ApproximateNumberOfMessagesVisible and ApproximateAgeOfOldestMessage in CloudWatch when configuring difference Kinesis Data Queue depth and message age are primary SLI signals for consumer backlog saturation, far superior to consumer CPU utilization.
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 →