Question 520
An organization running Snowflake reports: A task warehouse resumes for tiny jobs every few seconds, then suspends between them, producing unexpectedly high charges. What observation most directly confirms the correction?
Explanation
Correct Answer
This verifies warehouse startup credits because repeated warehouse resumes can incur minimum billing intervals despite short queries. The corresponding corrective action is: Consolidate appropriately timed work or choose a suspend policy that reduces needless churn. A green status for a different component would not independently establish this result.
Incorrect Answers
Serverless services can consume managed compute independently of a user warehouse. “Review the service-specific billing and scheduling controls rather than relying only on warehouse suspension” would address that alternative cause, not the condition in this question: repeated warehouse resumes can incur minimum billing intervals despite short queries.
“Use a scaling policy aligned with queue-latency requirements and measure the tradeoff” responds to this separate finding: economy scaling may tolerate more queuing to conserve compute credits. This question instead needs “Consolidate appropriately timed work or choose a suspend policy that reduces needless churn”, so the alternative does not meet the stated condition.
The workload lacks sufficient memory and compute for individual query execution. “Benchmark a larger warehouse size and compare runtime and credit use for the query” applies to that separate problem. The observed case is a task warehouse resumes for tiny jobs every few seconds, then suspends between them, producing unexpectedly high charges; choosing this alternative would address the wrong failure mode.