QuestionQ17

Data Ingestion and Data Preparation

Files arrive in an external stage every 10 seconds from a proprietary system. The files range in size from 500 K to 3 MB. The data must be available to dashboards as soon as it arrives.

How can a Snowflake Architect satisfy this requirement with the LEAST amount of coding?

Choose two
Explanation

Files land every 10 seconds and must be visible almost immediately with minimal coding. A task has a minimum schedule interval of 60 seconds, so any COPY-plus-task or task-plus-stream approach (B, E) cannot meet the 10-second latency. Snowpipe with auto-ingest (A) uses cloud event notifications to load files continuously as they arrive with essentially no custom code, and a materialized view on an external table (C) exposes the staged data to dashboards and auto-refreshes as new files appear — both low-code, near-real-time. A one-off COPY INTO (D) is manual and not continuous. Therefore A and C.

Learn more

Community Discussion

No comments yet. Be the first to start the discussion!