DAA-C01 Question 253
Single answerManage and share Snowsight dashboardsA retail analytics team has built a Snowsight dashboard that combines charts from several worksheets in the ANALYTICS database. The dashboard must be shared with regional sales managers who should be able to view the dashboard in Snowsight, but they must not be able to edit the dashboard or access underlying data beyond what their existing Snowflake permissions already allow. The lead data analyst wants the simplest approach that supports ongoing dashboard updates without redistributing links each time. Which action should the analyst take?
- A
Share the dashboard directly with the sales manager role in Snowsight and grant view access to that role
- B
Export the dashboard as a PDF and distribute it by email whenever changes are made
- C
Create a Secure Data Sharing share for the dashboard and add the sales managers as consumers
- D
Grant OWNERSHIP on the dashboard to the sales manager role so they can open it in Snowsight
Show answer and explanation
Correct answer: A
Explanation
The best solution is to share the Snowsight dashboard directly with the appropriate role and grant view access. This aligns with how Snowsight dashboards are intended to be distributed internally for consumption while preserving centralized maintenance by the dashboard author or owner. A key principle is that dashboard sharing does not replace or expand underlying data authorization; users still need the necessary permissions on the referenced objects to see results. This makes role-based dashboard sharing the most practical and secure choice for internal business consumers. By contrast, exporting to PDF removes interactivity and creates versioning overhead, Secure Data Sharing is for database object sharing rather than Snowsight dashboard objects, and granting OWNERSHIP violates least-privilege access design. This follows Snowflake best practices around role-based access control and Snowsight content sharing.
- A. Correct.
Correct. In Snowsight, dashboards can be shared with users or roles for viewing. Granting view access lets recipients open the dashboard in Snowsight without giving them edit capabilities. Access to the underlying data is still governed by existing Snowflake object privileges, so sharing the dashboard does not bypass database, schema, table, or view permissions. This is also the simplest option for ongoing updates because the shared dashboard link remains the same as the owner updates content.
- B. Incorrect.
Incorrect. Exporting to PDF creates a static snapshot, not an interactive Snowsight dashboard experience. It also adds operational overhead because updates require generating and redistributing a new file each time. This does not meet the requirement for an ongoing shared dashboard inside Snowsight.
- C. Incorrect.
Incorrect. Secure Data Sharing is used to share database objects such as tables, views, and secure views across accounts, not to share Snowsight dashboards as dashboard objects. This option reflects a common misconception that all Snowflake content is shared through database shares. Dashboard sharing in Snowsight is managed separately from data sharing features.
- D. Incorrect.
Incorrect. Granting OWNERSHIP is excessive and inappropriate for a view-only use case. OWNERSHIP provides full control and transfer of the object, including management rights, which violates the requirement that sales managers must not be able to edit the dashboard. This also conflicts with least-privilege best practices.