SnowPro Associate: Platform Question 24
Single answer● SnowsightA data analyst is using Snowsight to investigate a dashboard query that is running slowly in production. The analyst does not have ACCOUNTADMIN privileges but does have permission to use the warehouse and query history views available to their role. They want to identify which queries are consuming the most time and review the SQL text and execution details without leaving Snowsight. Which Snowsight feature should the analyst use?
- A
Use the Query History page in Snowsight to filter recent queries, inspect duration, and open the query details for the SQL text and execution information
- B
Use the Data loading wizard in Snowsight because it shows file ingestion history and all SQL statements that affect dashboard performance
- C
Use the Worksheets page only, because Snowsight does not provide query execution details outside an active worksheet session
- D
Use the User Profile page in Snowsight, because it provides account-wide query tuning recommendations and complete SQL execution plans
Show answer and explanation
Correct answer: A
Explanation
In Snowsight, Query History is the appropriate feature for investigating slow-running queries when the user has the necessary permissions to view query history. It allows users to review recent statements, identify long-running queries, and inspect details such as the SQL text and execution metadata. This aligns with common Snowflake operational practice: use Snowsight monitoring and history views for troubleshooting rather than unrelated interfaces like data loading or user settings. Snowflake documentation for Snowsight and query monitoring describes using query history and query details to analyze executed statements, durations, and related execution information.
- A. Correct.
Correct. Snowsight includes a Query History experience that lets authorized users review executed queries, filter and sort them, and open query details such as SQL text, timing, and other execution-related information. This is the most direct way in Snowsight to investigate slow-running queries in a realistic troubleshooting scenario.
- B. Incorrect.
Incorrect. The data loading interface in Snowsight is for loading data and reviewing load-related activity, not for general dashboard query performance analysis. Someone might choose this if they confuse ingestion history with overall query history, but it does not serve as the primary tool for investigating slow analytical SQL queries.
- C. Incorrect.
Incorrect. Worksheets are used to write and run SQL, but Snowsight is not limited to viewing execution information only inside a worksheet. Query History is a separate feature specifically intended for reviewing previously executed queries. This option reflects the misconception that historical troubleshooting must happen only where the query was originally written.
- D. Incorrect.
Incorrect. The User Profile page is not the place for account-wide query tuning analysis or complete execution plans. A user might pick this because profile/settings areas often contain personal usage information, but query performance investigation in Snowsight is handled through query monitoring and history features, not profile pages.