What is 'schema drift' in ETL testing, and why is it a concern?
-
A
When ETL jobs run slower over time due to data volume growth
-
B
When source schema changes (added/removed columns) break the ETL pipeline unexpectedly
-
C
When the target warehouse schema is redesigned without reloading history
-
D
When data types change in the target but not the source