A provider wants to share live, read-only Delta tables from a Unity Catalog-enabled workspace to external consumers who will query using non-Databricks tools (for example, pandas or Power BI). Which authentication approaches are supported for open Delta Sharing recipients?
Answer & explanation
Correct answer: B
WHY B: Databricks open sharing supports token-based auth (bearer token credentials shared with the recipient) and OIDC federation (the recipient exchanges IdP JWTs for short-lived Databricks OAuth tokens). This lets recipients query from many platforms (Spark, pandas, Power BI, etc.).
WHY NOT A: Sharing identifiers are used for Databricks-to-Databricks sharing, not open sharing; bearer tokens are an open-sharing credential, so this option has the two models reversed.
WHY NOT C: Databricks-to-Databricks identity is the other sharing model. Open sharing explicitly targets non-Databricks clients, so the recipient does not need a Databricks workspace.
WHY NOT D: Kerberos/Hive metastore authentication is unrelated to the Delta Sharing open protocol.