Handling duplicate or corrupted data in batch ETL involves multiple layers. First, implement idempotency—use MERGE/UPSERT or truncate-and-reload with deterministic keys. For duplicates, apply business rules: keep most recent (MAX(updated_at)), first occurrence, or aggregate. Use ROW_NUMBER() OVER (PARTITION BY composite_key ORDER BY timestamp DESC) and filter rn=1. For corrupted data, validate schemas at ingestion, reject bad records to a quarantine table, and alert....
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 Adidas. 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 SQL 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.