During business hours hundreds of short dashboard queries hit one warehouse at once, and many of them queue and wait because the single cluster is saturated, even though each query is small. The team wants queries to stop queuing during these concurrency spikes without making individual queries run on larger compute. Which configuration best addresses this?
- AConfigure the warehouse as a multi-cluster warehouse in auto-scale mode so Snowflake starts extra clusters when queries queue and stops them when demand falls Correct
- BIncrease the warehouse to a larger size so each dashboard query gets more memory and the extra capacity clears the queue during the busy period
- CSet a long statement timeout on the warehouse so queued queries are allowed to wait longer and eventually all run on the existing single cluster
- DLower the auto-suspend setting to zero so the warehouse never suspends and is therefore always warm enough to absorb the concurrency spikes by itself
Why A is correct: A multi-cluster warehouse in auto-scale mode adds clusters when queuing is detected, spreading the concurrent dashboard queries across clusters so they stop waiting, then scales back down.
Why B is wrong: A larger size speeds up each query but still runs them on one cluster with limited concurrency slots, so queries keep queuing under a heavy concurrent load.
Why C is wrong: A longer statement timeout only lets queries wait before being cancelled, so it does not add concurrency and the queue still builds during the spike.
Why D is wrong: Keeping a single-cluster warehouse always running does not add concurrency capacity, so queries still queue when the one cluster is saturated during the spike.