Clustering keys for large tables in Snowflake - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to create a clustering key on the 'customer_id' column.

Snowflake

ALTER TABLE sales_data CLUSTER BY ([1]);

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

Acustomer_id

Bproduct_id

Cregion

Dorder_date

Attempts:

3 left

💡 Hint

Common Mistakes

Choosing a column that is rarely used in queries.

Using a column with low cardinality as clustering key.

The clustering key should be set on the 'customer_id' column to optimize queries filtering by customer.

2fill in blank

medium

Complete the code to create a clustering key on multiple columns: 'region' and 'order_date'.

Snowflake

ALTER TABLE sales_data CLUSTER BY ([1], order_date);

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

Aproduct_id

Bcustomer_id

Cregion

Dsales_amount

Attempts:

3 left

💡 Hint

Common Mistakes

Swapping the order of clustering columns.

Using columns not suitable for clustering.

To cluster by 'region' and 'order_date', the first column must be 'region'.

3fill in blank

hard

Fix the error in the clustering key syntax to cluster by 'order_date'.

Snowflake

ALTER TABLE sales_data CLUSTER BY [1];

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

A(order_date)

B'order_date'

Corder_date

D[order_date]

Attempts:

3 left

💡 Hint

Common Mistakes

Using quotes around column names.

Using brackets instead of parentheses.

The clustering key columns must be enclosed in parentheses without quotes.

4fill in blank

hard

Fill both blanks to create a clustering key on 'region' and 'customer_id'.

Snowflake

ALTER TABLE sales_data CLUSTER BY ([1], [2]);

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

Aregion

Border_date

Ccustomer_id

Dproduct_id

Attempts:

3 left

💡 Hint

Common Mistakes

Reversing the order of clustering columns.

Using columns not relevant for query patterns.

The clustering key should be on 'region' first, then 'customer_id' to optimize queries filtering by these columns.

5fill in blank

hard

Fill all three blanks to create a clustering key on 'region', 'order_date', and 'product_id'.

Snowflake

ALTER TABLE sales_data CLUSTER BY ([1], [2], [3]);

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

Aregion

Border_date

Cproduct_id

Dcustomer_id

Attempts:

3 left

💡 Hint

Common Mistakes

Incorrect order of clustering columns.

Including columns that are not useful for clustering.

The clustering key columns are 'region', then 'order_date', then 'product_id' to optimize multi-dimensional queries.

Practice

1.

What is the main purpose of using clustering keys in large Snowflake tables?

easy

A. To group data physically for faster query performance

B. To encrypt the data for security

C. To create backups automatically

D. To increase storage space usage

Solution

1. Step 1: Understand clustering keys role

   Clustering keys organize data physically in storage to improve how fast queries run.

2. Step 2: Compare options

   Only To group data physically for faster query performance describes grouping data for faster queries. Others mention unrelated features like encryption or backups.

3. Final Answer:

   To group data physically for faster query performance -> Option A

4. Quick Check:

   Clustering keys = faster queries [OK]

Hint: Clustering keys speed up queries by grouping data [OK]

Common Mistakes:

• Thinking clustering keys encrypt data
• Confusing clustering keys with backups
• Assuming clustering keys increase storage

2.

Which of the following is the correct syntax to add a clustering key on column user_id when creating a table in Snowflake?

CREATE TABLE users (id INT, user_id INT, name STRING) ...

easy

A. CLUSTERING user_id

B. CLUSTER ON user_id

C. CLUSTER KEY user_id

D. CLUSTER BY (user_id)

Solution

1. Step 1: Recall Snowflake clustering syntax

   Snowflake uses CLUSTER BY (column_name) to define clustering keys during table creation.

2. Step 2: Check options

   Only CLUSTER BY (user_id) matches the correct syntax. Others use incorrect keywords or missing parentheses.

3. Final Answer:

   CLUSTER BY (user_id) -> Option D

4. Quick Check:

   Correct syntax = CLUSTER BY (column) [OK]

Hint: Use 'CLUSTER BY (column)' to set clustering keys [OK]

Common Mistakes:

• Using 'CLUSTER ON' instead of 'CLUSTER BY'
• Omitting parentheses around column name
• Using 'CLUSTER KEY' which is invalid

3.

Given the table sales with columns region, date, and amount, and clustering key on region, what is the expected effect on the query below?

SELECT SUM(amount) FROM sales WHERE region = 'West';

medium

A. Query result will be incorrect due to clustering

B. Query runs slower because clustering adds overhead

C. Query runs faster because data is clustered by region

D. Query performance is unchanged

Solution

1. Step 1: Understand clustering effect on filtering

   Clustering by region groups data physically, so filtering by region scans fewer data blocks.

2. Step 2: Analyze query impact

   The query filters on region = 'West', so it benefits from clustering, making it faster.

3. Final Answer:

   Query runs faster because data is clustered by region -> Option C

4. Quick Check:

   Filter on clustering key = faster query [OK]

Hint: Filtering on clustering key speeds queries [OK]

Common Mistakes:

• Thinking clustering slows queries
• Assuming clustering changes query results
• Believing clustering has no effect on performance

4.

Identify the error in this Snowflake command to add a clustering key on customer_id to an existing table orders:

ALTER TABLE orders ADD CLUSTER BY (customer_id);

medium

A. Should use ALTER TABLE orders CLUSTER BY (customer_id);

B. Cannot add clustering keys to existing tables

C. Clustering keys must be added during table creation only

D. Missing parentheses around customer_id

Solution

1. Step 1: Check Snowflake syntax for altering clustering keys

   Snowflake requires ALTER TABLE ... CLUSTER BY (columns) to add or change clustering keys.

2. Step 2: Compare given command

   The command uses ADD CLUSTER BY which is invalid syntax.

3. Final Answer:

   Should use ALTER TABLE orders CLUSTER BY (customer_id); -> Option A

4. Quick Check:

   Use CLUSTER BY with parentheses to alter keys [OK]

Hint: Use 'ALTER TABLE ... CLUSTER BY (cols)' to add keys [OK]

Common Mistakes:

• Using ADD instead of CLUSTER BY
• Omitting parentheses around columns
• Believing clustering keys can't be altered

5.

You have a large table events with columns event_type, event_date, and user_id. You often run queries filtering by event_type and event_date. Which clustering key choice will best improve query speed?

hard

A. CLUSTER BY (user_id)

B. CLUSTER BY (event_type, event_date)

C. CLUSTER BY (event_date)

D. No clustering key needed

Solution

1. Step 1: Identify columns used in frequent filters

   Queries filter on both event_type and event_date, so clustering on both helps.

2. Step 2: Evaluate clustering options

   CLUSTER BY (event_type, event_date) clusters by both columns, improving filtering speed. CLUSTER BY (user_id) clusters on unrelated user_id. CLUSTER BY (event_date) clusters only on one filter column. No clustering key needed ignores clustering benefits.

3. Final Answer:

   CLUSTER BY (event_type, event_date) -> Option B

4. Quick Check:

   Cluster on all filter columns for best speed [OK]

Hint: Cluster on all frequent filter columns together [OK]

Common Mistakes:

• Clustering on unrelated columns
• Clustering on only one of multiple filter columns
• Skipping clustering for large tables