What metadata is maintained by Snowflake for every table during data loading when using the COPY INTO command? (Choose two.)

The correct answer is A. Number of rows parsed in the file D. Timestamp of the last load for the file. When Snowflake processes files using COPY INTO, it maintains a load history per table that tracks two key pieces of metadata: the number of rows parsed (A) and the timestamp of the last load (D). This allows Snowflake to prevent duplicate loads and provide auditing - you can quer

Data Movement

Question

Options

ANumber of rows parsed in the file
BNumber of columns parsed in the file
CDatatypes of the last load for the file
DTimestamp of the last load for the file
EName of each column in the file from which data was loaded

How the community answered

(34 responses)

A
91% (31)
C
6% (2)
E
3% (1)

Explanation

When Snowflake processes files using COPY INTO, it maintains a load history per table that tracks two key pieces of metadata: the number of rows parsed (A) and the timestamp of the last load (D). This allows Snowflake to prevent duplicate loads and provide auditing - you can query INFORMATION_SCHEMA.LOAD_HISTORY to see exactly this data.

The distractors are wrong because Snowflake's load metadata is row-oriented and time-oriented, not column-oriented: it does not track number of columns parsed (B), datatypes of loaded columns (C), or individual column names (E) - that structural information belongs to the table schema, not the load history.

Memory tip: Think "COPY INTO = Rows + Timestamp" - Snowflake cares about how much was loaded and when, not what shape the file had.

Topics

#Data Loading#COPY INTO#Metadata#Load History

Community Discussion

No community discussion yet for this question.

Full DEA-C02 Practice