COF-C03 Data Loading, Unloading, and Connectivity Practice Question
Exhibit
SELECT * FROM TABLE(INFORMATION_SCHEMA.COPY_HISTORY( TABLE_NAME => 'SALES_DATA', START_TIME => DATEADD(hours, -1, CURRENT_TIMESTAMP()) )); -- Result Row: -- FILE_NAME: sales_oct_01.csv, STATUS: PARTIALLY_LOADED, ROW_COUNT: 500, ROW_ERRORS: 2
Refer to the exhibit. A user executes a COPY INTO command and then queries the COPY_HISTORY. Based on the output shown, what most likely happened during the load and what is the current state of the data in the SALES_DATA table?
⚠ Common exam trap
Candidates often assume that any error during a load causes the entire transaction to rollback, failing to account for the ON_ERROR = 'CONTINUE' behavior.
Answer choices
Why each option matters
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Exactly 500 rows were successfully loaded into the table, and the 2 errors were ignored.
The COPY_HISTORY result showing 'PARTIALLY_LOADED' with specific row errors indicates that the ON_ERROR parameter was likely set to 'CONTINUE'. In this mode, Snowflake skips rows that contain errors but proceeds to load all valid records into the table. This results in a successful transaction for the 500 valid rows, while the 2 erroneous rows are logged but not ingested.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
The load failed completely, and no rows were added to the table because of the 2 errors.
Why it's wrong here
If the load had failed completely, the STATUS column would show 'LOAD_FAILED' or 'ABORTED', and the ROW_COUNT would be zero. Since the status is 'PARTIALLY_LOADED' and there is a positive ROW_COUNT, it confirms that the transaction was committed for the rows that did not encounter any parsing or data type errors.
- ✓
Exactly 500 rows were successfully loaded into the table, and the 2 errors were ignored.
Why this is correct
The 'PARTIALLY_LOADED' status is the key indicator that the 'ON_ERROR = CONTINUE' option was used. This tells Snowflake to load whatever it can. The ROW_COUNT of 500 represents the records that met the table's schema requirements and are now available for querying within the SALES_DATA table, while the errors are recorded for debugging.
- ✗
The 2 errors represent duplicate files that were already loaded in a previous session.
Why it's wrong here
Duplicate files are handled by Snowflake's load metadata and would typically result in the file being skipped entirely with a status like 'LOAD_SKIPPED' (if not forced). ROW_ERRORS specifically refers to issues within the content of the file itself, such as a string being too long for a column or a mismatch in the number of delimiters.
- ✗
The entire file was skipped because the number of errors exceeded the default threshold.
Why it's wrong here
If the file had been skipped, the ROW_COUNT would not be 500. A skipped file would result in zero rows being added to the target table for that specific file. The status 'PARTIALLY_LOADED' explicitly means that some data from that specific file was committed to the database despite the presence of some bad records.
About these practice questions
One of 280 original COF-C03 practice questions on Courseiva, each with a full explanation and wrong-answer analysis — not exam dumps or protected exam content. Learn why practice questions differ from exam dumps →
JA
Written and reviewed by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
Last reviewed September 2026 · checked against the official Snowflake exam blueprint
This COF-C03 practice question is part of Courseiva's free Snowflake certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the COF-C03 exam.