Multi-cluster warehouses in Snowflake - Practice Problems & Coding Challenges

Challenge - 5 Problems

🧠 Conceptual

intermediate

Understanding Multi-cluster Warehouse Behavior

What happens when a Snowflake multi-cluster warehouse reaches its maximum number of clusters during a high query load?

A Queries are rejected with an error indicating warehouse capacity exceeded.

B New queries are queued until an existing cluster finishes processing and frees capacity.

C Snowflake automatically creates additional clusters beyond the maximum limit to handle the load.

D The warehouse scales down to a single cluster to reduce costs.

💡 Hint

Think about how Snowflake manages concurrency within set limits.

Snowflake queues new queries when all clusters are busy and the maximum cluster count is reached. It does not create extra clusters beyond the configured maximum, nor does it reject queries or scale down automatically under load.

❓ Configuration

intermediate

Configuring a Multi-cluster Warehouse

Which Snowflake SQL command correctly creates a multi-cluster warehouse named 'ANALYTICS_WH' with a minimum of 2 clusters and a maximum of 5 clusters?

A CREATE WAREHOUSE ANALYTICS_WH WAREHOUSE_SIZE = 'MEDIUM' MIN_CLUSTER_COUNT = 2 MAX_CLUSTER_COUNT = 5;

B CREATE WAREHOUSE ANALYTICS_WH WAREHOUSE_SIZE = 'MEDIUM' SET MIN_CLUSTER_COUNT = 2 SET MAX_CLUSTER_COUNT = 5;

C CREATE WAREHOUSE ANALYTICS_WH WITH WAREHOUSE_SIZE = 'MEDIUM' SET MIN_CLUSTER_COUNT = 2 MAX_CLUSTER_COUNT = 5;

D CREATE WAREHOUSE ANALYTICS_WH WITH WAREHOUSE_SIZE = 'MEDIUM' MIN_CLUSTER_COUNT = 2 MAX_CLUSTER_COUNT = 5;

💡 Hint

Check the correct syntax for warehouse creation with multi-cluster settings.

The correct syntax uses 'WITH' followed by parameters separated by spaces and equals signs. 'MIN_CLUSTER_COUNT' and 'MAX_CLUSTER_COUNT' must be set within the 'WITH' clause.

❓ Architecture

advanced

Choosing Multi-cluster Warehouse Settings for Variable Load

You have a workload with unpredictable spikes in query volume. Which multi-cluster warehouse configuration best balances cost and performance?

A Set MIN_CLUSTER_COUNT and MAX_CLUSTER_COUNT both to 1 to avoid extra costs.

B Set MIN_CLUSTER_COUNT equal to MAX_CLUSTER_COUNT at a high number to always have maximum clusters running.

C Set MIN_CLUSTER_COUNT to 1 and MAX_CLUSTER_COUNT to a higher number like 10 to allow scaling during spikes.

D Disable multi-cluster and rely on a single large cluster to handle all queries.

💡 Hint

Consider how multi-cluster warehouses scale and cost implications.

Setting a low minimum and a higher maximum cluster count allows the warehouse to scale out during spikes and scale in when idle, balancing cost and performance.

❓ security

advanced

Security Implications of Multi-cluster Warehouses

Which statement about security and multi-cluster warehouses in Snowflake is true?

A All clusters in a multi-cluster warehouse share the same security context and access controls.

B Each cluster in a multi-cluster warehouse runs in a separate virtual private cloud (VPC) for isolation.

C Multi-cluster warehouses require separate user roles for each cluster to enforce security.

D Data encryption keys differ per cluster in a multi-cluster warehouse.

💡 Hint

Think about how Snowflake manages security across clusters in the same warehouse.

All clusters in a multi-cluster warehouse operate under the same security context and access controls defined at the warehouse and database level.

❓ service_behavior

expert

Impact of Auto Suspend on Multi-cluster Warehouses

If a multi-cluster warehouse is configured with AUTO_SUSPEND = 300 seconds and MIN_CLUSTER_COUNT = 2, what happens when the warehouse is idle for 10 minutes?

A Clusters above the minimum suspend after 5 minutes, but the minimum number of clusters remain running.

B The warehouse suspends completely after 5 minutes, regardless of minimum cluster count.

C The warehouse never suspends because minimum clusters must always be active.

D All clusters suspend after 5 minutes of inactivity, including reducing clusters below the minimum count.

💡 Hint

Consider how auto suspend interacts with minimum cluster count in multi-cluster warehouses.

Clusters above the minimum count suspend after the AUTO_SUSPEND period, but the minimum number of clusters remain active to ensure availability.

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