Question 510
A Snowflake administrator investigates the following production situation: A bulk COPY INTO job inserts shifted columns from a pipe-delimited file because the configured format expects commas. What should the team change first?
Explanation
Correct Answer
The root issue is that the declared file format does not match the delimiter and record structure of the incoming files. The selected fix targets that condition: Set the correct FILE_FORMAT options and validate a sample before loading the batch. Validate it by checking this outcome: The loaded columns align with their source fields across representative records.
Incorrect Answers
This action targets internal stage file loading, where the source files have not been uploaded to an accessible Snowflake stage. In the given incident, the decisive issue is instead that the declared file format does not match the delimiter and record structure of the incoming files.
This action targets bulk load warehouse selection, where the chosen virtual warehouse is not sized for the batch load's resource needs. The corrective response here is “Set the correct FILE_FORMAT options and validate a sample before loading the batch”; this alternative does not provide that response.
This action targets copy on_error policy, where the ingest policy tolerates bad records without a compensating audit or remediation process. The stem reports a bulk COPY INTO job inserts shifted columns from a pipe-delimited file because the configured format expects commas; this control addresses a different failure condition.