Databricks Certified Data Engineer - Associate
Get started today
Ultimate access to all questions.
Deep dive into the quiz with AI chat providers.
We prepare a focused prompt with your quiz and certificate details so each AI can offer a more tailored, in-depth explanation.
Objective: Use the Delta Sharing feature available with Unity Catalog to share data
A data engineer is configuring Delta Sharing for a multi-team project where teams from different departments will need to access shared data. The data engineer has successfully created a Unity Catalog metastore and is now setting up the Delta Share. The goal is to ensure that internal teams can access the data with full permissions, while external partners can only read the shared data.
Which action should the Data Engineer take to configure the sharing?
Exam-Like
Community
UAnonymous
A
Grant READ permissions to external partners through the Delta Share and READ/WRITE permissions to internal teams on Unity Catalog.
B
Create a Delta Share, add the internal team's tables and views, and assign READ/WRITE permissions to both external partners and internal teams.
C
Create READ permissions to external partners and READ/WRITE permissions to internal teams through Delta Share.
D
Create a Delta Share, set up a secure access URL for internal teams and external partners, and distribute the URL to provide them access to the shared data.
Explanation:
Correct answer: A
Explanation:
-
Delta Sharing (using Unity Catalog) is intended to share data with external consumers in a secure, read-only manner. When you create a Delta Share and add tables/views to the share, recipients access the shared data with READ privileges exposed by the share (the share itself provides read-only access to recipients).
-
Internal teams that are part of the same Databricks account and Unity Catalog metastore should be granted their desired permissions (including READ/WRITE) through Unity Catalog object-level access controls (catalog/schema/table permissions). This allows internal users to perform write operations (INSERT/UPDATE/DELETE) which Delta Shares do not allow.
-
Option B is incorrect because it assigns READ/WRITE to external partners (shares are read-only and you shouldn’t grant external partners write privileges via a Delta Share).
-
Option C is incorrect because you cannot grant READ/WRITE permissions to internal teams via a Delta Share; Delta Share recipients get read-only access. Internal write permissions must be granted in Unity Catalog.
-
Option D is incomplete/misleading: while Delta Sharing can use secure endpoints and tokens for external recipients, internal teams should be given Unity Catalog permissions (not merely a share URL) to get full (read/write) access.
Therefore, the correct configuration is to grant external partners READ via the Delta Share and manage internal teams’ READ/WRITE permissions in Unity Catalog.
Comments
Loading comments...