A dashboard author publishes a dashboard and wants viewers who do NOT have direct access to the underlying Unity Catalog tables to still see the full dashboard data. Which publishing data permission setting achieves this?
Answer & explanation
Correct answer: B
WHY B: Shared data permissions (the default) cause all viewers to run queries using the publisher's credentials. This allows users who lack direct access to the underlying data or compute to still view the full dashboard. This is explicitly described as the option to 'use when sharing with users who do not have access to the underlying data.' WHY NOT A: Individual data permissions have the opposite effect — viewers use their own credentials, so users without table access would see no data or receive permission errors. WHY NOT C: There is no 'Consumer access entitlement mode' as a publishing option; Consumer access is a workspace entitlement limiting users to read-and-run-only on the dashboard UI, not a bypass of Unity Catalog security. WHY NOT D: There is no workspace-level open permissions setting for catalogs triggered by dashboard publishing; catalog and schema permissions are managed separately in Unity Catalog. WHY NOT E: There is no 'Embedded data permissions' option in the publishing dialog; dashboards always query live data (cached or freshly run), not pre-packaged snapshots.