Question 440
A Snowflake administrator investigates the following production situation: A product owner assumes one warehouse resource monitor will enforce a global ceiling for every serverless feature and storage byte. What is the principal technical cause in this scenario?
Explanation
Correct Answer
The described symptoms indicate that warehouse resource monitors do not provide universal spend control for all Snowflake services. The appropriate resolution is: Apply a resource monitor to eligible warehouse usage and separately manage other service budgets. Confirm with: Warehouse actions trigger at the expected credit threshold while other expenses remain separately tracked.
Incorrect Answers
The session has no running compute and the warehouse will not automatically restart. “Resume the approved warehouse or enable auto-resume where governance allows it” would address that alternative cause, not the condition in this question: warehouse resource monitors do not provide universal spend control for all Snowflake services.
“Review the service-specific billing and scheduling controls rather than relying only on warehouse suspension” responds to this separate finding: serverless services can consume managed compute independently of a user warehouse. This question instead needs “Apply a resource monitor to eligible warehouse usage and separately manage other service budgets”, so the alternative does not meet the stated condition.
Economy scaling may tolerate more queuing to conserve compute credits. “Use a scaling policy aligned with queue-latency requirements and measure the tradeoff” applies to that separate problem. The observed case is a product owner assumes one warehouse resource monitor will enforce a global ceiling for every serverless feature and storage byte; choosing this alternative would address the wrong failure mode.