COF-C03 Question 14
Single answerSnowsightA data engineering team uses Snowsight to investigate rising warehouse costs. An engineer wants to create a dashboard tile that shows daily credits consumed by each warehouse over the last 30 days and refreshes as new usage data becomes available. The engineer also wants other team members to view the visualization without editing the underlying SQL. Which approach best meets these requirements in Snowsight?
- A
Run a query against ACCOUNT_USAGE.WAREHOUSE_METERING_HISTORY in a Snowsight worksheet, create a chart from the results, and add the chart to a dashboard that can be shared for viewing.
- B
Create a stage, export warehouse usage to CSV files daily, and use Snowsight to upload the files into a dashboard tile because dashboards require staged files as a data source.
- C
Use Classic Console to build the visualization because Snowsight dashboards do not support charts based on SQL query results.
- D
Create a temporary table with warehouse usage data and email screenshots daily, because Snowsight dashboards cannot be viewed by other users unless they can edit the SQL worksheet.
Show answer and explanation
Correct answer: A
Explanation
The best answer is to use Snowsight worksheets and dashboards directly. A common real-world pattern is to query SNOWFLAKE.ACCOUNT_USAGE views, including WAREHOUSE_METERING_HISTORY, to analyze credit usage trends. In Snowsight, query results can be turned into charts and added to dashboards for ongoing monitoring. This aligns with Snowflake best practices of using ACCOUNT_USAGE for account-level historical monitoring and using Snowsight for collaborative analysis and visualization. The incorrect answers reflect common misconceptions: that dashboards require files instead of SQL result sets, that Snowsight lacks charting/dashboard functionality, or that sharing visualizations requires recipients to edit the underlying worksheet.
- A. Correct.
Correct. In Snowsight, a user can run SQL in a worksheet, visualize the result set as a chart, and add that chart to a dashboard. Querying usage views such as SNOWFLAKE.ACCOUNT_USAGE.WAREHOUSE_METERING_HISTORY is a practical way to analyze warehouse credit consumption over time. Dashboards are intended for sharing visual insights, and viewers do not need to edit the underlying SQL just to consume the dashboard.
- B. Incorrect.
Incorrect. Snowsight dashboards do not require staged CSV files as a source. This option describes an unnecessary manual export/import workflow and misunderstands how Snowsight visualizations are created. In practice, dashboard charts are commonly built directly from SQL query results in worksheets.
- C. Incorrect.
Incorrect. This is based on a false limitation. Snowsight is the modern Snowflake web interface and supports creating charts from worksheet query results and organizing them into dashboards. A candidate might choose this if they confuse older UI capabilities with current Snowsight functionality.
- D. Incorrect.
Incorrect. Creating screenshots is not an appropriate solution for a dashboarding requirement, and the statement about other users being unable to view dashboards without editing SQL is inaccurate. Snowsight dashboards are specifically designed to present shared visualizations without requiring recipients to modify the source query.