Question 170
A Snowflake administrator investigates the following production situation: A team designs a routine that manually chooses physical file partitions for every insert into a native Snowflake table. What practice should the team establish for future deployments?
Explanation
Correct Answer
This guardrail directly addresses micro-partition organization: Snowflake automatically organizes supported native table data into micro-partitions. The prevention is: Review physical design through partition pruning evidence rather than hand-managed files. A separate subsystem check would not prevent the specific recurrence.
Incorrect Answers
Snowflake managed table storage is separate from the lifecycle of a particular warehouse. “Test data availability independently of individual warehouse suspend and resume operations” would address that alternative cause, not the condition in this question: snowflake automatically organizes supported native table data into micro-partitions.
“Include data modification and retention effects when estimating storage growth” responds to this separate finding: snowflake creates new micro-partitions for changed data while older versions may remain for retention. This question instead needs “Review physical design through partition pruning evidence rather than hand-managed files”, 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 a team designs a routine that manually chooses physical file partitions for every insert into a native Snowflake table; choosing this alternative would address the wrong failure mode.