Question 80
An analytics engineering team reports this behavior: An inactive database's billed storage increases even though no warehouse currently queries it. What practice should the team establish for future deployments?
Explanation
Correct Answer
This guardrail directly addresses storage cost trend: stored data and retained historical versions incur storage costs independent of active compute. The prevention is: Monitor storage growth and retention alongside compute usage. A separate subsystem check would not prevent the specific recurrence.
Incorrect Answers
Snowflake can evaluate enabled secondary roles as well as the current primary role for authorized operations. “Capture active and secondary role context when investigating effective access” would address that alternative cause, not the condition in this question: stored data and retained historical versions incur storage costs independent of active compute.
“Reconcile warehouse, storage and managed-service cost categories separately” responds to this separate finding: warehouse metering does not include every separately billed serverless service. This question instead needs “Monitor storage growth and retention alongside compute usage”, so the alternative does not meet the stated condition.
Aggregate warehouse charges do not identify the specific expensive queries and users. “Tag workload queries and preserve ownership context for cost attribution” applies to that separate problem. The observed case is an inactive database's billed storage increases even though no warehouse currently queries it; choosing this alternative would address the wrong failure mode.