DAA-C01 Question 226
Single answer4.1 Given a use case, create reports and dashboards to meet business requirements.A retail analytics team uses Snowsight dashboards to monitor daily sales performance across regions. Executives want a dashboard that opens with a company-wide KPI summary, but also lets regional managers quickly focus on only their own region without editing the underlying SQL for each chart. The dashboard must support consistent filtering across multiple tiles and be easy to maintain as reporting needs change. Which approach best meets these requirements?
- A
Create separate dashboards for each region, and hard-code a WHERE clause for the region in every query used by each dashboard tile.
- B
Create one dashboard with charts based on reusable worksheets or SQL queries, and add dashboard-level filters so users can interactively filter all relevant tiles by region.
- C
Build one dashboard and duplicate each chart once per region so users can scroll to the section for their region.
- D
Create a dashboard from ad hoc query results only, and instruct regional managers to edit the SQL text in each tile when they need to focus on their region.
Show answer and explanation
Correct answer: B
Explanation
The best practice for this use case is to create a single Snowsight dashboard that uses reusable queries or worksheets as its source and applies dashboard-level filters to support consistent interactivity across multiple visualizations. This aligns with common analytics design principles: minimize duplication, centralize query logic, and provide governed self-service filtering for end users. Separate dashboards or duplicated charts increase maintenance burden and make it harder to keep business logic consistent. Requiring users to edit SQL is also inappropriate for report consumers and does not satisfy the business requirement. Snowflake Snowsight documentation describes creating dashboards from worksheets and using filters to refine dashboard views, which supports this scalable and maintainable reporting pattern.
- A. Incorrect.
This approach is not the best fit because it creates significant maintenance overhead and duplicates logic across dashboards. Hard-coding region filters into separate dashboards makes it harder to support executive company-wide views and increases the effort required when metrics or visualizations change. Although technically possible, it does not meet the requirement for easy maintenance and interactive filtering.
- B. Correct.
This is the best answer. In Snowsight, dashboards can be built from queries/worksheets and support filters that can be applied across multiple tiles, allowing consumers to interactively focus on a region without modifying SQL. This approach supports both the executive need for a company-wide default view and the regional manager need for drill-in filtering, while improving maintainability through reuse of underlying queries.
- C. Incorrect.
This is a plausible but poor design choice. Duplicating charts for every region increases clutter and makes the dashboard harder to use and maintain. It also does not provide a clean, interactive filtering experience across multiple tiles. Users would need to navigate a much larger dashboard instead of applying a simple region filter.
- D. Incorrect.
This is incorrect because it shifts report customization to dashboard consumers and requires manual SQL changes, which is not appropriate for business users. It also undermines governance, consistency, and usability. The requirement explicitly states that users should not need to edit the underlying SQL for each chart.