DAA-C01 Question 264
Single answerTroubleshoot common issues with data analytics dashboard and reportsA data analyst maintains a Snowsight dashboard that is shared with several business users. One chart in the dashboard suddenly shows an error instead of results, while other charts continue to work. The chart is based on a worksheet query that references SALES_DB.PUBLIC.MONTHLY_REVENUE. The analyst can run the worksheet successfully, but business users viewing the dashboard receive an object access error for that chart. The analyst recently changed the dashboard so it runs using the viewer's role instead of the dashboard owner's role. What is the MOST likely cause of the issue?
- A
The business users do not have the necessary privileges on SALES_DB.PUBLIC.MONTHLY_REVENUE when the dashboard executes with the viewer's role.
- B
The warehouse used by the dashboard is too small, so Snowsight blocks only that chart with an object access error.
- C
The MONTHLY_REVENUE object must be recreated as a secure view before it can be used in a shared dashboard.
- D
The worksheet query succeeded for the analyst, so dashboard viewers automatically inherit the analyst's object privileges.
Show answer and explanation
Correct answer: A
Explanation
The key troubleshooting clue is that the issue affects only one chart, the analyst can run the worksheet, viewers get an object access error, and the execution mode was changed to use the viewer's role. In Snowsight, execution context matters: when content runs as the viewer, object-level access is evaluated against the viewer's active role rather than the author's privileges. A practical troubleshooting approach is to verify the dashboard execution setting, then confirm the viewers' role has USAGE on the database and schema plus appropriate SELECT privileges on the underlying table or view. Warehouse sizing would affect performance, not object authorization. Likewise, secure views are not required simply because content is displayed in a dashboard. This aligns with Snowflake best practices around role-based access control and Snowsight dashboard sharing behavior.
- A. Correct.
Correct. When a dashboard is configured to execute using the viewer's role, each viewer must have the required privileges on the underlying objects referenced by the chart query, such as the database, schema, and table or view. If viewers lack access to SALES_DB.PUBLIC.MONTHLY_REVENUE, they can see an object access error for that chart even though the analyst can run it successfully with their own role.
- B. Incorrect.
Incorrect. An undersized warehouse typically leads to performance issues, queueing, or query failures such as timeouts or resource-related errors, not an object access error. The scenario specifically points to permissions because the failure began after switching execution context to the viewer's role.
- C. Incorrect.
Incorrect. Shared dashboards in Snowsight do not require the underlying object to be a secure view. Secure views are used for specific data protection and sharing use cases, but they are not a prerequisite for rendering dashboard charts for internal users with proper privileges.
- D. Incorrect.
Incorrect. This reflects a common misconception. When the dashboard runs with the viewer's role, viewers do not inherit the analyst's privileges. The worksheet running successfully for the analyst only proves the analyst's current role has access, not the viewers' roles.