You need to share a Unity Catalog-managed dataset with another organization that also uses a Unity Catalog-enabled Databricks workspace. You also want to share a notebook and a Unity Catalog volume along with the tables, and you do not want to manage long-lived bearer tokens for the recipient. Which Delta Sharing model best fits these requirements?
Answer & explanation
Correct answer: D
WHY D: Databricks-to-Databricks Delta Sharing is designed for sharing between Unity Catalog-enabled Databricks workspaces (often across accounts/clouds). It supports assets not available in open sharing (for example notebook files and Unity Catalog volumes) and avoids provider-managed bearer tokens by using the Databricks-managed identity/sharing identifier flow.
WHY NOT A: Open sharing (D2O) is for recipients on any platform, but it typically uses bearer tokens or OIDC federation and does not support notebook/volume/model sharing.
WHY NOT C: The open-source server is for customer-managed implementations and is not required for D2D on Databricks.
WHY NOT B: If both workspaces are attached to the same Unity Catalog metastore, you can govern access with Unity Catalog directly, but the scenario describes sharing across organizations/metastores and explicitly includes Delta Sharing-specific assets. Delta Sharing is not limited to non-Databricks recipients.