DAA-C01 Question 225
Single answer4.1 Given a use case, create reports and dashboards to meet business requirements.A retail analytics team uses Snowsight to deliver dashboards for regional sales managers. The managers need a dashboard that shows daily sales, profit margin, and order counts by region and product category. They also need to be able to change the date range and limit the view to their assigned region without editing the underlying SQL each time. The dashboard will be refreshed regularly and viewed by non-technical users. Which approach best meets these business requirements?
- A
Create a Snowsight dashboard from worksheets that use SQL with dashboard filters and input parameters for date range and region, then share the dashboard with the intended users.
- B
Create a secure view for each regional manager and ask each manager to run ad hoc SQL queries in Snowsight whenever they need updated metrics.
- C
Export query results to CSV files every day and distribute them by email so managers can filter the data locally in spreadsheet software.
- D
Build a single worksheet with hard-coded date filters and region values, then instruct users to duplicate and edit the SQL whenever they need a different view.
Show answer and explanation
Correct answer: A
Explanation
The best answer is to use Snowsight dashboards built from worksheets with interactive controls such as filters or parameters so consumers can adjust the date range and regional scope without rewriting SQL. This matches the business need for governed, reusable, regularly refreshed reporting for non-technical users. In Snowflake, Snowsight is designed to support visualizations and dashboards directly on top of query results, making it appropriate for operational and analytical reporting use cases. Best practice is to centralize report logic, expose only the necessary controls to users, and avoid distributing static extracts or requiring end users to modify SQL. Where regional data restriction is also required, that can be implemented through Snowflake access controls and data-model design, but the reporting requirement itself is best addressed through an interactive Snowsight dashboard.
- A. Correct.
Correct. Snowsight supports building dashboards from worksheets and using filters/interactive controls so business users can adjust common parameters such as date range and region without modifying SQL directly. This approach aligns with the requirement for a regularly refreshed, user-friendly dashboard for non-technical consumers. It also supports centralized maintenance of the logic instead of distributing many separate report definitions.
- B. Incorrect.
Incorrect. Secure views can help restrict data access, but this option does not meet the reporting usability requirement because it expects non-technical users to run ad hoc SQL themselves. The need is for interactive dashboards and reports, not manual query execution. Candidates may choose this because row-level restriction sounds relevant, but it does not address dashboard interactivity or ease of use.
- C. Incorrect.
Incorrect. CSV exports are static snapshots and move reporting outside Snowsight. This breaks the requirement for regularly refreshed dashboards and creates version-control and governance problems. While spreadsheets allow filtering, they are not the best solution for centralized, governed dashboards tied directly to Snowflake data.
- D. Incorrect.
Incorrect. Hard-coding filters into a worksheet does not satisfy the requirement for users to change date range and region without editing SQL. It also creates maintenance overhead and increases the likelihood of inconsistent logic across duplicated worksheets. This is a common but poor workaround when interactive dashboard features should be used instead.