DAA-C01 Question 243
Single answerCreate charts and dashboard in SnowsightA sales analytics team uses Snowsight to share a dashboard with regional managers. One chart should show monthly revenue trends by region, and another should let users compare the current month against the previous month. The source query already returns MONTH, REGION, REVENUE, and PRIOR_MONTH_REVENUE columns. The team wants the dashboard to be easy to interpret and to refresh directly from the underlying query results in Snowsight without exporting data to another tool. Which approach is the BEST fit for this requirement?
- A
Create a line chart using MONTH on the x-axis and REVENUE as the value, grouped by REGION, then create a separate chart that uses REVENUE and PRIOR_MONTH_REVENUE for side-by-side comparison on the dashboard.
- B
Create a pivot table in Snowsight and pin it directly to the dashboard, because dashboards in Snowsight only support tabular results and not visual charts.
- C
Export the query results to a CSV file and build the visualizations outside Snowsight, because Snowsight dashboards do not refresh from worksheet query results.
- D
Create a single KPI tile in Snowsight showing total revenue, because Snowsight dashboards cannot display both trend and comparison visuals from the same dataset.
Show answer and explanation
Correct answer: A
Explanation
The best answer is to create the needed charts directly in Snowsight from the query result set and add them to a dashboard. In practice, a line chart is well suited for time-series analysis such as monthly revenue trends, and a separate comparison chart helps users evaluate current versus prior period performance. Snowsight supports building charts from worksheet results and organizing them into dashboards for ongoing use. This makes it appropriate for operational analytics scenarios where teams want native visualizations tied to Snowflake data without moving results into another BI tool. Best practice is to choose a chart type that matches the analytical goal: line charts for trends over time, and bar or similar comparison-oriented visuals for side-by-side metric evaluation. This aligns with Snowflake Snowsight capabilities for creating visualizations and dashboards directly from query output.
- A. Correct.
Correct. Snowsight supports creating charts directly from query results in worksheets and adding those visualizations to dashboards. A line chart is an appropriate choice for showing monthly trends over time, especially with MONTH on the x-axis and REGION as a grouping dimension. A separate comparison chart using REVENUE and PRIOR_MONTH_REVENUE is also appropriate when the business wants an easy current-versus-previous-month comparison. This approach keeps the workflow inside Snowsight and aligns with the requirement to refresh from the underlying query results rather than exporting data elsewhere.
- B. Incorrect.
Incorrect. This option reflects a common misconception. Snowsight dashboards can display visualizations such as charts, not just tables or pivoted data. While tabular views can be useful for detail, they are not the only supported dashboard content type, and this option does not best satisfy the requirement for easily interpretable trend and comparison visuals.
- C. Incorrect.
Incorrect. Exporting to CSV and using another tool contradicts the stated requirement to keep the solution in Snowsight and refresh directly from the underlying query results. Snowsight is specifically designed to let users build charts from worksheet result sets and organize them into dashboards without requiring external export for this kind of use case.
- D. Incorrect.
Incorrect. A KPI tile can be useful for a summary metric, but it does not meet the requirement to show both a monthly trend by region and a current-versus-previous-month comparison. The statement that Snowsight cannot display both kinds of visuals from the same dataset is false.