nerdexam
Snowflake

DEA-C02 · Question #76

A Data Engineer needs to obtain details about data loading history for tables in a specific database and schema. The tables were loaded using Snowpipe in the last 24 hours. How should the Engineer acc

The correct answer is B. Use the LOAD HISTORY view using the usage privilege on the database and schema, and any. Option B is correct because Snowflake's INFORMATION_SCHEMA.LOAD_HISTORY view is specifically designed to surface data loading history (including Snowpipe) at the database and schema level, and it only requires the USAGE privilege on that database and schema - the minimum necessar

Data Movement

Question

A Data Engineer needs to obtain details about data loading history for tables in a specific database and schema. The tables were loaded using Snowpipe in the last 24 hours. How should the Engineer accomplish these tasks?

Options

  • AUse the USAGE privilege on the database and schema to use the copy history view in the
  • BUse the LOAD HISTORY view using the usage privilege on the database and schema, and any
  • CUse the MONITOR privilege on the account and access the table details to use the copy history
  • DUSAGE

How the community answered

(57 responses)
  • A
    2% (1)
  • B
    93% (53)
  • C
    2% (1)
  • D
    4% (2)

Explanation

Option B is correct because Snowflake's INFORMATION_SCHEMA.LOAD_HISTORY view is specifically designed to surface data loading history (including Snowpipe) at the database and schema level, and it only requires the USAGE privilege on that database and schema - the minimum necessary access for this task.

Why the distractors are wrong:

  • Option A references the COPY_HISTORY view, which is a table function (not a view) and typically requires MONITOR privilege - not just USAGE - making it the wrong privilege pairing.
  • Option C requires MONITOR privilege at the account level, which is elevated and unnecessary when you only need history scoped to a specific database and schema; this violates the principle of least privilege.
  • Option D is incomplete - USAGE alone with no specified view or object is not a valid or actionable answer.

Memory tip: Think "Load → Least privilege → LOADHISTORY + USAGE." The LOAD_HISTORY view is the lowest-privilege path to loading history scoped to a database/schema, while COPY_HISTORY (the table function) requires more elevated MONITOR privilege and is better suited for account-wide queries.

Topics

#Data Loading History#Snowpipe Monitoring#Account Usage Views#Permissions

Community Discussion

No community discussion yet for this question.

Full DEA-C02 Practice