Multi-cluster warehouses in Snowflake - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is a multi-cluster warehouse in Snowflake?

A multi-cluster warehouse is a compute resource in Snowflake that can automatically start and stop multiple clusters to handle varying query loads, improving performance and concurrency.

intermediate

How does Snowflake decide when to add or remove clusters in a multi-cluster warehouse?

Snowflake adds clusters when query load increases and removes clusters when load decreases, based on user activity and concurrency to optimize resource use and cost.

beginner

What are the benefits of using multi-cluster warehouses?

They provide better concurrency handling, reduce query queuing, and maintain consistent performance during peak workloads by scaling compute resources automatically.

intermediate

What is the difference between a single-cluster and a multi-cluster warehouse?

A single-cluster warehouse has one compute cluster and can become a bottleneck under high load, while a multi-cluster warehouse can run multiple clusters simultaneously to handle more queries.

intermediate

How do you configure a multi-cluster warehouse in Snowflake?

You set the warehouse size and specify the minimum and maximum number of clusters to allow Snowflake to auto-scale between these limits based on workload.

What triggers Snowflake to add a new cluster in a multi-cluster warehouse?

A Manual user request only

B Scheduled time intervals

C Increased query load causing queuing

D When storage usage is high

Snowflake automatically adds clusters when query load increases and queries start to queue, to improve performance.

Which of the following is NOT a benefit of multi-cluster warehouses?

A Reduced storage costs

B Automatic scaling of compute resources

C Consistent query performance during peak times

D Improved query concurrency

Multi-cluster warehouses improve compute scaling and concurrency but do not directly reduce storage costs.

What happens when the workload decreases in a multi-cluster warehouse?

A Nothing changes automatically

B Snowflake stops all clusters immediately

C Snowflake increases cluster size

D Snowflake reduces the number of active clusters

Snowflake automatically reduces the number of active clusters to save resources when workload decreases.

How do you limit the number of clusters in a multi-cluster warehouse?

A By disabling auto-scaling

B By setting minimum and maximum cluster counts

C By setting storage limits

D By setting query timeout

You configure the minimum and maximum number of clusters to control auto-scaling limits.

Which warehouse type can become a bottleneck under high query load?

A Single-cluster warehouse

B Multi-cluster warehouse

C Virtual warehouse

D Cloud storage warehouse

Single-cluster warehouses have only one cluster and can become bottlenecks when many queries run simultaneously.

Explain how a multi-cluster warehouse manages varying workloads in Snowflake.

Think about how Snowflake adjusts compute resources based on query demand.

Describe the key differences between single-cluster and multi-cluster warehouses.

Focus on how many clusters run and how they affect query handling.

Practice

1. What is the main purpose of a multi-cluster warehouse in Snowflake?

easy

A. To automatically add or remove compute clusters based on workload demand

B. To store data in multiple regions for disaster recovery

C. To encrypt data at rest and in transit

D. To create backups of data automatically every hour

Solution

1. Step 1: Understand multi-cluster warehouse functionality

   Multi-cluster warehouses adjust the number of compute clusters automatically to handle workload changes.

2. Step 2: Compare options with this functionality

   Only To automatically add or remove compute clusters based on workload demand describes automatic scaling of compute clusters based on demand.

3. Final Answer:

   To automatically add or remove compute clusters based on workload demand -> Option A

4. Quick Check:

   Multi-cluster warehouses scale clusters automatically = A [OK]

Hint: Remember: multi-cluster means auto scaling clusters [OK]

Common Mistakes:

• Confusing multi-cluster warehouses with data replication
• Thinking multi-cluster warehouses handle backups
• Assuming multi-cluster warehouses manage encryption

2. Which of the following is the correct way to set the minimum and maximum cluster count for a multi-cluster warehouse in Snowflake?

easy

A. ALTER WAREHOUSE mywh SET MIN_CLUSTER_COUNT = 2, MAX_CLUSTER_COUNT = 5;

B. ALTER WAREHOUSE mywh SET MIN_CLUSTERS = 2, MAX_CLUSTERS = 5;

C. ALTER WAREHOUSE mywh SET MIN_CLUSTER = 2, MAX_CLUSTER = 5;

D. ALTER WAREHOUSE mywh SET CLUSTER_MIN = 2, CLUSTER_MAX = 5;

Solution

1. Step 1: Recall correct parameter names for cluster count

   The correct parameters are MIN_CLUSTERS and MAX_CLUSTERS.

2. Step 2: Match syntax with correct parameters

   ALTER WAREHOUSE mywh SET MIN_CLUSTERS = 2, MAX_CLUSTERS = 5; uses the exact correct syntax and parameter names for Snowflake.

3. Final Answer:

   ALTER WAREHOUSE mywh SET MIN_CLUSTERS = 2, MAX_CLUSTERS = 5; -> Option B

4. Quick Check:

   Use MIN_CLUSTERS and MAX_CLUSTERS for scaling [OK]

Hint: Use full parameter names with _CLUSTERS suffix [OK]

Common Mistakes:

• Using incorrect parameter names like MIN_CLUSTER_COUNT
• Omitting the _CLUSTERS suffix
• Using wrong syntax for ALTER WAREHOUSE

3. Consider a multi-cluster warehouse configured with MIN_CLUSTER_COUNT=1 and MAX_CLUSTER_COUNT=3. If the workload suddenly increases, what will happen?

medium

A. The warehouse will reduce clusters to save cost

B. The warehouse will stay at 1 cluster and queue queries

C. The warehouse will shut down automatically

D. The warehouse will add clusters up to 3 to handle the workload

Solution

1. Step 1: Understand scaling behavior of multi-cluster warehouses

   When workload increases, Snowflake adds clusters up to the MAX_CLUSTER_COUNT to reduce query wait times.

2. Step 2: Apply configuration limits

   Since MAX_CLUSTER_COUNT is 3, the warehouse can scale from 1 up to 3 clusters automatically.

3. Final Answer:

   The warehouse will add clusters up to 3 to handle the workload -> Option D

4. Quick Check:

   Workload increase triggers cluster scaling up to max [OK]

Hint: Scaling adds clusters up to max limit on demand [OK]

Common Mistakes:

• Assuming clusters stay fixed at minimum count
• Thinking warehouse shuts down on high load
• Believing clusters reduce during high workload

4. You configured a multi-cluster warehouse with MIN_CLUSTER_COUNT=2 and MAX_CLUSTER_COUNT=4, but it never scales beyond 2 clusters even under heavy load. What is the most likely cause?

medium

A. The warehouse is paused

B. The MAX_CLUSTER_COUNT parameter is set incorrectly

C. The warehouse is set to SINGLE cluster mode instead of MULTI cluster mode

D. The warehouse size is too small to scale

Solution

1. Step 1: Check warehouse mode setting

   Multi-cluster scaling only works if the warehouse is in MULTI cluster mode, not SINGLE cluster mode.

2. Step 2: Understand effect of SINGLE cluster mode

   If set to SINGLE cluster mode, the warehouse will not scale beyond one cluster regardless of MIN or MAX settings.

3. Final Answer:

   The warehouse is set to SINGLE cluster mode instead of MULTI cluster mode -> Option C

4. Quick Check:

   Multi-cluster scaling requires MULTI cluster mode [OK]

Hint: Check warehouse mode: must be MULTI cluster for scaling [OK]

Common Mistakes:

• Ignoring warehouse mode and expecting scaling
• Assuming warehouse size limits scaling
• Not realizing paused warehouse cannot scale

5. You want to optimize a multi-cluster warehouse for unpredictable workloads that spike quickly but also have long idle periods. Which configuration is best to balance performance and cost?

hard

A. Set MIN_CLUSTER_COUNT=1 and MAX_CLUSTER_COUNT=5 with auto-suspend enabled

B. Set MIN_CLUSTER_COUNT=5 and MAX_CLUSTER_COUNT=5 with auto-suspend disabled

C. Set MIN_CLUSTER_COUNT=3 and MAX_CLUSTER_COUNT=3 with auto-suspend enabled

D. Set MIN_CLUSTER_COUNT=0 and MAX_CLUSTER_COUNT=1 with auto-suspend disabled

Solution

1. Step 1: Analyze workload characteristics

   Unpredictable spikes require ability to scale up quickly; long idle times require cost saving by suspending.

2. Step 2: Evaluate configuration options

   Set MIN_CLUSTER_COUNT=1 and MAX_CLUSTER_COUNT=5 with auto-suspend enabled allows scaling from 1 to 5 clusters and enables auto-suspend to save cost during idle periods.

3. Step 3: Compare other options

   Configurations with fixed cluster counts reduce flexibility; MIN_CLUSTER_COUNT=0 and MAX_CLUSTER_COUNT=1 with auto-suspend disabled limits max clusters and increases cost.

4. Final Answer:

   Set MIN_CLUSTER_COUNT=1 and MAX_CLUSTER_COUNT=5 with auto-suspend enabled -> Option A

5. Quick Check:

   Flexible scaling plus auto-suspend balances cost and performance [OK]

Hint: Use low min, high max clusters with auto-suspend for spikes [OK]

Common Mistakes:

• Fixing cluster count too high wastes cost
• Disabling auto-suspend wastes resources during idle
• Setting max clusters too low limits performance