Multi-cluster warehouses in Snowflake - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to create a multi-cluster warehouse with auto-scaling enabled.

Snowflake

CREATE WAREHOUSE my_wh WITH WAREHOUSE_SIZE = 'XSMALL' [1];

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

AAUTO_SUSPEND = 60

BMAX_CLUSTER_COUNT = 3

CMIN_CLUSTER_COUNT = 1

DAUTO_RESUME = TRUE

Attempts:

3 left

💡 Hint

Common Mistakes

Using AUTO_SUSPEND instead of MAX_CLUSTER_COUNT

Setting MIN_CLUSTER_COUNT without MAX_CLUSTER_COUNT

The MAX_CLUSTER_COUNT parameter enables multi-cluster warehouses by setting the maximum number of clusters.

2fill in blank

medium

Complete the code to set the minimum number of clusters for a multi-cluster warehouse.

Snowflake

ALTER WAREHOUSE my_wh SET [1] = 2;

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

AMIN_CLUSTER_COUNT

BMAX_CLUSTER_COUNT

CAUTO_SUSPEND

DAUTO_RESUME

Attempts:

3 left

💡 Hint

Common Mistakes

Confusing MIN_CLUSTER_COUNT with MAX_CLUSTER_COUNT

Using AUTO_SUSPEND instead of cluster count

The MIN_CLUSTER_COUNT parameter sets the minimum number of clusters that remain active.

3fill in blank

hard

Fix the error in the code to enable auto-suspend for a multi-cluster warehouse.

Snowflake

ALTER WAREHOUSE my_wh SET AUTO_SUSPEND = [1];

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

A'TRUE'

BTRUE

C'60'

D60

Attempts:

3 left

💡 Hint

Common Mistakes

Using TRUE or 'TRUE' instead of a number

Using a string for the number instead of an integer

The AUTO_SUSPEND parameter expects a number representing seconds before suspension, not a boolean.

4fill in blank

hard

Fill both blanks to create a multi-cluster warehouse with minimum 2 and maximum 5 clusters.

Snowflake

CREATE WAREHOUSE multi_wh WITH WAREHOUSE_SIZE = 'MEDIUM' [1] [2];

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

AMIN_CLUSTER_COUNT = 2

BAUTO_RESUME = TRUE

CMAX_CLUSTER_COUNT = 5

DAUTO_SUSPEND = 300

Attempts:

3 left

💡 Hint

Common Mistakes

Using AUTO_RESUME or AUTO_SUSPEND instead of cluster counts

Setting only one of the cluster count parameters

Setting MIN_CLUSTER_COUNT and MAX_CLUSTER_COUNT defines the cluster range for the warehouse.

5fill in blank

hard

Fill all three blanks to alter a warehouse to enable auto-resume, set auto-suspend to 120 seconds, and max clusters to 4.

Snowflake

ALTER WAREHOUSE my_wh SET [1] = TRUE, [2] = [3], MAX_CLUSTER_COUNT = 4;

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

AAUTO_RESUME

BAUTO_SUSPEND

C120

DMIN_CLUSTER_COUNT

Attempts:

3 left

💡 Hint

Common Mistakes

Mixing AUTO_RESUME and AUTO_SUSPEND parameters

Using a string instead of a number for AUTO_SUSPEND

AUTO_RESUME enables the warehouse to start automatically, AUTO_SUSPEND sets the idle time before suspension, and 120 is the time in seconds.

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