Why pipelines automate data freshness in Snowflake - Test Your Understanding

Practice - 5 Tasks

1fill in blank

easy

Complete the code to create a Snowflake task that runs every hour.

Snowflake

CREATE OR REPLACE TASK hourly_task
  WAREHOUSE = my_warehouse
  SCHEDULE = [1]
AS
  CALL refresh_data();

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

A'1 MINUTE'

B'1 HOUR'

C'10 MINUTES'

D'1 DAY'

Attempts:

3 left

💡 Hint

Common Mistakes

Using '1 MINUTE' runs too frequently.

Using '1 DAY' runs too infrequently.

The schedule '1 HOUR' sets the task to run every hour, ensuring data freshness hourly.

2fill in blank

medium

Complete the code to resume the Snowflake task after creation.

Snowflake

ALTER TASK hourly_task [1];

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

ARESUME

BSUSPEND

CPAUSE

DSTART

Attempts:

3 left

💡 Hint

Common Mistakes

Using SUSPEND stops the task.

START is not a valid Snowflake task command.

RESUME activates the task so it can run on its schedule.

3fill in blank

hard

Fix the error in the task creation by choosing the correct schedule syntax.

Snowflake

CREATE OR REPLACE TASK daily_task
  WAREHOUSE = my_warehouse
  SCHEDULE = [1]
AS
  CALL refresh_daily_data();

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

A'EVERY 24 HOURS'

B'24 HOURS'

C'DAILY'

D'1 DAY'

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'DAILY' is invalid syntax.

Using 'EVERY 24 HOURS' is not supported.

Snowflake expects schedule intervals like '1 DAY' for daily tasks.

4fill in blank

hard

Fill both blanks to create a task that runs every 30 minutes and calls the correct procedure.

Snowflake

CREATE OR REPLACE TASK [1]
  WAREHOUSE = my_warehouse
  SCHEDULE = [2]
AS
  CALL refresh_half_hour_data();

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

Ahalf_hour_task

Bhourly_task

C'30 MINUTES'

D'60 MINUTES'

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'hourly_task' with '30 MINUTES' is inconsistent.

Using '60 MINUTES' runs hourly, not half-hourly.

The task name 'half_hour_task' and schedule '30 MINUTES' set the task to run every half hour.

5fill in blank

hard

Fill all three blanks to create a task that runs daily, calls the correct procedure, and resumes the task.

Snowflake

CREATE OR REPLACE TASK [1]
  WAREHOUSE = my_warehouse
  SCHEDULE = '[2]'
AS
  CALL [3];

ALTER TASK [1] RESUME;

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

Adaily_task

B1 DAY

Crefresh_daily_data()

Drefresh_hourly_data()

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'refresh_hourly_data()' for a daily task.

Forgetting to resume the task after creation.

The task named 'daily_task' runs every '1 DAY' and calls 'refresh_daily_data()'. The ALTER TASK command resumes it.

Practice

1. What is the main reason to use tasks in Snowflake for data freshness?

easy

A. To automate data updates without manual steps

B. To store data permanently without changes

C. To manually refresh data when needed

D. To delete old data automatically

Solution

1. Step 1: Understand task purpose

   Tasks are designed to automate data updates, so they run without manual work.

2. Step 2: Identify automation benefit

   Automating data updates keeps data fresh and ready without needing manual refreshes.

3. Final Answer:

   To automate data updates without manual steps -> Option A

4. Quick Check:

   Automation means no manual steps [OK]

Hint: Tasks run automatically to keep data fresh [OK]

Common Mistakes:

• Thinking tasks only store data
• Assuming manual refresh is needed
• Confusing deletion with freshness

2. Which syntax correctly creates a Snowflake task that runs every hour?

easy

A. CREATE TASK my_task SCHEDULE = '1 HOUR' AS COPY INTO my_table FROM @my_stage;

B. CREATE TASK my_task SCHEDULE = 'USING CRON 0 * * * *' AS COPY INTO my_table FROM @my_stage;

C. CREATE TASK my_task SCHEDULE = '60 MINUTES' AS COPY INTO my_table FROM @my_stage;

D. CREATE TASK my_task SCHEDULE = 'EVERY HOUR' AS COPY INTO my_table FROM @my_stage;

Solution

1. Step 1: Check Snowflake task schedule syntax

   Snowflake uses CRON expressions for scheduling tasks, e.g., 'USING CRON 0 * * * *' means every hour at minute 0.

2. Step 2: Compare options

   Only CREATE TASK my_task SCHEDULE = 'USING CRON 0 * * * *' AS COPY INTO my_table FROM @my_stage; uses valid CRON syntax. Options A, B, and D use incorrect or unsupported schedule formats.

3. Final Answer:

   CREATE TASK my_task SCHEDULE = 'USING CRON 0 * * * *' AS COPY INTO my_table FROM @my_stage; -> Option B

4. Quick Check:

   Snowflake tasks use CRON for schedules [OK]

Hint: Snowflake task schedules use CRON syntax [OK]

Common Mistakes:

• Using plain time strings instead of CRON
• Writing 'EVERY HOUR' instead of CRON
• Confusing minutes and hours format

3. Given this task code:

CREATE TASK daily_update SCHEDULE = 'USING CRON 0 0 * * *' AS
COPY INTO sales FROM @sales_stage;

What happens when this task runs?

medium

A. It copies new data from sales_stage to sales table daily at midnight

B. It deletes all data from sales table daily at midnight

C. It copies data every minute from sales_stage to sales table

D. It runs only once when created

Solution

1. Step 1: Interpret CRON schedule

   'USING CRON 0 0 * * *' means the task runs daily at midnight (00:00 hours).

2. Step 2: Understand task action

   The task copies data from the stage 'sales_stage' into the 'sales' table each time it runs.

3. Final Answer:

   It copies new data from sales_stage to sales table daily at midnight -> Option A

4. Quick Check:

   CRON midnight + COPY INTO = daily data update [OK]

Hint: CRON 0 0 * * * means daily at midnight [OK]

Common Mistakes:

• Thinking it deletes data
• Assuming it runs every minute
• Believing it runs only once

4. You created a task but it never runs. Which fix will most likely solve this?

medium

A. Rename the task to a different name

B. Delete the task and recreate the table

C. Check if the task schedule uses valid CRON syntax

D. Run the COPY command manually every hour

Solution

1. Step 1: Identify common task issue

   If a task never runs, an invalid schedule is a common cause, especially if CRON syntax is wrong.

2. Step 2: Apply fix

   Correcting the schedule to valid CRON syntax enables the task to run automatically as expected.

3. Final Answer:

   Check if the task schedule uses valid CRON syntax -> Option C

4. Quick Check:

   Invalid schedule blocks task runs [OK]

Hint: Invalid CRON stops task from running [OK]

Common Mistakes:

• Deleting unrelated objects
• Running commands manually defeats automation
• Renaming does not fix schedule issues

5. You want to ensure your sales data is always fresh by running a task every 15 minutes. Which approach is best?

hard

A. Create a task without schedule and run it once daily

B. Manually run COPY commands every 15 minutes

C. Create a task with schedule 'USING CRON 15 * * * *' to run once per hour

D. Create a task with schedule 'USING CRON */15 * * * *' to automate data copy

Solution

1. Step 1: Understand CRON for 15-minute intervals

   'USING CRON */15 * * * *' means run every 15 minutes, which fits the requirement.

2. Step 2: Compare options for automation

   Create a task with schedule 'USING CRON */15 * * * *' to automate data copy automates the data copy every 15 minutes. Manually run COPY commands every 15 minutes is manual and not automated. Create a task with schedule 'USING CRON 15 * * * *' to run once per hour runs only once per hour, not every 15 minutes. Create a task without schedule and run it once daily runs once daily, too infrequent.

3. Final Answer:

   Create a task with schedule 'USING CRON */15 * * * *' to automate data copy -> Option D

4. Quick Check:

   CRON '*/15' means every 15 minutes [OK]

Hint: Use '*/15' in CRON for every 15 minutes [OK]

Common Mistakes:

• Choosing manual runs over automation
• Misunderstanding CRON syntax for intervals
• Setting schedule too infrequent