SnowPro Associate: Platform Question 41
Single answer1.3 Describe how to use the Snowsight user interface.A data analyst is new to Snowflake and wants to use Snowsight to investigate slow-running queries from a shared worksheet. They need to review the query history, inspect execution details for a specific statement, and then rerun that statement after switching to a larger warehouse for testing. Which Snowsight workflow best meets this requirement?
- A
Open Monitoring or Query History in Snowsight to locate the statement, view its query details, then open or rerun it in a worksheet after selecting a larger warehouse from the worksheet context.
- B
Use Data » Databases to find the table involved, then change the table type to temporary so Snowsight automatically reruns the slow query on a larger warehouse.
- C
Open the Users & Roles area in Snowsight, assign the analyst a higher role, and Snowsight will recalculate the previous query with more compute resources.
- D
Go to Admin » Warehouses, resize the warehouse used by the original query, and Snowsight will retroactively update the execution details for the completed statement.
Show answer and explanation
Correct answer: A
Explanation
This question tests practical use of the Snowsight interface rather than memorization of menu names. In real-world troubleshooting, a user commonly starts with Query History or Monitoring to find a slow statement, reviews the statement's details, and then reruns the SQL from a worksheet while selecting an appropriate warehouse. Snowsight supports switching the active role, warehouse, database, and schema in the worksheet context for subsequent executions. By contrast, object browsing in Data, role changes in Users & Roles, or resizing a warehouse after a query completes do not retroactively alter the original query's execution record. This aligns with Snowflake documentation describing Snowsight features for worksheets, query history, and warehouse management.
- A. Correct.
Correct. In Snowsight, users can review query history and inspect details for executed statements, including execution-related information. They can then open or rerun SQL in a worksheet and choose a different current warehouse in the worksheet context before executing again. This reflects a practical Snowsight workflow for investigating and testing query performance.
- B. Incorrect.
Incorrect. The Data area is used to explore databases, schemas, tables, and other objects, but changing a table to temporary is not a valid performance troubleshooting action for rerunning an existing slow query. Snowsight does not automatically rerun queries based on table type changes.
- C. Incorrect.
Incorrect. Users & Roles is for security and access management tasks, not for query performance testing. Assigning a higher role may change object access, but it does not increase compute resources or rerun a prior statement with a larger warehouse.
- D. Incorrect.
Incorrect. Resizing a warehouse can affect future query executions, but it does not retroactively change the execution details of a query that has already completed. To test performance on a larger warehouse, the query must be run again.