Question 340
An analytics engineering team reports this behavior: A dashboard team chooses the multi-cluster Economy scaling policy but expects clusters to start immediately at the first brief queue spike. Which underlying issue should be investigated first?
Explanation
Correct Answer
The described symptoms indicate that Economy scaling may tolerate more queuing to conserve compute credits. The appropriate resolution is: Use a scaling policy aligned with queue-latency requirements and measure the tradeoff. Confirm with: Peak-time warehouse load shows wait times within agreed limits at acceptable credits.
Incorrect Answers
The chosen warehouse configuration is not suitable for its memory-intensive Snowpark processing. “Evaluate a compatible Snowpark-optimized or larger warehouse for the measured workload” would address that alternative cause, not the condition in this question: economy scaling may tolerate more queuing to conserve compute credits.
“Evaluate a suitable auto-suspend interval and monitor data scanned from cache before changing data design” responds to this separate finding: a suspended warehouse loses its local data cache and must warm it again. This question instead needs “Use a scaling policy aligned with queue-latency requirements and measure the tradeoff”, so the alternative does not meet the stated condition.
The warehouse lacks enough concurrent cluster capacity for peak users. “Evaluate a multi-cluster warehouse under the supported edition and scaling policies” applies to that separate problem. The observed case is a dashboard team chooses the multi-cluster Economy scaling policy but expects clusters to start immediately at the first brief queue spike; choosing this alternative would address the wrong failure mode.