
Answer-first summary for fast verification
Answer: Configure the warehouse to a multi-cluster warehouse.
The warehouse configuration shows MIN_CLUSTER_COUNT = 1 and MAX_CLUSTER_COUNT = 1, indicating it is currently a single-cluster warehouse. The utilization pattern shows queuing occurs when 4 queries are running, and concurrency reaches up to 6 queries. This suggests the warehouse is hitting cluster capacity limits rather than concurrency limits (default MAX_CONCURRENCY_LEVEL is 8). Option C (configure as multi-cluster warehouse) is optimal because it enables auto-scaling to add clusters when load increases, reducing queuing by distributing queries across multiple clusters. Option B (increase MAX_CONCURRENCY_LEVEL) is less suitable as it may degrade performance by allowing more queries to share limited compute resources. Option A (increase warehouse size) addresses performance but not concurrency queuing efficiently. Option D (lower STATEMENT_QUEUED_TIMEOUT_IN_SECONDS) would cause queries to fail sooner rather than resolve queuing. The community consensus strongly favors C, with the highest upvoted comments explaining that scaling out via multi-cluster is the best solution for concurrency queuing.
Author: LeetQuiz Editorial Team
Ultimate access to all questions.
A virtual warehouse was created with the following command:
CREATE WAREHOUSE my_WH
WITH
WAREHOUSE_SIZE = MEDIUM
MIN_CLUSTER_COUNT = 1
MAX_CLUSTER_COUNT = 1
AUTO_SUSPEND = 60
AUTO_RESUME = TRUE;
CREATE WAREHOUSE my_WH
WITH
WAREHOUSE_SIZE = MEDIUM
MIN_CLUSTER_COUNT = 1
MAX_CLUSTER_COUNT = 1
AUTO_SUSPEND = 60
AUTO_RESUME = TRUE;
The provided image shows a graphical representation of the warehouse utilization over two days. //IMG//
Based on the utilization pattern, what action should be taken to improve the warehouse configuration?

A
Increase the warehouse size from Medium to 2XL.
B
Increase the value for the parameter MAX_CONCURRENCY_LEVEL.
C
Configure the warehouse to a multi-cluster warehouse.
D
Lower the value of the parameter STATEMENT_QUEUED_TIMEOUT_IN_SECONDS.
No comments yet.