Exam SnowPro Core topic 1 question 224 discussion

I think that the right answer si C,D. Because the number of bytes scanned has no values if don't know if your query has or not make a prune, reducing the number of partition tha has scanned. I have a good query if my filters reduce the number of (micro) partiotion that the query must access to get the data.

A. Bytes scanned represents the amount of data scanned by the query. By minimizing the number of bytes scanned, query performance can be improved. C. Number of partitions scanned represents the number of partitions read during query execution. By minimizing the number of partitions scanned, query performance can be improved. B, D, and E are incorrect statements. Bytes sent over the network, percentage scanned from cache, and external bytes scanned may provide useful information for monitoring or troubleshooting, but they are not directly related to optimizing query performance.

D & E D: Inefficient Pruning https://docs.snowflake.com/en/user-guide/ui-query-profile.html#inefficient-pruning E: Queries Too Large to Fit in Memory: https://docs.snowflake.com/en/user-guide/ui-query-profile.html#queries-too-large-to-fit-in-memory

C and D are correct

AC is the answer

A. Bytes scanned: This indicates the amount of data scanned from the tables or files involved in the query. By minimizing the number of bytes scanned, you can optimize query performance by reducing the amount of data processed. C. Number of partitions scanned: This represents the number of partitions accessed during the query execution. Optimizing the number of partitions scanned can improve query performance, as accessing fewer partitions typically requires less processing time. So, the correct options are A. Bytes scanned and C. Number of partitions scanned

AC are correct

QUERY RESULT CACHE IS NOT HELPFULL

reference to this question https://community.snowflake.com/s/question/0D7Do000000cglDKAQ/detail

CORRECT

bytes scanned, partition scanned

Should be correct

CD is correct

I would go for AC. The query should not rely on cache.

https://docs.snowflake.com/en/user-guide/ui-query-profile

Number of partitions being scanned (in relation to the total number) -> Pruning Cache usage can significantly boost the performance

AC for me, because bytes scanned and number of partitions scanned referenced in the doc: https://docs.snowflake.com/en/user-guide/ui-query-profile.html#queries-too-large-to-fit-in-memory