Correct Answer: A
The correct answer is A. By inspecting the statistics pane in the Query Profile .
The Query Profile provides execution details for a query. To evaluate micro-partition pruning, users can inspect scan statistics, including partitions scanned versus total partitions. This helps determine whether Snowflake is efficiently skipping unnecessary micro-partitions.
Why A is correct:
The Query Profile statistics pane can show how many partitions were scanned and how many total partitions existed. Efficient pruning means Snowflake scanned only a small portion of the total relevant micro-partitions.
Example interpretation:
Partitions scanned: 100
Partitions total: 10,000
This indicates strong pruning because Snowflake skipped most micro-partitions.
Why the other options are incorrect:
B). Query details in Snowsight provide useful metadata such as duration, warehouse, and query text, but the Query Profile statistics pane is the best place to validate pruning efficiency.
C). SYSTEM$CLUSTERING_INFORMATION() gives clustering information for a table, such as clustering depth and overlap, but it does not directly show whether a specific query pruned efficiently.
D). INFORMATION_SCHEMA.TABLES provides table metadata, not query-level partition pruning details.
Official Snowflake documentation reference:
Snowflake documentation explains that Query Profile provides detailed execution information, including table scan statistics such as partitions scanned and partitions total. These statistics help validate pruning effectiveness.
Reference: Snowflake Documentation - Query Profile; Snowflake Documentation - Table scan statistics; Snowflake Documentation - Micro-partitions and pruning; SnowPro Core Study Guide - Performance Optimization.
==