Question 30
During a Snowflake architecture review, the team finds: Repeated inserts make an enormous time-series table poorly clustered on the customer and event-time filters used by critical queries. Which design safeguard best addresses the observed risk?
Explanation
Correct Answer
This guardrail directly addresses cluster depth observation: related key ranges overlap broadly across micro-partitions and reduce pruning efficiency. The prevention is: Reassess clustering benefits on large frequently filtered tables using real workload metrics. A separate subsystem check would not prevent the specific recurrence.
Incorrect Answers
Snowflake creates new micro-partitions for changed data while older versions may remain for retention. “Include data modification and retention effects when estimating storage growth” would address that alternative cause, not the condition in this question: related key ranges overlap broadly across micro-partitions and reduce pruning efficiency.
“Distinguish metadata operations from data queries in cost and troubleshooting playbooks” responds to this separate finding: metadata services maintain object definitions and privileges separately from raw table scans. This question instead needs “Reassess clustering benefits on large frequently filtered tables using real workload metrics”, so the alternative does not meet the stated condition.
Query compilation and authentication depend on cloud services rather than on storage alone. “Monitor cloud services availability separately from storage and warehouse activity” applies to that separate problem. The observed case is repeated inserts make an enormous time-series table poorly clustered on the customer and event-time filters used by critical queries; choosing this alternative would address the wrong failure mode.