Snowpipe for event-driven loading in Snowflake - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to create a Snowpipe that loads data automatically from a stage.

Snowflake

CREATE PIPE my_pipe AUTO_INGEST = [1] AS COPY INTO my_table FROM @my_stage;

Drag options to blanks, or click blank then click option'

AFALSE

BON

CTRUE

DOFF

Attempts:

3 left

💡 Hint

Common Mistakes

Using FALSE disables automatic loading.

Using ON or OFF are invalid values for AUTO_INGEST.

Setting AUTO_INGEST to TRUE enables event-driven loading with Snowpipe.

2fill in blank

medium

Complete the code to create a notification integration for Snowpipe event notifications.

Snowflake

CREATE NOTIFICATION INTEGRATION my_integration TYPE = [1] ENABLED = TRUE;

Drag options to blanks, or click blank then click option'

AQUEUE

BAWS_SNS

CGCP_PUBSUB

DAWS_SQS

Attempts:

3 left

💡 Hint

Common Mistakes

Using AWS_SQS or AWS_SNS instead of QUEUE.

Using unsupported types like GCP_PUBSUB.

TYPE = QUEUE is used for notification integrations with Snowpipe on AWS SQS.

3fill in blank

hard

Fix the error in the COPY statement to load data from the stage correctly.

Snowflake

COPY INTO my_table FROM @my_stage FILE_FORMAT = (TYPE = [1]);

Drag options to blanks, or click blank then click option'

ACSV

BJSON

CPARQUET

DTXT

Attempts:

3 left

💡 Hint

Common Mistakes

Using TXT which is not a recognized file format type.

Using JSON or PARQUET if the files are CSV.

CSV is a valid file format type for Snowflake COPY INTO commands.

4fill in blank

hard

Fill both blanks to configure Snowpipe to listen to the correct cloud storage bucket and notification integration.

Snowflake

ALTER PIPE my_pipe SET (NOTIFICATION_CHANNEL = '[1]', NOTIFICATION_INTEGRATION = [2]);

Drag options to blanks, or click blank then click option'

Aarn:aws:sqs:us-west-2:123456789012:my-queue

Bmy_integration

Carn:aws:sns:us-west-2:123456789012:my-topic

Ddefault_integration

Attempts:

3 left

💡 Hint

Common Mistakes

Using SNS ARN instead of SQS ARN for notification channel.

Using default or wrong integration names.

The NOTIFICATION_CHANNEL must be the ARN of the SQS queue, and NOTIFICATION_INTEGRATION must be the integration name.

5fill in blank

hard

Fill all three blanks to create a stage, pipe, and grant usage for Snowpipe event-driven loading.

Snowflake

CREATE STAGE my_stage URL='s3://my-bucket/data/' STORAGE_INTEGRATION=[1];
CREATE PIPE my_pipe AUTO_INGEST=TRUE AS COPY INTO my_table FROM @my_stage FILE_FORMAT = (TYPE=[2]);
GRANT USAGE ON INTEGRATION [3] TO ROLE my_role;

Drag options to blanks, or click blank then click option'

Amy_storage_integration

BCSV

Dmy_other_integration

Attempts:

3 left

💡 Hint

Common Mistakes

Using different integration names in stage and grant statements.

Using unsupported file format types.

The storage integration name must be consistent for the stage and grant statements, and CSV is the file format type.

Practice

1. What is the main purpose of Snowpipe in Snowflake?

easy

A. To manually run SQL queries on data

B. To automatically load data when new files arrive in cloud storage

C. To create visual dashboards from data

D. To backup Snowflake databases

Solution

1. Step 1: Understand Snowpipe's role

   Snowpipe is designed to automate data loading triggered by new files in cloud storage.

2. Step 2: Compare options

   Options A, C, and D describe other tasks not related to Snowpipe's automatic loading feature.

3. Final Answer:

   To automatically load data when new files arrive in cloud storage -> Option B

4. Quick Check:

   Snowpipe = automatic data loading [OK]

Hint: Snowpipe triggers loading automatically on new files [OK]

Common Mistakes:

• Confusing Snowpipe with manual query execution
• Thinking Snowpipe creates dashboards
• Assuming Snowpipe is for backups

2. Which Snowpipe option enables event-driven automatic loading?

easy

A. MANUAL_TRIGGER = TRUE

B. AUTO_LOAD = FALSE

C. AUTO_INGEST = TRUE

D. EVENT_NOTIFY = OFF

Solution

1. Step 1: Identify the correct Snowpipe setting

   The setting AUTO_INGEST = TRUE enables event-driven automatic loading in Snowpipe.

2. Step 2: Eliminate incorrect options

   Options A, B, and D either disable loading or do not exist as valid Snowpipe settings.

3. Final Answer:

   AUTO_INGEST = TRUE -> Option C

4. Quick Check:

   AUTO_INGEST = TRUE enables event-driven loading [OK]

Hint: AUTO_INGEST = TRUE turns on event-driven loading [OK]

Common Mistakes:

• Using AUTO_LOAD instead of AUTO_INGEST
• Confusing manual trigger with automatic
• Turning event notifications off

3. Given this Snowpipe command:

CREATE PIPE my_pipe AUTO_INGEST = TRUE AS
 COPY INTO my_table FROM @my_stage FILE_FORMAT = (TYPE = 'CSV');

What happens when a new CSV file is added to @my_stage?

medium

A. The file is automatically loaded into my_table

B. The file is ignored until manual load is triggered

C. An error occurs because AUTO_INGEST is not supported

D. The file is deleted from the stage

Solution

1. Step 1: Analyze the pipe creation

   The pipe is created with AUTO_INGEST = TRUE, meaning it listens for new files in the stage and loads them automatically.

2. Step 2: Understand the COPY INTO command

   The COPY INTO command loads data from the stage files into my_table using CSV format.

3. Final Answer:

   The file is automatically loaded into my_table -> Option A

4. Quick Check:

   New file + AUTO_INGEST = TRUE triggers load [OK]

Hint: AUTO_INGEST = TRUE pipes auto-load new files [OK]

Common Mistakes:

• Thinking manual load is needed
• Believing AUTO_INGEST is unsupported
• Assuming files get deleted automatically

4. You created a Snowpipe with AUTO_INGEST = TRUE but new files are not loading automatically. What is a likely cause?

medium

A. Cloud storage event notifications are not configured properly

B. The pipe was created without specifying a table

C. AUTO_INGEST must be set to FALSE for automatic loading

D. Snowpipe does not support CSV file formats

Solution

1. Step 1: Check event notification setup

   Snowpipe requires cloud storage event notifications to trigger automatic loading when AUTO_INGEST = TRUE.

2. Step 2: Review other options

   The pipe was created without specifying a table is invalid because pipe creation requires a target table. AUTO_INGEST must be set to FALSE for automatic loading is wrong since AUTO_INGEST = TRUE enables automatic loading. Snowpipe does not support CSV file formats is false; CSV is supported.

3. Final Answer:

   Cloud storage event notifications are not configured properly -> Option A

4. Quick Check:

   Missing event notifications block auto-load [OK]

Hint: Check cloud event notifications for AUTO_INGEST pipes [OK]

Common Mistakes:

• Setting AUTO_INGEST to FALSE expecting auto-load
• Ignoring cloud event notification setup
• Thinking CSV format is unsupported

5. You want to set up Snowpipe to load JSON files automatically into a table. Which sequence of steps is correct?

hard

A. Create a file format for CSV, create a pipe with AUTO_INGEST=TRUE, then upload JSON files

B. Create a pipe first, then create a stage and file format after uploading files

C. Upload files to the table directly, then create a pipe with AUTO_INGEST=FALSE

D. Create a file format for JSON, create a stage, create a pipe with AUTO_INGEST=TRUE, then upload files to the stage

Solution

1. Step 1: Prepare file format and stage

   Define a JSON file format and create a stage to hold files before loading.

2. Step 2: Create pipe with AUTO_INGEST=TRUE

   Create the pipe referencing the stage and file format, enabling automatic loading on new files.

3. Step 3: Upload JSON files to the stage

   Uploading files triggers Snowpipe to load data automatically into the target table.

4. Final Answer:

   Create a file format for JSON, create a stage, create a pipe with AUTO_INGEST=TRUE, then upload files to the stage -> Option D

5. Quick Check:

   File format + stage + pipe + upload = auto-load [OK]

Hint: Set file format and stage before pipe with AUTO_INGEST [OK]

Common Mistakes:

• Creating pipe before stage and file format
• Uploading files directly to table
• Using CSV format for JSON files