COF-C03 Data Loading, Unloading, and Connectivity 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.

• ✗

  Streams and tasks on the target table

  Why it's wrong here

  Streams capture change data on existing tables, and tasks orchestrate SQL execution, but neither detects new files in an external stage on its own. They operate on warehouse compute and require an upstream trigger. Without something that reacts to file arrivals, this combination cannot initiate a load when a Parquet file appears in Azure storage.

• ✗

  A scheduled task that runs COPY INTO every five minutes

  Why it's wrong here

  A task-based approach uses warehouse compute on a fixed schedule rather than reacting to file arrival, adding latency and cost. It does not automatically detect new files; it simply re-executes COPY, relying on load metadata to skip already-loaded files. The scenario explicitly rules out scheduled COPY execution, so this does not satisfy the stated requirement.

• ✗

  An external table with automatic refresh enabled

  Why it's wrong here

  External tables expose data in place for querying and can refresh metadata, but they do not load data into a native Snowflake table. The requirement is to load files into a table, not query them externally. Automatic refresh also depends on event notifications or a schedule, and it manages partitions rather than performing ingestion into a managed table.

• ✓

  Snowpipe with a cloud messaging notification integration

  Why this is correct

  Snowpipe combined with an event notification from the cloud provider triggers loads when new files land in the external stage, which matches the requirement for automatic, event-driven ingestion without polling. It also tracks loaded files in load metadata so duplicate loads are avoided. This is the documented mechanism for continuous loading from external cloud storage in Snowflake.