Question 130
An organization running Snowflake reports: A finance lead wants to know which workload generated a warehouse spending spike but has only a total monthly bill. Which preventive control would most directly reduce recurrence?
Explanation
Correct Answer
This guardrail directly addresses query attribution by user: aggregate warehouse charges do not identify the specific expensive queries and users. The prevention is: Tag workload queries and preserve ownership context for cost attribution. A separate subsystem check would not prevent the specific recurrence.
Incorrect Answers
The active role does not have the required database and table privileges. “Design access around task-specific roles and test effective privileges with representative users” would address that alternative cause, not the condition in this question: aggregate warehouse charges do not identify the specific expensive queries and users.
“Monitor storage growth and retention alongside compute usage” responds to this separate finding: stored data and retained historical versions incur storage costs independent of active compute. This question instead needs “Tag workload queries and preserve ownership context for cost attribution”, so the alternative does not meet the stated condition.
Warehouse metering does not include every separately billed serverless service. “Reconcile warehouse, storage and managed-service cost categories separately” applies to that separate problem. The observed case is a finance lead wants to know which workload generated a warehouse spending spike but has only a total monthly bill; choosing this alternative would address the wrong failure mode.