DAA-C01 Question 258
Single answerPresent data for business-use analysesA retail analytics team uses Snowsight to review weekly sales trends and wants a business-facing view that non-technical users can consume without writing SQL. They need a reusable visual that shows sales by week and product category, supports simple filtering, and can be shared with other internal users who already have Snowflake access. The analyst wants to minimize maintenance and keep the data directly in Snowflake. Which approach best meets these requirements?
- A
Create a Snowsight dashboard from SQL worksheets and charts, then share the dashboard with internal Snowflake users.
- B
Export query results to CSV each week and distribute the files through an external file-sharing platform.
- C
Create a secure data share containing the base tables so business users can build their own visualizations in any SQL client.
- D
Build a Python stored procedure that renders charts and writes image files to an internal stage for users to download.
Show answer and explanation
Correct answer: A
Explanation
For presenting data for business-use analyses directly in Snowflake, Snowsight dashboards are the most appropriate choice in this scenario. Snowsight allows analysts to build visualizations from worksheet queries, add filters, and organize charts into dashboards that can be shared with internal users. This supports governed, current, low-maintenance presentation of analytical results without requiring business consumers to write SQL. By contrast, CSV exports break interactivity and governance, secure data sharing is about data access rather than presentation, and stored procedures are not intended to serve as a dashboarding framework. This aligns with Snowflake best practices around using Snowsight for native visualization and dashboarding when the goal is to present analytical data to business users within Snowflake.
- A. Correct.
Correct. Snowsight supports creating charts from query results and assembling them into dashboards for interactive, business-friendly consumption. This approach keeps the data in Snowflake, reduces operational overhead compared to manual exports, and allows sharing with internal Snowflake users who already have access. It is well aligned with presenting governed analytical results for business use without requiring end users to write SQL.
- B. Incorrect.
Incorrect. Exporting results to CSV is manual or requires separate orchestration, creates version-control and freshness issues, and removes the analysis from Snowflake's governed environment. While it may work for ad hoc distribution, it does not provide a reusable, interactive, low-maintenance presentation layer for business users.
- C. Incorrect.
Incorrect. Secure data sharing is intended for sharing database objects between Snowflake accounts without copying data, not for delivering a ready-to-consume business presentation layer. It also assumes users will build their own analysis, which does not satisfy the requirement for a reusable visual that non-technical users can consume directly.
- D. Incorrect.
Incorrect. Stored procedures are not the appropriate Snowflake-native mechanism for producing and distributing business dashboards. Writing chart images to a stage adds unnecessary complexity, provides limited interactivity, and is not a standard best practice for presenting business-use analyses in Snowflake.