What is a characteristic of event notifications in Snowpipe?

Question

Options

• AThe load history is stored In the metadata of the target table.
• BNotifications identify the cloud storage event and the actual data in the files.
• CSnowflake can process all older notifications when a paused pipe Is resumed.
• DWhen a pipe Is paused, event messages received for the pipe enter a limited retention period.

• A
  9% (4)
• B
  2% (1)
• C
  2% (1)
• D
  87% (39)

Explanation

When a Snowpipe pipe is paused, cloud storage event messages (e.g., from S3 SQS, Azure Event Grid, or GCS Pub/Sub) that arrive during the paused state enter a limited retention period - they are not queued indefinitely. If the pipe is not resumed before that retention window expires, those notifications and the corresponding file loads will be lost. Option A is incorrect: load history metadata stored in the target table is a characteristic of the standard COPY INTO command, not event-driven Snowpipe. Option B is incorrect: event notifications identify the file location (cloud storage path) but do not contain the actual data. Option C is incorrect: Snowflake cannot process all older notifications upon resume - only those still within the limited retention window.

No community discussion yet for this question.