Question 350
A Snowflake platform team receives the following requirement: A regulated billing load silently skips malformed source rows after ON_ERROR is set to CONTINUE without any rejection follow-up. What is the principal technical cause in this scenario?
Explanation
Correct Answer
The described symptoms indicate that the ingest policy tolerates bad records without a compensating audit or remediation process. The appropriate resolution is: Choose an approved ON_ERROR strategy and reconcile every rejected record against the source. Confirm with: The load report accounts for all source rows and exceptions are reviewed or corrected.
Incorrect Answers
The COPY transformation encounters invalid source data and its error handling is not investigated. “Use supported COPY validation or error reporting to locate the bad file and row, then correct the input” would address that alternative cause, not the condition in this question: the ingest policy tolerates bad records without a compensating audit or remediation process.
“Inspect load history and use an intentional approved reprocessing workflow only when necessary” responds to this separate finding: file-load metadata can prevent unchanged staged files from being loaded repeatedly. This question instead needs “Choose an approved ON_ERROR strategy and reconcile every rejected record against the source”, so the alternative does not meet the stated condition.
The external storage integration has not been configured for governed access. “Configure an authorized external stage with a scoped storage integration and permitted cloud trust” applies to that separate problem. The observed case is a regulated billing load silently skips malformed source rows after ON_ERROR is set to CONTINUE without any rejection follow-up; choosing this alternative would address the wrong failure mode.