SnowPro Advanced: Architect — Question 112
A Snowflake Architect anticipates that a table will contain several terabytes of data, and so defines a custom cluster key of three columns to optimize query performance. However, the table still takes a long time to query.
Why is this occurring?
Answer options
- A. A multi-cluster virtual warehouse is not being used.
- B. The cluster key should not exceed two columns.
- C. The custom cluster key cardinality is too high.
- D. The table needs to be manually reclustered to partition the key.
Correct answer: C
Explanation
The correct answer is C because a high cardinality in the custom cluster key can lead to inefficient data organization, slowing down query performance. Option A is incorrect as using a multi-cluster virtual warehouse doesn't directly relate to cluster key performance. Option B is false since cluster keys can include more than two columns, and option D is not necessarily true, as reclustering may not be required if the key is already optimally defined.