COF-C03 Question 13
Single answerSnowsightA data engineering team has begun using Snowsight for daily work. A junior analyst accidentally ran a long-running transformation query from a worksheet and wants to stop it immediately without waiting for the warehouse statement timeout. The analyst can still access Snowsight but is not sure where to manage the running statement. Which action should the analyst take in Snowsight to cancel the query?
- A
Open Monitoring, locate the running query in Query History, and cancel the query from there
- B
Open Data, navigate to the target table, and use the table preview page to stop active SQL statements
- C
Open Dashboards, find the worksheet tile, and disable refresh to terminate the running statement
- D
Open Projects, duplicate the worksheet, and close the original worksheet to force Snowflake to cancel the query
Show answer and explanation
Correct answer: A
Explanation
This question tests practical use of Snowsight for operational query management. In Snowsight, Monitoring provides access to account activity views such as Query History, where users can inspect execution details and cancel running queries when permitted. This aligns with real-world troubleshooting and warehouse cost control practices. By contrast, Data is for object exploration, Dashboards are for analytics consumption, and Projects/worksheets are for development workflows rather than backend query termination. Candidates should know where to perform common operational tasks in Snowsight, not just how to write SQL.
- A. Correct.
Correct. In Snowsight, running and completed statements can be reviewed in Monitoring, including Query History. Users with the appropriate permissions can identify an active query and cancel it there. This is the practical Snowsight interface for stopping a running statement without relying on timeout settings.
- B. Incorrect.
Incorrect. The Data area is used to explore databases, schemas, tables, views, and object details such as columns and previews. It is not the place to manage or cancel active SQL statements.
- C. Incorrect.
Incorrect. Dashboards are intended for visualizations and shared business insights, not query lifecycle management. Disabling a dashboard refresh does not serve as a general mechanism to cancel an actively running worksheet query.
- D. Incorrect.
Incorrect. Duplicating or closing a worksheet does not reliably cancel a running query on the Snowflake backend. Query execution is managed separately from simply closing the UI tab or worksheet.