Home / Data Analyst practice test / Working with Dashboards and Visualizations in Databricks / Question

Databricks Data Analyst Associate · free practice question

A Databricks account user who has NOT been added to the workspace is granted CAN EDIT permission on a published dashboard through the Sharing dialog. What is…

Exam-style question on Working with Dashboards and Visualizations in Databricks from the free Data Analyst practice test, with the answer and a full explanation below.

Updated November 10, 2026

Working with Dashboards and Visualizations in Databricks

A Databricks account user who has NOT been added to the workspace is granted CAN EDIT permission on a published dashboard through the Sharing dialog. What is this user's actual effective permission level on the dashboard?

  1. ACAN EDIT as specified, because the Sharing dialog overrides workspace membership requirements and enforces the assigned permission level regardless of whether the user has workspace access
  2. BCAN MANAGE, because the system automatically elevates non-workspace users to the highest permission tier so they can administer the shared dashboard from the account level
  3. CCAN RUN (view-only), because non-workspace users are capped at CAN RUN regardless of any higher level assigned in the Sharing dialog, until workspace access is granted
  4. DNo access at all, because the Sharing dialog prevents elevated permissions from being assigned to users who are not yet workspace members and requires workspace membership before any access is granted
  5. ECAN VIEW read-only mode, which is a special intermediate permission tier automatically applied to account users without workspace access, falling between CAN RUN and CAN EDIT
Answer & explanation

Correct answer: C

WHY C: According to Databricks documentation, users who do not have access to the workspace are limited to CAN RUN permissions. Even if CAN EDIT or higher appears in the Sharing dialog, those elevated permissions are not enforced until the user is added to the workspace. If the user is later added, the assigned permission level takes effect. WHY NOT A: The Sharing dialog does display the assigned permission, but it does not override the workspace membership requirement for elevated permissions; the actual effective permission is CAN RUN. WHY NOT B: Non-workspace users are not elevated to CAN MANAGE; they are capped at CAN RUN, the minimum permission tier for dashboard access. WHY NOT D: The Sharing dialog does allow higher permissions to be assigned to non-workspace users, and the assignments are retained; the elevated permissions simply are not enforced until workspace access is granted. WHY NOT E: CAN VIEW is not a distinct permission tier between CAN RUN and CAN EDIT in the dashboard ACL model; the tier applied to non-workspace account users is CAN RUN.

Take the full Data Analyst practice test free →

Would you pass today?

This question is one of 45 in the free, timed Databricks Data Analyst Associate practice test. Take it and get a section-by-section score.

Start the free test →