Reviewed by Aditya Kumar · Last reviewed 2026-03-25
**Why it matters**: At scale, design choices directly impact reliability, latency, and cost. Wrong decisions compound across jobs and teams. Kafka retry for corrupted messages: (1) Dead-letter topic—send failed messages to DLQ for inspection. (2) Retry with backoff—catch...
This hard-level Spark/Big Data question appears frequently in data engineering interviews at companies like Dunnhumby. While less common, it tests deeper understanding that distinguishes strong candidates. Mastering the underlying concepts (optimization, partition) will help you answer variations of this question confidently.
This is a senior-level question that tests architectural thinking. Lead with the high-level design, then drill into specifics. Discuss trade-offs explicitly - there is rarely one correct answer. Show awareness of scale, fault tolerance, and operational complexity.
Why it matters: At scale, design choices directly impact reliability, latency, and cost. Wrong decisions compound across jobs and teams.
Kafka retry for corrupted messages: (1) Dead-letter topic—send failed messages to DLQ for inspection. (2) Retry with backoff—catch exception, sleep, retry N times. (3) Skip and log—commit offset, log for later. (4) Use enable.auto.commit=false; commit only after successful process. (5) Idempotent consumer—handle duplicates. Config: max.poll.interval.ms, session.timeout.ms. Best practice: Don't block consumer; use DLQ; alert on DLQ depth; fix schema/corruption at source.
Scalability trade-offs: Partition/parallelism limits; single points of failure; horizontal vs vertical scaling. Cost implications: Sizing, spot vs reserved, optimization ROI.
Red Flag: Block consumer on retry. Pro-Move: 'DLQ; commit after process; alert depth.'
Some links below are affiliate links. If you buy through them we may earn a small commission at no extra cost to you — it helps keep DataEngPrep free.
According to DataEngPrep.tech, this is one of the most frequently asked Spark/Big Data interview questions, reported at 1 company. DataEngPrep.tech maintains an editor-reviewed database of 1,863 data engineering interview questions across 7 categories.