COF-C03 Data Loading, Unloading, and Connectivity Practice Question
A data engineer is configuring a Snowpipe to automatically load data from an external stage (Google Cloud Storage) into a Snowflake table. The engineer wants to minimize latency between file arrival and data availability. Which configuration should the engineer use?
⚠ Common exam trap
The trap here is assuming that periodic polling or manual triggers can match the low latency of event-driven auto-ingest, when they inherently introduce delays and overhead.
Answer choices
Why each option matters
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Set up a cloud messaging service (e.g., Google Cloud Pub/Sub) to send event notifications to Snowflake, and create a pipe with AUTO_INGEST = TRUE.
To minimize latency, Snowpipe should be configured with AUTO_INGEST = TRUE, which leverages cloud messaging services to receive event notifications when new files arrive. This event-driven approach triggers immediate ingestion, ensuring data is loaded as soon as it lands in the external stage.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Configure the external stage to use a storage integration and set the pipe's file format to automatically detect new files via directory listing.
Why it's wrong here
Storage integrations are used for secure access to external stages, but they do not provide event notifications. The pipe does not automatically detect new files via directory listing; it requires either event notifications or manual invocation. This option confuses access configuration with ingestion triggering.
- ✓
Set up a cloud messaging service (e.g., Google Cloud Pub/Sub) to send event notifications to Snowflake, and create a pipe with AUTO_INGEST = TRUE.
Why this is correct
Snowpipe with AUTO_INGEST = TRUE uses cloud messaging to receive event notifications when new files arrive in the external stage. This triggers immediate ingestion, minimizing latency. For Google Cloud Storage, you configure Pub/Sub to send notifications to Snowflake, which then loads the files automatically.
- ✗
Create a pipe with AUTO_INGEST = FALSE and schedule a task to call the pipe every minute using SYSTEM$PIPE_FORCE_REFRESH.
Why it's wrong here
AUTO_INGEST = FALSE means the pipe does not listen for event notifications. Using a scheduled task to force refresh introduces up to a minute of latency and unnecessary overhead. This approach is not event-driven and is less efficient than auto-ingest, especially when minimizing latency is critical.
- ✗
Use the Snowpipe REST API to call insertFiles every 30 seconds from an external scheduler to check for new files.
Why it's wrong here
Polling with the REST API every 30 seconds introduces latency and requires an external scheduler. It is less efficient than event-driven auto-ingest and can lead to missed files if the polling interval is too long. The REST API is typically used for manual or programmatic triggers, not for continuous low-latency ingestion.
About these practice questions
Courseiva writes every COF-C03 question from scratch — 280 in total, each with an explanation and a wrong-answer breakdown. None are copied from real exams or dumps. Learn why practice questions differ from exam dumps →
JA
Written and reviewed by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
Last reviewed September 2026 · checked against the official Snowflake exam blueprint
This COF-C03 practice question is part of Courseiva's free Snowflake certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the COF-C03 exam.