New column in source: impact on ETL—schema mismatch, pipeline failure if not handled. Solutions: schema evolution (add column with default), use schema-on-read (Spark, Parquet), dynamic schema detection, add column to target with default. Best: version schema, use flexible formats (Parquet), add columns as nullable initially, backfill if needed. **Why it matters**: Design choices compound at scale—wrong approach can cause 100× overhead....
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 Verizon. 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.