SnowPro Core (COF-C03) · Free practice question 11 of 15
Streams and tasks for change data capture
You want to capture row-level changes (inserts, updates, deletes) on a source table and process them in batches every five minutes using native Snowflake features. Which combination achieves this?
- A.A STREAM on the source table consumed by a TASK scheduled every 5 minutes.
- B.Snowpipe configured with a 5-minute throttle.
- C.A materialized view that refreshes on schedule.
- D.S3 event notifications triggering an external Lambda that writes back via JDBC.
Show answer and explanation
Correct answer: A. A STREAM on the source table consumed by a TASK scheduled every 5 minutes.
Why: Streams capture row-level CDC on a base table; Tasks run on a schedule and can consume from a Stream to process change batches. Snowpipe ingests new files into Snowflake — it is not a CDC mechanism. Materialized views maintain query results, not change feeds.
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
- Clustering keys for partition pruning
- Network policies for IP allowlisting
- Zero-copy cloning for QA environments
- Snowpipe auto-ingest for low latency