Warehouse sizes and scaling in Snowflake - Practice Problems & Coding Challenges

Challenge - 5 Problems

🧠 Conceptual

intermediate

Understanding Snowflake Warehouse Size Impact

Which of the following statements best describes the impact of increasing the size of a Snowflake warehouse?

A Increasing warehouse size decreases compute resources, which slows down query processing but reduces cost.

B Increasing warehouse size increases compute resources, which speeds up query processing but also increases cost proportionally.

C Increasing warehouse size has no effect on query speed but increases storage capacity.

D Increasing warehouse size automatically reduces the number of concurrent queries allowed.

💡 Hint

Think about how compute power and cost relate in Snowflake warehouses.

In Snowflake, larger warehouses have more compute resources, which speeds up queries but costs more because billing is based on compute usage.

❓ service_behavior

intermediate

Effect of Auto-suspend on Warehouse Billing

What happens to billing when a Snowflake warehouse is set to auto-suspend after 5 minutes of inactivity?

A Billing pauses only when the warehouse is manually suspended, not auto-suspended.

B Billing continues for 30 minutes after inactivity regardless of auto-suspend settings.

C Billing stops immediately after 5 minutes of inactivity because the warehouse suspends.

D Billing is unaffected by auto-suspend and continues as long as the account is active.

💡 Hint

Consider how auto-suspend controls warehouse state and billing.

Auto-suspend stops the warehouse after the set inactivity period, which stops compute billing since the warehouse is not running.

❓ Architecture

advanced

Choosing Warehouse Size for Concurrent Heavy Queries

You have a workload with many concurrent heavy queries that must complete quickly. Which Snowflake warehouse configuration is best?

A Use a single X-Large warehouse with multi-cluster enabled to scale out automatically.

B Use a Small warehouse and rely on query queuing to manage concurrency.

C Use multiple Small warehouses manually started and stopped as needed.

D Use a Medium warehouse with auto-suspend set to 1 minute.

💡 Hint

Think about how multi-cluster warehouses handle concurrency and heavy workloads.

Multi-cluster warehouses automatically add clusters to handle many concurrent heavy queries, improving performance without manual intervention.

❓ security

advanced

Security Implications of Warehouse Scaling

What is a key security consideration when enabling multi-cluster warehouses in Snowflake?

A Each cluster in a multi-cluster warehouse shares the same security context and access controls.

B Multi-cluster warehouses require separate user credentials for each cluster.

C Scaling warehouses automatically disables encryption for faster performance.

D Multi-cluster warehouses expose data to external networks by default.

💡 Hint

Consider how Snowflake manages security across clusters within the same warehouse.

All clusters in a multi-cluster warehouse operate under the same security policies and access controls, ensuring consistent security.

✅ Best Practice

expert

Optimizing Cost and Performance with Warehouse Scaling

You want to optimize both cost and performance for a variable workload with unpredictable spikes. Which Snowflake warehouse strategy is best?

A Set a Small warehouse with auto-resume disabled to control costs strictly.

B Use a Large warehouse always running to avoid startup delays during spikes.

C Manually start and stop multiple Small warehouses based on predicted workload.

D Configure a Medium warehouse with multi-cluster auto-scaling enabled and auto-suspend set to 5 minutes.

💡 Hint

Think about balancing automatic scaling and cost control features.

Auto-scaling with auto-suspend allows the warehouse to grow during spikes and pause when idle, optimizing cost and performance automatically.

Practice

1. What does the size of a Snowflake warehouse primarily determine?

easy

A. The storage capacity for data

B. The amount of computing power available for queries

C. The number of users who can access the database

D. The network bandwidth for data transfer

Solution

1. Step 1: Understand warehouse size meaning

   Warehouse size in Snowflake controls the compute resources allocated.

2. Step 2: Differentiate from storage and network

   Storage and network bandwidth are managed separately, not by warehouse size.

3. Final Answer:

   The amount of computing power available for queries -> Option B

4. Quick Check:

   Warehouse size = compute power [OK]

Hint: Warehouse size means compute power, not storage or users [OK]

Common Mistakes:

• Confusing warehouse size with storage capacity
• Thinking warehouse size limits user access
• Assuming network bandwidth depends on warehouse size

2. Which Snowflake warehouse size is correctly written in a SQL command to create a warehouse?

easy

A. CREATE WAREHOUSE mywh WAREHOUSE_SIZE = 'LARGE';

B. CREATE WAREHOUSE mywh WAREHOUSE_SIZE = 'medium';

C. CREATE WAREHOUSE mywh WITH WAREHOUSE_SIZE = 'XSMALL';

D. CREATE WAREHOUSE mywh SET SIZE = 'SMALL';

Solution

1. Step 1: Check correct syntax for warehouse size

   The correct syntax uses WAREHOUSE_SIZE = 'SIZE' with uppercase size names.

2. Step 2: Validate option correctness

   CREATE WAREHOUSE mywh WAREHOUSE_SIZE = 'LARGE'; uses correct syntax and valid size 'LARGE'. Others have syntax or size errors.

3. Final Answer:

   CREATE WAREHOUSE mywh WAREHOUSE_SIZE = 'LARGE'; -> Option A

4. Quick Check:

   Correct syntax uses WAREHOUSE_SIZE = 'SIZE' [OK]

Hint: Use WAREHOUSE_SIZE = 'SIZE' with uppercase size [OK]

Common Mistakes:

• Using lowercase size names
• Using WITH keyword
• Using SET SIZE instead of WAREHOUSE_SIZE

3. Given a Snowflake warehouse set to size 'MEDIUM' with auto-suspend enabled at 5 minutes, what happens if no queries run for 6 minutes?

medium

A. The warehouse suspends automatically after 5 minutes of inactivity

B. The warehouse continues running indefinitely

C. The warehouse scales up to a larger size automatically

D. The warehouse deletes all cached data

Solution

1. Step 1: Understand auto-suspend behavior

   Auto-suspend pauses the warehouse after the specified inactivity time to save costs.

2. Step 2: Apply to given time

   Since no queries run for 6 minutes, which is more than 5 minutes, the warehouse suspends.

3. Final Answer:

   The warehouse suspends automatically after 5 minutes of inactivity -> Option A

4. Quick Check:

   Auto-suspend triggers after inactivity time [OK]

Hint: Auto-suspend pauses warehouse after set idle time [OK]

Common Mistakes:

• Thinking warehouse keeps running without queries
• Assuming warehouse scales automatically without manual setting
• Confusing auto-suspend with cache clearing

4. You configured a multi-cluster warehouse with MIN_CLUSTER_COUNT=1 and MAX_CLUSTER_COUNT=3, but queries queue up during peak times. What is the likely cause?

medium

A. The warehouse is suspended manually

B. Warehouse size is too large causing delays

C. Auto-suspend is set to zero minutes

D. Auto-scaling is not enabled or configured incorrectly

Solution

1. Step 1: Understand multi-cluster warehouse scaling

   Multi-cluster warehouses scale clusters between min and max counts automatically if auto-scaling is enabled.

2. Step 2: Identify cause of query queuing

   If queries queue despite max clusters > 1, auto-scaling might be off or misconfigured, preventing cluster addition.

3. Final Answer:

   Auto-scaling is not enabled or configured incorrectly -> Option D

4. Quick Check:

   Multi-cluster needs auto-scaling enabled to add clusters [OK]

Hint: Check auto-scaling enabled for multi-cluster warehouses [OK]

Common Mistakes:

• Assuming large warehouse size fixes queuing
• Confusing auto-suspend with scaling
• Not verifying if warehouse is suspended

5. A company wants to handle unpredictable spikes in query load without manual intervention. Which Snowflake warehouse configuration best supports this?

hard

A. Set warehouse size to X-LARGE and disable auto-suspend

B. Create multiple single-cluster warehouses and switch between them manually

C. Use a multi-cluster warehouse with auto-scaling enabled and set MIN_CLUSTER_COUNT=1, MAX_CLUSTER_COUNT=5

D. Set warehouse size to SMALL and rely on auto-resume only

Solution

1. Step 1: Identify need for handling spikes automatically

   The company wants automatic scaling to handle unpredictable query spikes without manual steps.

2. Step 2: Evaluate options for auto-scaling

   Multi-cluster warehouses with auto-scaling and a range of cluster counts allow dynamic scaling up and down.

3. Step 3: Compare other options

   Set warehouse size to X-LARGE and disable auto-suspend wastes resources by disabling suspend; B requires manual switching; D is too small and lacks scaling.

4. Final Answer:

   Use a multi-cluster warehouse with auto-scaling enabled and set MIN_CLUSTER_COUNT=1, MAX_CLUSTER_COUNT=5 -> Option C

5. Quick Check:

   Multi-cluster auto-scaling handles spikes best [OK]

Hint: Multi-cluster with auto-scaling handles spikes automatically [OK]

Common Mistakes:

• Choosing fixed large size wastes cost
• Relying on manual warehouse switching
• Ignoring cluster count settings