SOL-C01 Question #83: Real Exam Question with Answer & Explanation

Question

You are tasked with optimizing a Snowflake query that frequently uses the 'SALES' table. This table has a large number of rows, and users often filter the data based on the 'ORDER DATE column. You decide to create a clustering key on the 'ORDER DATE column. After creating the clustering key, you notice that the query performance has not improved as expected. What are the potential reasons for this lack of improvement?

Options

• AThe 'ORDER_DATE column has low cardinality, making clustering ineffective.
• BThe automatic clustering process has not yet completed re-clustering the table after the clustering
• CThe queries being executed are not filtering on the 'ORDER DATE column, thus not leveraging the
• DThe table is too small for clustering to provide a significant performance benefit.
• EThe table is not being maintained correctly, leading to high micro-partition fragmentation.

Explanation

Clustering works best when the column has high cardinality. If the automatic clustering has not completed the reclustering of the table after the clustering key was defined, it might have not taken effect yet. If the queries aren't filtering on the ORDER_DATE column then the clustering wont have effect. Clustering is more effective on larger tables with high cardinality, and on queries that use filter that leverage the clustering keys. High Fragmentation of micro-partition may affect the query peformance after reclustering is completed.

No community discussion yet for this question.