Question 230
During a Snowflake architecture review, the team finds: A pipe exists and reports healthy definition text, but newly uploaded files never enter its load history after a bucket notification change. Which validation result best demonstrates that the reported defect is resolved?
Explanation
Correct Answer
This verifies snowpipe missing notification because the storage event-to-pipe notification path is missing or misconfigured. The corresponding corrective action is: Inspect the event integration and notification queue, then repair the approved auto-ingest linkage. A green status for a different component would not independently establish this result.
Incorrect Answers
Automated event ingestion generally handles new notifications rather than all historical files by default. “Run a controlled historical load or supported pipe refresh mechanism for existing eligible files” would address that alternative cause, not the condition in this question: the storage event-to-pipe notification path is missing or misconfigured.
“Use supported Snowpipe Streaming ingestion with authorized client and delivery semantics” responds to this separate finding: file-based ingest introduces unnecessary staging and notification latency for direct row events. This question instead needs “Inspect the event integration and notification queue, then repair the approved auto-ingest linkage”, so the alternative does not meet the stated condition.
The ingestion design does not use a suitable Kafka-to-Snowflake streaming integration. “Configure the supported Snowflake Connector for Kafka and its streaming ingestion path” applies to that separate problem. The observed case is a pipe exists and reports healthy definition text, but newly uploaded files never enter its load history after a bucket notification change; choosing this alternative would address the wrong failure mode.