SnowPro Associate: Platform Question 21
Single answer● SnowsightA data analyst is using Snowsight to investigate why a dashboard query became slower after a recent schema change. The analyst needs to identify the SQL statement that ran, review its execution details, and share the findings with a senior engineer without giving that engineer direct access to edit the worksheet. Which action in Snowsight best meets this requirement?
- A
Open Query History in Snowsight, locate the statement, review the query profile details, and share the worksheet or saved results with the engineer for review
- B
Use Data Preview on the target table because it shows the full execution plan and can be shared as a read-only troubleshooting artifact
- C
Open the warehouse monitor in Snowsight and increase the warehouse size, because Snowsight cannot display execution details for completed queries
- D
Export the database schema as SQL from Snowsight, because schema export includes the runtime statistics needed to diagnose slow queries
Show answer and explanation
Correct answer: A
Explanation
This scenario focuses on practical use of Snowsight for performance troubleshooting. For a completed query, the correct workflow is to use Query History to identify the statement and then inspect the Query Profile to understand execution behavior. This aligns with Snowflake best practices: investigate the specific query before making infrastructure changes such as resizing a warehouse. Snowsight is designed to support this kind of analysis and collaboration through worksheets, query history, and result sharing. Candidates should distinguish between data inspection features, warehouse monitoring, and query-level troubleshooting tools within Snowsight.
- A. Correct.
Correct. In Snowsight, Query History allows users to find executed SQL statements and inspect execution details, including the query profile for completed queries. This is the appropriate place to analyze why a query slowed down after a schema change. Snowsight also supports sharing worksheets and results in a controlled way, which is more appropriate than granting edit access when the goal is review.
- B. Incorrect.
Incorrect. Data Preview is used to inspect table data, not to analyze execution details of a previously run query. It does not provide a full query execution plan or query profile for troubleshooting performance issues.
- C. Incorrect.
Incorrect. Warehouse monitoring can help identify warehouse load or sizing issues, but it does not replace query-level investigation. Snowsight can display execution details for completed queries through Query History and Query Profile, so increasing warehouse size first would be premature and does not satisfy the requirement to review the exact statement and its execution details.
- D. Incorrect.
Incorrect. Exporting schema definitions may help compare object structures, but it does not include runtime execution statistics for a slow query. Query performance investigation in Snowsight is done through Query History and Query Profile, not schema export.