Reviewed by Aditya Kumar Ā· Last reviewed 2026-03-24
Why this stack: Each service has a roleāingestion, storage, compute, serving. Architectural logic: S3 (lake); EMR/Glue (Spark); Lambda (event-driven); Kinesis (streaming); DMS (CDC); Redshift (warehouse); Athena (serverless SQL); MWAA (Airflow); Glue Catalog (metadata); IAM/KMS...
Red Flag: Listing services without understanding roles. Pro-Move: 'S3 + Glue for serverless; EMR when we need fine-grained Spark tuningācost vs. control trade-off.'
Why this stack: Each service has a roleāingestion, storage, compute, serving. Architectural logic: S3 (lake); EMR/Glue (Spark); Lambda (event-driven); Kinesis (streaming); DMS (CDC); Redshift (warehouse); Athena (serverless SQL); MWAA (Airflow); Glue Catalog (metadata); IAM/KMS (security); CloudWatch (monitoring). Trade-offs: Glue vs. EMRāGlue serverless, EMR more control. Athena vs. RedshiftāAthena pay per query; Redshift for interactive. Cost: S3 cheap; compute (EMR, Glue) scales with usage; Redshift reserved for predictable load.
Red Flag: Listing services without understanding roles. Pro-Move: 'S3 + Glue for serverless; EMR when we need fine-grained Spark tuningācost vs. control trade-off.'
According to DataEngPrep.tech, this is one of the most frequently asked Cloud/Tools interview questions, reported at 1 company. DataEngPrep.tech maintains an editor-reviewed database of 1,863 data engineering interview questions across 7 categories.