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.

• ✗

  A scheduled task using the EXECUTE TASK command.

  Why it's wrong here

  Tasks are designed for scheduled execution at specific intervals, not for event-driven real-time ingestion. Using a task would introduce latency equivalent to the interval duration, failing to meet the requirement of loading files 'as soon as' they appear in the cloud storage bucket for immediate processing.

• ✓

  Snowpipe using event-based notifications.

  Why this is correct

  Snowpipe is purpose-built for continuous, event-driven data loading. By integrating with cloud provider event notifications, it automatically detects new files and queues them for ingestion, providing near-real-time data availability for Snowflake users without requiring manual intervention or complex infrastructure monitoring to track file arrival times.

• ✗

  An external function that writes directly to the table.

  Why it's wrong here

  External functions are meant for executing code outside of Snowflake, not for standard bulk data ingestion. They lack the built-in management for file formats, error tracking, and automatic loading that Snowpipe provides, making them an incorrect and inefficient choice for standard data movement tasks into Snowflake tables.

• ✗

  A recurring COPY INTO command inside a stored procedure.

  Why it's wrong here

  While a stored procedure could be scheduled, it does not inherently monitor the storage bucket for new files. It would require complex logic to track which files have already been processed, resulting in an error-prone and resource-intensive design compared to the built-in, highly optimized Snowpipe ingestion framework.