DEA-C02 Data Movement Practice Question

Answer analysis

Option-by-option breakdown

For each option: why learners choose it and why it is or isn't the right answer here.

• ✗

  Create a pipe with AUTO_INGEST = TRUE and rely on Snowflake's internal polling mechanism to detect new files.

  Why it's wrong here

  Snowpipe does not use internal polling for AUTO_INGEST; it relies on cloud event notifications. Without a notification integration, Snowpipe will not automatically detect new files. The engineer must configure the notification integration (e.g., Pub/Sub for GCS) to push events to Snowflake. Relying on internal polling is not a supported feature and would not provide automatic ingestion.

• ✗

  Create a pipe with AUTO_INGEST = TRUE and configure the stage to use a storage integration with Google Cloud Storage.

  Why it's wrong here

  A storage integration allows Snowflake to access the Google Cloud Storage bucket securely, but it does not provide event notifications. AUTO_INGEST = TRUE requires a notification integration to receive events from the cloud provider. Without the notification integration, the pipe will not be triggered automatically. Therefore, this configuration alone does not enable automatic ingestion.

• ✗

  Create a pipe with AUTO_INGEST = FALSE and schedule it to run every minute using a task.

  Why it's wrong here

  AUTO_INGEST = FALSE means the pipe must be manually refreshed or triggered by a task. Scheduling a task every minute introduces latency and consumes compute resources even when no new files are present. While it can work, it is not the most efficient or low-latency solution. The requirement to load files as soon as they are available is best met with event-driven ingestion, not polling.

• ✓

  Create a pipe with AUTO_INGEST = TRUE and configure a cloud notification integration for Google Cloud Pub/Sub.

  Why this is correct

  AUTO_INGEST = TRUE enables Snowpipe to automatically ingest new files as they arrive in the external stage, based on event notifications from the cloud provider. For Google Cloud Storage, you configure a notification integration that uses Google Cloud Pub/Sub to send event messages to Snowflake. This setup provides near-real-time ingestion with minimal latency and no manual intervention, making it the correct choice.