Snowpipe for event-driven loading in Snowflake - Practice Problems & Coding Challenges

Challenge - 5 Problems

🧠 Conceptual

intermediate

How does Snowpipe detect new files for loading?

Snowpipe automates data loading into Snowflake. Which method does Snowpipe use to detect new files for loading?

A It requires manual triggering by the user for each file.

B It continuously polls the cloud storage location for new files.

C It uses a scheduled batch job to scan and load files every hour.

D It relies on event notifications from the cloud storage service.

💡 Hint

Think about how Snowpipe reacts instantly when new data arrives.

Snowpipe uses event notifications from cloud storage (like AWS S3 events) to detect new files and load them automatically. This event-driven approach avoids constant polling or manual triggers.

❓ Configuration

intermediate

Which Snowpipe configuration enables event-driven loading from AWS S3?

You want Snowpipe to load data automatically when new files arrive in an AWS S3 bucket. Which configuration step is required?

A Configure an S3 event notification to send messages to an SQS queue subscribed by Snowpipe.

B Set up an S3 event notification to send messages to an SNS topic subscribed by Snowpipe.

C Create an SQS queue and configure Snowpipe to poll it every 5 minutes.

D Manually upload files to Snowflake stage to trigger Snowpipe.

💡 Hint

Snowpipe listens to messages from a queue service for event-driven loading.

Snowpipe integrates with AWS S3 event notifications by configuring S3 to send events to an SQS queue. Snowpipe then subscribes to this queue to receive notifications and load data automatically.

❓ Architecture

advanced

What is the main benefit of using Snowpipe with event-driven loading over batch loading?

Compare Snowpipe event-driven loading with traditional batch loading. What is the primary advantage of event-driven loading?

A It reduces data latency by loading files immediately after arrival.

B It lowers storage costs by compressing files before loading.

C It allows manual control over when data is loaded.

D It batches multiple files to load only once per day.

💡 Hint

Think about how quickly data becomes available for queries.

Event-driven loading with Snowpipe reduces data latency by loading files as soon as they arrive, making data available faster than batch loading which waits for scheduled intervals.

❓ security

advanced

Which IAM permission is essential for Snowpipe to access files in an AWS S3 bucket for event-driven loading?

To enable Snowpipe to load data from an AWS S3 bucket using event notifications, which IAM permission must be granted?

A s3:DeleteObject to remove files after loading.

B s3:PutObject to upload files to the bucket.

C s3:GetObject to read files from the bucket.

D s3:ListBucket to list all buckets in the account.

💡 Hint

Snowpipe needs to read files to load data.

Snowpipe requires the s3:GetObject permission to read files from the S3 bucket for loading. Other permissions like PutObject or DeleteObject are not needed for loading.

❓ service_behavior

expert

What happens if Snowpipe receives duplicate event notifications for the same file?

Snowpipe is configured for event-driven loading. If it receives multiple event notifications for the same file, what is the expected behavior?

A Snowpipe loads the file multiple times, causing duplicate data.

B Snowpipe ignores duplicates and loads the file only once.

C Snowpipe raises an error and stops loading further files.

D Snowpipe deletes the file after the first load to prevent duplicates.

💡 Hint

Consider how Snowpipe ensures data consistency.

Snowpipe is designed to be idempotent. It tracks loaded files and ignores duplicate event notifications to prevent loading the same file multiple times.