**Architectural decision framework**: Choose by data volume, latency, complexity, and operational model. **Lambda**: Event-driven, <15 min, <10 GB memory, stateless. Use for: S3/Kinesis/EventBridge triggers, lightweight transforms (JSON reshape, validation), API backends, orchestration (Step Functions). Suits sub-GB data and sub-second to low-second latency. **Cost**: Pay per invocation + GB-second; at 1M invocations/month with 512 MB × 3 s, ~$20....
The complete answer continues with detailed implementation patterns, architectural trade-offs, and production-grade considerations. It covers performance optimization strategies, common pitfalls to avoid, and real-world examples from companies like Bitwise. The answer also includes follow-up discussion points that interviewers commonly explore.
Continue Reading the Full Answer
Unlock the complete expert answer with code examples, trade-offs, and pro tips - plus 1,863+ more.
Or upgrade to Platform Pro - $39
Engineers who used these answers got offers at
AmazonDatabricksSnowflakeGoogleMeta
According to DataEngPrep.tech, this is one of the most frequently asked Cloud/Tools interview questions, reported at 1 company. DataEngPrep.tech maintains a curated database of 1,863+ real data engineering interview questions across 7 categories, verified by industry professionals.