Sample question 1 — Data Transformations
An ingestion pipeline carries files from S3 into a table through a Snowpipe configured for auto-ingest. Twice this week a downstream dashboard lagged, and the on-call engineer could not tell whether files were piling up unread or whether each batch had loaded and simply taken longer to land. Which pairing of functions and views gives that operational picture?
- A. SYSTEM$PIPE_STATUS for the pending-file count and ACCOUNT_USAGE.COPY_HISTORY for completed loads.
- B. SHOW PIPES for the latest state and ACCOUNT_USAGE.PIPE_USAGE_HISTORY for the credits consumed.
- C. ALTER PIPE … SET COMMENT to record health and INFORMATION_SCHEMA.PIPES to read the comment back.
- D. VALIDATE_PIPE_LOAD to replay the pending files and SYSTEM$PIPE_FORCE_RESUME to rebuild pipe state.
Answer: A. Option A is correct because SYSTEM$PIPE_STATUS reports the pipe's current condition, including how many files are still waiting, while ACCOUNT_USAGE.COPY_HISTORY records each completed load and its timing; together they separate a growing queue from loads that merely ran slowly. Option B shows the pipe definition and consumption credits, neither of which reveals a waiting queue. Option C depends on a comment an operator would have to write by hand, so it reports nothing the platform measured. Option D re-validates a load rather than reporting live state, and forcing a resume does not describe the queue.
