Clustering keys for large tables in Snowflake - Practice Problems & Coding Challenges

Challenge - 5 Problems

🧠 Conceptual

intermediate

Why use clustering keys on large tables?

Imagine you have a huge table with millions of rows. Why would adding clustering keys help when querying this table?

A Clustering keys duplicate data to make queries run faster.

B Clustering keys physically sort the data to speed up queries that filter on those keys.

C Clustering keys automatically compress the data to reduce storage size.

D Clustering keys create indexes that speed up all types of queries regardless of filters.

💡 Hint

Think about how data is stored and accessed on disk.

Clustering keys organize data physically by the key columns, so queries filtering on those keys scan less data, improving speed.

❓ Model Choice

intermediate

Choosing clustering keys for time-series data

You have a large table storing sensor readings with columns: sensor_id, reading_time, temperature. Which clustering key choice is best to speed up queries filtering by recent time ranges?

A CLUSTER BY (reading_time)

B No clustering key needed

C CLUSTER BY (temperature)

D CLUSTER BY (sensor_id)

💡 Hint

Queries filter mostly by recent timestamps.

Clustering by reading_time groups data by time, so queries filtering recent times scan less data.

❓ Hyperparameter

advanced

Impact of too many clustering keys

What is a likely effect of defining too many clustering keys on a large table?

A Increased maintenance cost and slower data loading due to complex clustering.

B Automatic removal of unused keys by Snowflake.

C Improved query speed for all queries without any downsides.

D No effect; clustering keys do not impact performance.

💡 Hint

Think about the cost of maintaining physical data order.

Too many clustering keys make the clustering process complex and costly, slowing data loading and maintenance.

❓ Metrics

advanced

Evaluating clustering effectiveness

Which metric helps you understand if your clustering keys are effective in Snowflake?

A Total storage size of the table.

B Number of rows in the table.

C Clustering depth metric showing how well data is sorted by keys.

D Number of columns in the table.

💡 Hint

Look for a metric that measures data organization quality.

Clustering depth measures how well data is physically sorted by clustering keys, indicating clustering effectiveness.

🔧 Debug

expert

Why is clustering not improving query speed?

You added clustering keys on columns user_id and event_date for a large events table. But queries filtering on event_date are still slow. What is the most likely reason?

A Snowflake does not support clustering on date columns.

B Clustering keys only speed up queries filtering on all key columns together.

C The table is too small for clustering to have any effect.

D The clustering keys are defined in the wrong order; event_date should be first.

💡 Hint

Think about how clustering keys order data physically.

Clustering keys order data by the first key, then second, so if event_date is second, filtering only by event_date may not be efficient.

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