Multiple ChoiceIntermediate 45s
ETL vs ELT for schema drift
Source schemas change often with new optional columns. Which approach best absorbs schema drift with least rework?
Options
- 1A strict ETL layer that fails the pipeline whenever it encounters any new column
- 2Manual schema edits performed by hand in every pipeline for each upstream change
- 3ELT loading raw semi-structured data first, then modeling downstream with schema-on-read
- 4Disabling schema evolution entirely so upstream changes are rejected at ingest
Think you can answer under pressure?
Get matched and answer live questions in 3-minute 1v1 battles. Elo ranking, badge tiers and bragging rights on the line.