SnowPro Core (COF-C03) · Free practice question 15 of 15
Snowpipe auto-ingest for low latency
A streaming source writes ~50 small files (about 5 MB each) per minute into an S3 bucket. You want to load them into Snowflake with the lowest end-to-end latency. Which approach is best?
- A.A scheduled TASK that runs `COPY INTO` every 5 minutes.
- B.Snowpipe with auto-ingest triggered by S3 event notifications.
- C.A Stream over an external table built on the S3 prefix.
- D.Manual `COPY INTO` commands issued by an analyst.
Show answer and explanation
Correct answer: B. Snowpipe with auto-ingest triggered by S3 event notifications.
Why: Snowpipe with auto-ingest is purpose-built for continuous file-based loading: S3 event notifications trigger ingestion within roughly a minute of file arrival. Scheduled `COPY INTO` has worse latency bounded by the schedule interval. Streams capture CDC on base tables, not external file arrivals.
More free SnowPro Core (COF-C03) questions
- Micro-partition immutability
- SECURITYADMIN for user and role management
- Multi-cluster warehouses for concurrency
- Snowflake edition for extended Time Travel
- Recovering a truncated table with Time Travel
- Types of internal stages
- File sizing for COPY INTO
- Query result cache
- Reader accounts for non-Snowflake consumers
- LATERAL FLATTEN on VARIANT arrays
- Streams and tasks for change data capture
- Clustering keys for partition pruning
- Network policies for IP allowlisting
- Zero-copy cloning for QA environments