ADA-C01 Question 287
Single answerIdentify constraints with sharing a Snowsight chartA Snowflake administrator created a Snowsight chart from a worksheet that queries a secure view in the ANALYTICS database. The administrator wants to send the chart to several business users by using Snowsight sharing so the users can explore the visualization directly. However, some recipients report that they cannot open the chart, while others can open it but do not see current results after the underlying data changes. Which statement best explains these sharing constraints?
- A
Snowsight charts can be shared with any email recipient, but only ACCOUNTADMIN can refresh the chart results after the initial share.
- B
Recipients must have access to the underlying objects and appropriate privileges in Snowflake, and shared charts are not a substitute for granting data access.
- C
A shared Snowsight chart automatically exposes only the rendered image, so recipients do not need a Snowflake user account or permissions on the source data.
- D
If the chart was created from a secure view, Snowsight blocks all sharing of that chart regardless of role privileges.
Show answer and explanation
Correct answer: B
Explanation
This question tests a practical administrator concern: sharing a Snowsight chart does not bypass Snowflake security. Snowsight is governed by Snowflake RBAC, so users opening a shared chart must still have the required privileges to the underlying objects referenced by the worksheet or query. Administrators commonly assume that sharing a chart is similar to sending a static BI artifact, but Snowsight sharing is constrained by account access and object privileges. If recipients lack privileges on the source view, database, schema, or warehouse, they may be unable to open the chart or refresh/query current results. This aligns with Snowflake documentation and best practices around Snowsight sharing and role-based access control: access to visualizations depends on access to the underlying data and execution context, rather than the share action alone.
- A. Incorrect.
Incorrect. Snowsight chart sharing is not an email-based public sharing feature that bypasses Snowflake access control. Recipients generally need to be able to access Snowsight in the account and have the necessary permissions to the underlying data. There is also no special rule that only ACCOUNTADMIN can refresh shared chart results.
- B. Correct.
Correct. A key constraint of sharing a Snowsight chart is that sharing the chart does not override Snowflake's RBAC model. Users who receive access to the chart still need the required privileges on the underlying database objects used by the worksheet or chart. In practice, this means a chart share may fail for users without access to the source database, schema, view, table, warehouse, or other required objects. It also explains why recipients may not see usable or current results if they cannot run the underlying query in their own security context.
- C. Incorrect.
Incorrect. This describes a common misconception: that chart sharing is similar to publishing a static dashboard externally. Snowsight chart sharing is not an anonymous or public rendering mechanism. It does not remove the need for a Snowflake account, Snowsight access, or permissions on the source data objects.
- D. Incorrect.
Incorrect. The use of a secure view does not by itself prohibit chart sharing. The real constraint is still privilege-based access. If recipients have the necessary permissions to use the secure view and supporting objects, they can access the chart. Secure views protect underlying logic and data exposure, but they do not categorically block Snowsight chart sharing.