Data Analyst Associate · Domain 9: Securing Data · 8% of the exam
Task 9.1: Use Unity Catalog roles and sharing settings to ensure workspace objects are secure; Understand how the 3-level namespace (Catalog / Schema / Tables or Volumes) works in the Unity Catalog
Admin roles, privileges and their inheritance down the three-level namespace, USE CATALOG and USE SCHEMA, workspace object permissions, and share and recipient access.
Study it
Unity Catalog privileges, the three-level namespace and sharing settings
Try each one before opening the answer. Every option is explained, with the Databricks documentation page that proves it.
Question 1 · choose 1
The folder /Workspace/Shared/finance-reports holds alerts and dashboards, and more are added every month. The finance-analysts group must be able to run all of them, now and later, but must not edit them or change their permissions. What should a workspace admin do?
AGrant the group CAN RUN on each alert and dashboard in the folder today
BGrant the group CAN MANAGE on the folder
CMake them workspace admins
DGrant the group CAN RUN on the folder
Show the answer and why
AGrant the group CAN RUN on each alert and dashboard in the folder today
Incorrect
Grants on today's objects do not cover objects added to the folder later.
BGrant the group CAN MANAGE on the folder
Incorrect
CAN MANAGE goes beyond running: it also allows editing the objects.
CMake them workspace admins
Incorrect
Workspace admins have CAN MANAGE on all objects in the workspace, far more than running reports.
DGrant the group CAN RUN on the folder
Correct
Objects in a folder inherit all permission settings of the folder, so CAN RUN on the folder applies to current and future objects in it.
Workspace object permissions can be managed through folders: objects in a folder inherit the folder's permission settings, for example CAN RUN on a folder gives CAN RUN on the alerts in it. CAN MANAGE adds editing, and workspace admins have CAN MANAGE on every object.
In workspace A, SELECT * FROM sales.orders returns European orders; in workspace B, attached to the same Unity Catalog metastore, the same statement returns American orders. Neither user ran USE CATALOG. What explains this?
AEach workspace has its own default catalog, which is used when the catalog name is left out
BUnity Catalog searches every catalog for a schema named sales and uses the first one it finds
CTwo-level names are not valid in Unity Catalog, so one of the queries must have failed
DEach workspace keeps a private copy of the metastore's tables
Show the answer and why
AEach workspace has its own default catalog, which is used when the catalog name is left out
Correct
A default catalog is configured for each workspace; when the top-level catalog name is omitted, the default catalog is assumed.
BUnity Catalog searches every catalog for a schema named sales and uses the first one it finds
Incorrect
Names without a catalog resolve against the default catalog, not by a search across catalogs.
CTwo-level names are not valid in Unity Catalog, so one of the queries must have failed
Incorrect
Data operations can omit the catalog; the default catalog is then assumed.
DEach workspace keeps a private copy of the metastore's tables
Incorrect
Workspaces attached to a metastore share its catalogs; the difference comes from the default catalog.
Unity Catalog names objects with a three-level namespace, catalog.schema.object. Each Unity Catalog-enabled workspace has a default catalog that is assumed when a statement omits the catalog, so a two-level name can point to different tables in different workspaces. Use the full three-level name or USE CATALOG to be explicit.
A provider wants to grant a recipient access to an OpenSharing (Delta Sharing) share. Which permissions does Databricks list for the user who does it, if that user owns neither object?
ASELECT on every table that the share contains, with USE SCHEMA
BWorkspace admin rights only
CCREATE CATALOG on the metastore
DUSE SHARE and SET SHARE PERMISSION, plus USE RECIPIENT
Show the answer and why
ASELECT on every table that the share contains, with USE SCHEMA
Incorrect
Granting share access is governed by privileges on the share and the recipient objects.
BWorkspace admin rights only
Incorrect
The page lists a metastore admin or delegated permissions or ownership on the share and recipient; workspace admin rights are not among them.
CCREATE CATALOG on the metastore
Incorrect
CREATE CATALOG does not let a user grant share access.
DUSE SHARE and SET SHARE PERMISSION, plus USE RECIPIENT
Correct
The user needs USE SHARE plus SET SHARE PERMISSION (or share ownership) and USE RECIPIENT (or recipient ownership).
To grant a recipient access to a share, a user needs delegated permissions or ownership on both objects: USE SHARE and SET SHARE PERMISSION, or ownership, on the share, and USE RECIPIENT, or ownership, on the recipient.
A workspace folder named Reorg 2027 holds several notebooks. An analyst is given CAN VIEW on one notebook in it and no permissions on the folder. What can she see of the folder?
AIts name, but none of the other objects stored in it
BEvery notebook stored in it
CNothing at all; the notebook's location stays hidden from her
DIts name and the names of its other notebooks, without their cells
Show the answer and why
AIts name, but none of the other objects stored in it
Correct
A user with access to an object in a folder can view the parent folder's name, but not the folder's other objects.
BEvery notebook stored in it
Incorrect
She cannot view or access the other objects unless she is granted permissions on them.
CNothing at all; the notebook's location stays hidden from her
Incorrect
The folder's name is visible to a user who has access to an object in it.
DIts name and the names of its other notebooks, without their cells
Incorrect
Listing the objects in a folder needs a permission on the folder itself.
If you grant a user access to an object inside a folder, the user can view the parent folder's name even without permissions on the folder, but cannot view or access its other objects unless granted permissions on them. Listing a folder's objects needs a permission on the folder.
A data steward wants a group to read files in every volume of the schema main.raw, including volumes created later, without granting each volume separately. What does the documentation allow?
AGranting SELECT on each volume as it is created
BGranting READ VOLUME on the schema main.raw, which cascades to its volumes
CGranting MODIFY on the catalog main
DMaking the group owner of each volume
Show the answer and why
AGranting SELECT on each volume as it is created
Incorrect
Volume access uses READ VOLUME, and it can be set at a higher level to cascade.
BGranting READ VOLUME on the schema main.raw, which cascades to its volumes
Correct
Privileges such as READ VOLUME can be set at the catalog or schema level to cascade to all contained volumes.
CGranting MODIFY on the catalog main
Incorrect
MODIFY concerns changing table data, not reading files in volumes.
DMaking the group owner of each volume
Incorrect
Ownership is far broader than reading files and must be set per volume.
Volume privileges focus on working with files: READ VOLUME and WRITE VOLUME. Owners get all privileges on a volume, and READ VOLUME or WRITE VOLUME can be set at the catalog or schema level to cascade to all contained volumes.