DAA-C01 Question 246
Single answer4.2 Given a use case, maintain reports and dashboards to meet business requirements.A retail analytics team uses Snowsight dashboards backed by Snowflake tables to monitor daily sales by region and product category. Business users report that the dashboard is difficult to maintain because each chart has its own hard-coded date range and regional filter, and updates to one tile often require editing several others. The product owner wants a solution that reduces maintenance effort while allowing business users to adjust the reporting period and region consistently across all visualizations in the dashboard. Which approach should the data analyst implement?
- A
Create dashboard-level filters for date range and region, and configure each tile to use those shared filters
- B
Duplicate each chart for every major region and reporting period so users can switch between prebuilt tiles
- C
Embed the filter logic directly into each worksheet query using separate WHERE clauses and ask owners to update them manually when requirements change
- D
Replace the dashboard with individual worksheets and instruct users to change session variables before opening each report
Show answer and explanation
Correct answer: A
Explanation
The best answer is to use dashboard-level shared filters so that a single control can drive multiple visualizations consistently. For maintaining reports and dashboards to meet evolving business requirements, centralizing common filter inputs improves usability, reduces repetitive query edits, and lowers the risk of mismatched results between tiles. This aligns with Snowsight dashboard best practices, where filters can be applied across dashboard content to support interactive analysis without duplicating report logic. The other options introduce unnecessary operational burden, duplicated assets, or poor user experience, all of which make long-term dashboard maintenance harder rather than easier.
- A. Correct.
Correct. In Snowsight, using shared dashboard filters is the most maintainable approach when multiple tiles need to respond to the same business inputs, such as date range and region. This centralizes control, reduces duplicated logic across tiles, and helps ensure consistent filtering behavior across all dashboard visualizations. It directly addresses the requirement to reduce maintenance effort and support business-driven parameter changes.
- B. Incorrect.
Incorrect. Duplicating charts for each region and period increases dashboard sprawl and significantly raises maintenance overhead. Any logic or formatting change would need to be repeated across many tiles, which is the opposite of the stated business requirement. Although some teams use prebuilt views for common slices, this is not the best solution for flexible, maintainable dashboards.
- C. Incorrect.
Incorrect. Hard-coding or separately embedding filter logic in each query creates inconsistent behavior and high maintenance costs. This is a common anti-pattern in report maintenance because every requirement change must be implemented in multiple places, increasing the chance of errors and making dashboard governance harder.
- D. Incorrect.
Incorrect. Individual worksheets with manual session-variable changes do not provide a cohesive dashboard experience for business users and add operational complexity. Session variables can support parameterized logic in SQL, but requiring users to manage them manually across reports does not meet the need for a maintainable, business-friendly dashboard solution.