Question 360
For a university data platform, this issue must not recur: An operations analyst assumes COPY INTO will map reordered source columns correctly solely because target columns have matching names. Which review control fits best?
Explanation
Correct Answer
Test schema drift and reordered source files before each upstream release. This reduces recurrence of: Positional and name-based column mapping are distinct file-load behaviors. The verification should demonstrate: A deliberately reordered input sample lands values in the correct target columns.
Incorrect Answers
Review FORCE and PURGE options during production code changes. That safeguard is aimed at ANOTHER risk: A monthly COPY INTO command reloads yesterday's same file after an operator adds FORCE=TRUE to every run. It is less targeted than the control for: Positional and name-based column mapping are distinct file-load behaviors.
Use sample files with quoted delimiters and escaped values in ingestion acceptance tests. That safeguard is aimed at ANOTHER risk: A bulk load of customer CSV records splits addresses into wrong columns because the delimiter differs from the source contract. It is less targeted than the control for: Positional and name-based column mapping are distinct file-load behaviors.
Test notification delivery after cloud policy and storage routing changes. That safeguard is aimed at ANOTHER risk: A storage bucket sends events but a Snowpipe pipe never loads new objects because its notification integration is unconfigured. It is less targeted than the control for: Positional and name-based column mapping are distinct file-load behaviors.