Snowpipe for continuous loading in Snowflake - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

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

Snowflake

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

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

ATRUE

BFALSE

CON

DOFF

Attempts:

3 left

💡 Hint

Common Mistakes

Using FALSE disables continuous loading.

Using ON or OFF are invalid values for AUTO_INGEST.

Setting AUTO_INGEST = TRUE enables Snowpipe to continuously load data as soon as files arrive in the stage.

2fill in blank

medium

Complete the code to create a notification integration for Snowpipe.

Snowflake

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

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

ASTORAGE

BAWS_SNS

CQUEUE

DAWS_SQS

Attempts:

3 left

💡 Hint

Common Mistakes

Using AWS_SQS or AWS_SNS, which are not valid TYPE values.

Using STORAGE which is not a valid type.

Snowpipe notification integrations use TYPE = QUEUE to receive event messages for continuous loading. Cloud-specific parameters (e.g. AWS_SQS_URL) are specified separately.

3fill in blank

hard

Fix the error in the COPY statement inside the Snowpipe definition.

Snowflake

CREATE PIPE my_pipe AUTO_INGEST = TRUE NOTIFICATION_INTEGRATION = my_integration AS COPY INTO my_table FROM [1];

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

Amy_stage

B'my_stage'

Cstage

D@my_stage

Attempts:

3 left

💡 Hint

Common Mistakes

Omitting '@' causes Snowflake to look for a table or file path.

Using quotes around the stage name is invalid.

The stage name must be prefixed with '@' to indicate it is a stage reference in the COPY INTO command.

4fill in blank

hard

Fill both blanks to configure the pipe to load from an external stage and specify the file format.

Snowflake

CREATE PIPE my_pipe AUTO_INGEST = TRUE NOTIFICATION_INTEGRATION = my_integration AS COPY INTO my_table FROM [1] FILE_FORMAT = (TYPE = [2]);

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

A@external_stage

BCSV

CJSON

Dmy_stage

Attempts:

3 left

💡 Hint

Common Mistakes

Using stage names without '@'.

Choosing the wrong file format type.

The pipe loads data from the external stage '@external_stage' and uses the CSV file format for parsing files.

5fill in blank

hard

Fill all three blanks to create a pipe with auto ingest, using a notification integration and a JSON file format.

Snowflake

CREATE PIPE my_pipe AUTO_INGEST = [1] NOTIFICATION_INTEGRATION = [2] AS COPY INTO my_table FROM [3] FILE_FORMAT = (TYPE = 'JSON');

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

ATRUE

Bmy_integration

C@my_stage

DFALSE

Attempts:

3 left

💡 Hint

Common Mistakes

Setting AUTO_INGEST to FALSE disables continuous loading.

Using stage names without '@'.

Incorrect notification integration name.

This pipe is set to auto ingest (TRUE), uses the notification integration named 'my_integration', and loads data from the stage '@my_stage' with JSON format.

Practice

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

easy

A. To create visual dashboards from Snowflake data

B. To manually run SQL queries on Snowflake tables

C. To automatically load data continuously from cloud storage into Snowflake tables

D. To backup Snowflake databases to local storage

Solution

1. Step 1: Understand Snowpipe's role

   Snowpipe is designed to automate data loading continuously as new files arrive in cloud storage.

2. Step 2: Compare options

   Options A, B, and D describe visualization, manual querying, and backup, which are not Snowpipe's functions.

3. Final Answer:

   To automatically load data continuously from cloud storage into Snowflake tables -> Option C

4. Quick Check:

   Snowpipe = automatic continuous loading [OK]

Hint: Snowpipe automates loading new files immediately [OK]

Common Mistakes:

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

2. Which Snowpipe configuration enables automatic data loading when new files arrive?

easy

A. AUTO_INGEST = FALSE

B. AUTO_INGEST = TRUE

C. AUTO_LOAD = TRUE

D. AUTO_COPY = TRUE

Solution

1. Step 1: Identify the correct parameter for automatic loading

   The parameter AUTO_INGEST controls whether Snowpipe automatically loads data when new files arrive.

2. Step 2: Check option values

   Setting AUTO_INGEST = TRUE enables automatic loading; other options are invalid or incorrect parameter names.

3. Final Answer:

   AUTO_INGEST = TRUE -> Option B

4. Quick Check:

   AUTO_INGEST TRUE = auto load [OK]

Hint: AUTO_INGEST = TRUE enables continuous loading [OK]

Common Mistakes:

• Using AUTO_INGEST = FALSE disables auto loading
• Confusing parameter names like AUTO_LOAD or AUTO_COPY
• Not setting AUTO_INGEST at all

3. Given this Snowpipe command snippet:

CREATE PIPE my_pipe AUTO_INGEST = TRUE AS
COPY INTO my_table FROM @my_stage;

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

medium

A. Snowpipe automatically loads the file data into my_table

B. The file is ignored until manual COPY command runs

C. An error occurs because AUTO_INGEST must be FALSE

D. The file is deleted from @my_stage immediately

Solution

1. Step 1: Understand AUTO_INGEST = TRUE effect

   This setting tells Snowpipe to load new files automatically when they appear in the stage.

2. Step 2: Analyze file arrival behavior

   When a new file is added to @my_stage, Snowpipe triggers the COPY INTO command to load data into my_table.

3. Final Answer:

   Snowpipe automatically loads the file data into my_table -> Option A

4. Quick Check:

   AUTO_INGEST TRUE + new file = auto load [OK]

Hint: AUTO_INGEST TRUE means new files load automatically [OK]

Common Mistakes:

• Thinking manual COPY is still needed
• Believing AUTO_INGEST must be FALSE for loading
• Assuming files get deleted automatically

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

medium

A. Event notifications from cloud storage are not set up correctly

B. The COPY INTO command syntax is invalid

C. AUTO_INGEST should be set to FALSE for auto loading

D. Snowpipe only works with manual triggers

Solution

1. Step 1: Check AUTO_INGEST prerequisites

   For AUTO_INGEST = TRUE to work, event notifications from cloud storage must be configured to notify Snowpipe of new files.

2. Step 2: Evaluate other options

   Invalid COPY syntax would cause errors but not silent failure; AUTO_INGEST = FALSE disables auto loading; Snowpipe supports auto loading with correct setup.

3. Final Answer:

   Event notifications from cloud storage are not set up correctly -> Option A

4. Quick Check:

   Missing event notifications = no auto load [OK]

Hint: Check cloud event notifications for AUTO_INGEST [OK]

Common Mistakes:

• Setting AUTO_INGEST to FALSE expecting auto load
• Ignoring cloud storage event notification setup
• Assuming Snowpipe requires manual triggers only

5. You want to load JSON files continuously into a Snowflake table using Snowpipe. Which combination of steps is correct?

hard

A. Create a pipe with AUTO_INGEST=FALSE, manually run COPY INTO with FILE_FORMAT = (TYPE = 'CSV'), and ignore event notifications

B. Create a pipe with AUTO_INGEST=TRUE, but do not create a stage or configure event notifications

C. Create a stage for CSV files, create a pipe with AUTO_INGEST=TRUE using COPY INTO without specifying file format, and disable event notifications

D. Create a stage for JSON files, create a pipe with AUTO_INGEST=TRUE using COPY INTO with FILE_FORMAT = (TYPE = 'JSON'), and configure cloud event notifications

Solution

1. Step 1: Prepare stage and pipe for JSON files

   Create a stage pointing to JSON files and a pipe with AUTO_INGEST=TRUE that uses COPY INTO specifying JSON file format.

2. Step 2: Configure cloud event notifications

   Set up cloud storage event notifications so Snowpipe knows when new files arrive to trigger loading automatically.

3. Final Answer:

   Create a stage for JSON files, create a pipe with AUTO_INGEST=TRUE using COPY INTO with FILE_FORMAT = (TYPE = 'JSON'), and configure cloud event notifications -> Option D

4. Quick Check:

   Stage + pipe + JSON format + event notifications = correct setup [OK]

Hint: Match file format and enable event notifications for continuous load [OK]

Common Mistakes:

• Using wrong file format in COPY INTO
• Not configuring event notifications
• Setting AUTO_INGEST to FALSE expecting auto load
• Skipping stage creation