COF-C03 Data Loading, Unloading, and Connectivity Practice Question

Answer analysis

Option-by-option breakdown

For each option: why learners choose it and why it is or isn't the right answer here.

• ✗

  ON_ERROR = 'REPLACE'

  Why it's wrong here

  There is no ON_ERROR = 'REPLACE' option in Snowflake COPY INTO. The valid values are CONTINUE, SKIP_FILE, SKIP_FILE_<n>, ABORT_STATEMENT, and SKIP_FILE_<n>%. REPLACE is not a recognized parameter, so this option is invalid and would cause a syntax error if used.

• ✓

  ON_ERROR = 'SKIP_FILE'

  Why this is correct

  ON_ERROR = 'SKIP_FILE' instructs Snowflake to skip a file entirely if any error occurs while loading it, including malformed JSON. This prevents the entire COPY INTO operation from failing and allows other valid files to load. It matches the requirement to skip malformed files without aborting the load, making it the correct choice.

• ✗

  ON_ERROR = 'CONTINUE'

  Why it's wrong here

  ON_ERROR = 'CONTINUE' skips rows that fail to load but does not skip entire malformed files. For a file with invalid JSON syntax, the COPY command will still report an error and may not load any rows from that file. It is designed for row-level errors, not file-level parsing failures, so it does not meet the requirement.

• ✗

  ON_ERROR = 'ABORT_STATEMENT'

  Why it's wrong here

  ON_ERROR = 'ABORT_STATEMENT' is the default behavior and aborts the entire COPY statement if any error is encountered. This would cause the load to fail completely upon encountering a malformed JSON file, which is the opposite of what the engineer wants. It does not skip files and is therefore incorrect.