**Roles**: (1) **Durable log**—events persisted; replayable. (2) **Decoupling**—producers and consumers independent. (3) **Buffer**—absorb spikes. (4) **Multiple consumers**—same stream, different use cases.
**In Pipelines**: Ingest (clicks, transactions) → Kafka → Spark/Flink process → sink (Delta, DB, dashboard). CDC from DB → Kafka → lake.
**Why Kafka**: Throughput (millions/sec), retention, exactly-once (with Transactions API).
**Scalability Trade-offs**: Partitions = parallelism....
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 BCG. 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 Spark/Big Data 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.