You are loading data from an external stage into a Snowflake table. Some of the rows in the data files contain invalid characters that cause the load operation to fail. You want to configure the 'COPY

Question

Exhibit

Options

• AOption A
• BOption B
• COption C
• DOption D
• EOption E

• A
  6% (3)
• B
  19% (9)
• C
  13% (6)
• D
  60% (29)
• E
  2% (1)

Explanation

The question tests knowledge of Snowflake's ON_ERROR parameter in the COPY INTO command. Option D is correct because setting ON_ERROR = 'CONTINUE' instructs Snowflake to skip individual invalid rows and continue loading all remaining valid rows, which is exactly the behavior described - partial success instead of an all-or-nothing load.

The distractors represent less suitable ON_ERROR values: ABORT_STATEMENT (the default) halts the entire load on the first error, loading nothing; SKIP_FILE abandons the entire file containing the bad row rather than just skipping the offending row; SKIP_FILE_<num> and SKIP_FILE_<num>% variants skip whole files once an error threshold is crossed, still discarding valid rows in flagged files. None of these achieve row-level granularity.

Memory tip: Think of the options on a spectrum from "strictest" to "most permissive" - ABORT_STATEMENT → SKIP_FILE → CONTINUE. The question asks to keep loading valid data row-by-row, so you want the most permissive end of the spectrum: CONTINUE.

No community discussion yet for this question.