DEA-C02 · Question #83
How can a Data Engineer return all the errors encountered during a previous file upload that used the COPY command?
The correct answer is B. Call the table function. Calling the VALIDATE table function (SELECT FROM TABLE(VALIDATE(..., JOB_ID=>'<query_id>'))) is correct because Snowflake provides this built-in table function specifically to replay and surface all errors from a previously executed COPY INTO command, identified by its query…
Question
How can a Data Engineer return all the errors encountered during a previous file upload that used the COPY command?
Options
- AQuery the VALIDATE information schema view.
- BCall the table function.
- CCall the VALIDATE_PIPE_LOAD table function.
- DQuery the VALIDATE account usage schema view.
How the community answered
(47 responses)- A6% (3)
- B89% (42)
- C2% (1)
- D2% (1)
Explanation
Calling the VALIDATE table function (SELECT * FROM TABLE(VALIDATE(..., JOB_ID=>'<query_id>'))) is correct because Snowflake provides this built-in table function specifically to replay and surface all errors from a previously executed COPY INTO command, identified by its query ID. Option A is wrong because no "VALIDATE information schema view" exists in Snowflake - VALIDATE is a table function, not a view. Option C (VALIDATE_PIPE_LOAD) is wrong because that function is scoped to Snowpipe continuous ingestion loads, not manually executed COPY commands. Option D is wrong because there is no VALIDATE view in the ACCOUNT_USAGE schema either.
Memory tip: Think "COPY = manually called, so you manually CALL a table function to check it." Views are for ongoing schema introspection; the VALIDATE function is for on-demand, query-specific error inspection - and it requires the query ID of the specific COPY job you want to inspect.
Topics
Community Discussion
No community discussion yet for this question.