Exam SnowPro Core All QuestionsBrowse all questions from this exam
Question 224

In the query profiler view for a query, which components represent areas that can be used to help optimize query performance? (Choose two.)

    Correct Answer: A, C

    Bytes scanned indicates the amount of data read by the query. Minimizing the number of bytes scanned can significantly improve query performance by reducing the volume of data processed. The number of partitions scanned represents the partitions accessed during query execution. Optimizing the number of partitions scanned helps improve performance by limiting the amount of partition data processed. These two components are key areas to focus on when optimizing query performance as they directly affect the query's efficiency and processing time.

Discussion
BigDataBBOptions: CD

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.

bibisaOptions: AC

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.

Lematthew31Options: AC

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

_yyuktaOptions: AC

AC are correct

sfdumpsOptions: AC

QUERY RESULT CACHE IS NOT HELPFULL

OTEOptions: CD

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

KarBiswaOptions: CD

pruning and memory consumption are the two main factors

Mallikharjuna452Options: CD

C and D are correct

PrashantGupta1616Options: AC

AC is the answer

niho1993Options: AC

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

Marge23Options: AC

CORRECT

Marge23Options: AC

bytes scanned, partition scanned

MultiCloudIronManOptions: CD

Should be correct

bonniezlOptions: CD

CD is correct

dmitriypoOptions: AC

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

shyemkoOptions: AD

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

psilvabrOptions: AC

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