Interview Question
Design an event-driven AWS pipeline that remains reliable when downstream processing slows down.
What a Strong Answer Should Cover
- Decoupling with a durable queue
- Retry and dead-letter strategy
- Idempotent consumers
- Metrics, alarms, and back-pressure
- Least-privilege IAM
Common Mistakes
- Jumping to a technology before clarifying the problem
- Explaining the solution without the reasoning or trade-offs
- Omitting verification, failure handling, or prevention
Interviewer Follow-ups
- What happens when downstream capacity is exhausted?
- How do you make processing safe to retry?
- How would you prove the design works under load?
What the interviewer is testing
- Requirements and constraints
- Architecture and trade-offs
- Reliability, security, cost, and operations
Real-World Sample Answer
A strong real-world response should connect requirements to engineering decisions, explain why the chosen approach fits the constraints, and make failure, security, cost, observability, and verification explicit.