**Ingestion**: Kinesis (streaming), DMS (DB migration/CDC), Transfer Family (SFTP), API Gateway + Lambda (REST), EventBridge (events). **Processing**: Glue (managed Spark, ETL), EMR (complex Spark, ML), Lambda (lightweight). **Storage**: S3. **Analytics**: Athena (ad-hoc SQL), Redshift (warehouse). **Orchestration**: Step Functions, EventBridge. **Decision**: By latency (real-time vs batch) and volume. Real-time: Kinesis→Lambda→S3. Batch: Glue/EMR from S3....
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 Moonfare. 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.