DP-750 Certification Practice Question #34

Question

You are a metastore admin acting as the data provider. You must securely share the table `sales.gold.orders` with a partner who already has a Unity Catalog-enabled Azure Databricks workspace (Databricks-to-Databricks sharing). Drag the configuration steps into the correct order, from first to last.

```mermaid
flowchart TB
  subgraph TILES["Steps (unordered)"]
    T1["Create a share object in your Unity Catalog metastore: CREATE SHARE sales_share"]
    T2["Enable Delta Sharing on the Unity Catalog metastore"]
    T3["Grant the recipient access to the share: GRANT SELECT ON SHARE sales_share TO RECIPIENT partner_co"]
    T4["Add the table to the share: ALTER SHARE sales_share ADD TABLE sales.gold.orders"]
    T5["Create a recipient using the partner's metastore sharing identifier: CREATE RECIPIENT partner_co USING ID '...'"]
  end
  subgraph SLOTS["Correct order"]
    S1["Step 1"]
    S2["Step 2"]
    S3["Step 3"]
    S4["Step 4"]
    S5["Step 5"]
  end
```

Accepted Answer

The documented provider workflow starts by enabling Delta Sharing on the Unity Catalog metastore (required to share outside your account), then creating a share object that will hold the data assets. The table is added to that share next (a share with no assets shares nothing). For Databricks-to-Databricks sharing the recipient is created from the partner's metastore sharing identifier — no bearer token is needed. Finally, the provider grants the recipient access with `GRANT SELECT ON SHARE ... TO RECIPIENT ...`; `SELECT` is the only grantable privilege on a share. Each step depends on the prior one (you cannot grant access to a recipient or share that does not yet exist), which fixes the order.

More DP-750 practice questions