Home / DE Professional practice test / Data Sharing and Federation

Free · 8 questions with explanations

Data Sharing and Federation: Databricks Data Engineer Professional Practice Questions

Exam-style questions on Data Sharing and Federation. Pick your answer, then open the explanation to see why it's right — and why the other options are wrong.

Updated November 16, 2026

1 Data Sharing and Federation Medium

A provider wants to share a Unity Catalog volume to a recipient. Which statement is correct about volume sharing in Delta Sharing?

  1. AVolumes can be shared using either open sharing (D2O) or Databricks-to-Databricks (D2D) sharing.
  2. BVolumes can only be shared using a customer-managed open-source Delta Sharing server.
  3. CVolumes cannot be shared using Delta Sharing; only Delta tables are supported.
  4. DVolumes can only be shared using the Databricks-to-Databricks (D2D) sharing flow.
Show answer & explanation

Correct answer: D

WHY D: Databricks documentation distinguishes assets that are only available in the Databricks-to-Databricks sharing flow; Unity Catalog volume sharing is supported in D2D, not open sharing. WHY NOT A: Open sharing is intended for cross-platform tabular sharing and does not support volume sharing. WHY NOT C: Delta Sharing can share more than just tables in D2D (for example notebooks, volumes, models, and certain views) when both sides use Unity Catalog-enabled Databricks. WHY NOT B: You do not need a customer-managed open-source server to share volumes between Databricks workspaces.

2 Data Sharing and Federation

A data engineer must let analysts query tables that live in an external PostgreSQL database directly from Databricks SQL, without copying the data into Delta, while enforcing Unity Catalog permissions on the federated tables. Which sequence of Unity Catalog objects correctly sets up Lakehouse Federation for this source?

  1. ACreate a Delta Sharing recipient for the PostgreSQL server and add it to a share; Delta Sharing's open protocol federates any JDBC-compatible source, exposing its tables as a shared catalog governed by Unity Catalog.
  2. BCreate an external location and a storage credential pointing at the PostgreSQL data files, then register the tables as external Delta tables over those files; Unity Catalog governs the external tables and reads them in place from the database's underlying storage.
  3. CMount the PostgreSQL database to DBFS with a JDBC mount point, then create views over the mount; the mount provides live federated access and Unity Catalog permissions are inherited from the DBFS mount ACLs.
  4. DUse spark.read.format('jdbc') inside a scheduled job to load each PostgreSQL table into a managed Delta table nightly, then grant analysts SELECT on the Delta copies; this is what Lakehouse Federation does under the hood, so no Connection object is needed.
  5. ECreate a Unity Catalog Connection to the PostgreSQL server (holding host, port, and credentials), then create a foreign catalog that references that connection and maps the PostgreSQL database; analysts then query it as catalog.schema.table with Unity Catalog governing access, and queries are pushed down to PostgreSQL at run time.
Show answer & explanation

Correct answer: E

WHY E: Lakehouse Federation uses a Unity Catalog Connection object (storing connection details and credentials for the external system) plus a foreign catalog that maps the remote database. Analysts then query the foreign catalog's tables by three-level name; Unity Catalog enforces permissions and Databricks pushes query fragments down to PostgreSQL, with no data copy. WHY NOT B: External locations/storage credentials govern access to cloud object storage files, not live queries against an operational database engine like PostgreSQL. WHY NOT C: DBFS mounts are a legacy file-access mechanism, do not perform live JDBC federation, and are not the Unity Catalog governance model. WHY NOT D: A nightly JDBC copy into Delta is exactly what federation avoids (it is a copy, not live), and federation is not implemented as a hidden nightly copy. WHY NOT A: Delta Sharing shares Delta data between provider and recipients; it does not federate an arbitrary JDBC/PostgreSQL source — that is Lakehouse Federation's role.

3 Data Sharing and Federation

A data provider on Databricks with Unity Catalog must share a curated Delta table with two consumers: (1) a partner organization that also runs Databricks with Unity Catalog, who should be able to reference the shared data as a catalog and have new data appear without re-copying, and (2) an external analytics team that uses pandas and Apache Spark on their own infrastructure with no Databricks account. The provider wants a single sharing technology, live (no-copy) access for both, and centralized governance of grants. Which approach is correct?

  1. AUse Lakehouse Federation to register the provider's Unity Catalog as a foreign catalog in the partner's workspace, and for the external team expose a JDBC endpoint; federation gives live access without any recipient objects for either consumer.
  2. BUse Databricks-to-Databricks Delta Sharing for the partner, and for the external team export the table to Parquet on a nightly schedule to a shared cloud bucket, because the open Delta Sharing protocol only supports Databricks recipients and cannot serve non-Databricks clients.
  3. CCreate a Delta DEEP CLONE of the table into each recipient's cloud storage account and grant them read access to the clone; deep clone keeps the copies in sync automatically, providing live access without exposing the provider's metastore.
  4. DPublish the table to a Databricks Marketplace listing for the partner and generate a personal access token (PAT) for the external team to call the Databricks Jobs REST API and pull table snapshots, since Delta Sharing does not support token-based external access.
  5. EUse Delta Sharing for both: add the Databricks partner as a Unity Catalog recipient with a metastore sharing identifier (Databricks-to-Databricks), and add the external team as an open-sharing recipient authenticated with a bearer token that they consume via the open Delta Sharing protocol connector — both read live data with no data copy.
Show answer & explanation

Correct answer: E

WHY E: Delta Sharing supports both modes from one technology. Databricks-to-Databricks (D2D) sharing lets the partner's Unity Catalog mount the share as a catalog with live, no-copy access and centrally managed grants. The open sharing protocol (D2O) serves non-Databricks clients (pandas/Spark) via a bearer-token-authenticated recipient reading live data through the open protocol connector. WHY NOT B: The open Delta Sharing protocol is specifically designed for non-Databricks recipients, so nightly Parquet exports are unnecessary and are not live/no-copy. WHY NOT C: DEEP CLONE creates physical copies that must be periodically refreshed; it is not live no-copy sharing and pushes data into recipient storage. WHY NOT D: Delta Sharing DOES support token-based external access via the open protocol; using PATs against the Jobs API to pull snapshots is not a sharing mechanism and is not live. WHY NOT A: Lakehouse Federation is for querying external/foreign data sources FROM Databricks, not for a provider to publish a Databricks table to external consumers; it does not serve non-Databricks clients this way.

4 Data Sharing and Federation Easy

A provider shares a Delta table with history using Delta Sharing open sharing. The recipient asks whether the provider must replicate data into a separate shared storage account and whether the data will stay up-to-date. Which response is most accurate?

  1. AYes—Delta Sharing requires a full copy of the data into a new storage location owned by the recipient; updates are delivered by periodic snapshot exports.
  2. BNo—Delta Sharing is designed for live, zero-copy sharing; recipients access shared data read-only and provider updates appear in near real time without needing replication.
  3. CYes—Delta Sharing always materializes the entire table on the provider side before recipients can query it, so updates are only visible after a manual refresh.
  4. DNo—Delta Sharing data is always cached permanently in Databricks-managed storage so the recipient never incurs network transfer.
Show answer & explanation

Correct answer: B

WHY B: Delta Sharing is an open protocol for secure cross-platform sharing that does not require data replication; recipients get read-only access and updates show up in near real time as the provider updates the underlying table. WHY NOT A: Replication/snapshot export is not a requirement of Delta Sharing. WHY NOT C: Materialization is not always required; it depends on asset type and compute context (for example, some view/materialized assets can be filtered/materialized in certain scenarios), but the protocol itself supports live access. WHY NOT D: Network transfer/egress can still apply (especially cross-cloud/region), and caching behavior depends on the specific workflow.

5 Data Sharing and Federation Medium

To enable Lakehouse Federation (query federation) for an external MySQL database, which Unity Catalog securable objects do you create, and what is the correct high-level permission model to create them?

  1. ACreate a storage credential and an external location; you need CREATE STORAGE CREDENTIAL and CREATE EXTERNAL LOCATION on the metastore.
  2. BCreate a schema and a view over the MySQL tables; you need CREATE TABLE on the schema and SELECT on the view that is created.
  3. CCreate a share and a recipient; you need USE SHARE and SET SHARE PERMISSION on the metastore to query the foreign tables.
  4. DCreate a connection and a foreign catalog; you need CREATE CONNECTION and CREATE CATALOG on the metastore plus rights on the connection.
Show answer & explanation

Correct answer: D

WHY D: Query federation in Lakehouse Federation uses a Unity Catalog connection (holds the JDBC path and credentials) and a foreign catalog (mirrors the external database). Creating them requires metastore-level privileges: CREATE CONNECTION on the metastore for the connection, and CREATE CATALOG on the metastore plus either ownership of the connection or explicit CREATE FOREIGN CATALOG on that connection for the foreign catalog. WHY NOT A: External locations and storage credentials are central to cloud storage access and catalog federation scenarios, not to basic JDBC query federation of a MySQL database. WHY NOT C: Shares and recipients are Delta Sharing concepts, not federation objects, and their privileges do not give access to an external MySQL database. WHY NOT B: Schemas and views do not establish federated access to an external database; without a connection and a foreign catalog there are no MySQL tables to build a view on.

6 Data Sharing and Federation Medium

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?

  1. AA Databricks sharing identifier supplied by the recipient; bearer tokens are reserved for Databricks-to-Databricks shares.
  2. BEither a long-lived bearer token or OpenID Connect (OIDC) token federation to obtain short-lived OAuth tokens.
  3. COAuth through Databricks-to-Databricks identity; open sharing requires the recipient to run a Databricks workspace.
  4. DKerberos tickets issued by the provider workspace; open sharing reuses Hive metastore authentication for recipients.
Show 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.

7 Data Sharing and Federation

A provider shares data with an external open-protocol recipient via a bearer token embedded in a credential file. Security policy requires that the token be rotated periodically and that a leaked token can be invalidated immediately without permanently destroying the sharing relationship or its grants. Using Unity Catalog Delta Sharing, which action set meets these requirements?

  1. ARevoke the SELECT grant on every shared table to invalidate the token, then re-grant after issuing a new one; grants and tokens are the same object in Delta Sharing, so revoking access is how a token is rotated.
  2. BDelete the recipient and recreate it with the same name whenever rotation is needed; recreating the recipient is the only supported way to change its token, and the shares automatically re-attach because they are keyed by recipient name.
  3. CEdit the credential file distributed to the recipient to contain a new random token; because the token is validated only by string length and format, changing the file value on the recipient side immediately rotates the credential server-side.
  4. DRotate the recipient's token with the Unity Catalog recipient token-rotation operation, which issues a new credential and (optionally with an immediate expiration on the old one) invalidates the previous token, while the recipient object, its shares, and grants remain intact.
  5. ESet the metastore-level delta.sharing.tokenLifetime to zero and toggle it back, which forces all recipient tokens to regenerate at once; per-recipient rotation is not supported, so it must be done globally.
Show answer & explanation

Correct answer: D

WHY D: Unity Catalog supports rotating a recipient's bearer token via the recipient token-rotation operation; it mints a new credential and can expire the old token immediately, invalidating a leaked token while preserving the recipient object, its shares, and grants — exactly the requirement. WHY NOT B: Deleting and recreating the recipient is destructive and unnecessary; token rotation exists precisely so you do not have to tear down the relationship, and shares/grants would need to be reattached. WHY NOT C: Tokens are validated server-side, not by editing the client's credential file; changing the file's string does not rotate anything and would simply break the recipient's access. WHY NOT A: Grants and tokens are distinct — revoking table grants removes access but does not rotate the authentication credential, and re-granting does not issue a new token. WHY NOT E: There is no global 'set lifetime to zero to regenerate all tokens' toggle; rotation is performed per recipient.

8 Data Sharing and Federation Hard

Your team is deciding between query federation and catalog federation within Lakehouse Federation. Which statement best describes the execution and cost characteristics?

  1. AQuery federation reads foreign tables directly from object storage on Databricks compute, which makes it the more cost-effective of the two options.
  2. BCatalog federation pushes queries down over JDBC and executes them on the remote database's compute, which makes it the better fit for ad hoc access.
  3. CBoth federation types execute the same way over JDBC on remote compute; they differ in whether the connection is created through the UI or with SQL.
  4. DQuery federation pushes work down over JDBC and uses Databricks plus remote compute; catalog federation reads object storage on Databricks compute.
Show answer & explanation

Correct answer: D

WHY D: Lakehouse Federation includes two patterns: query federation (JDBC pushdown with remote compute involvement, executing in both Databricks and the remote system) and catalog federation (direct object storage access, queries run only on Databricks compute). Catalog federation is typically more cost-effective and performance-optimized because it avoids remote query execution, while query federation is often suited for ad hoc reporting/POCs and leveraging external system compute. WHY NOT A: This swaps the definitions: reading foreign tables directly from object storage on Databricks compute describes catalog federation, not query federation. WHY NOT B: This swaps the definitions: JDBC pushdown to remote database compute describes query federation, not catalog federation. WHY NOT C: The difference is architectural and affects the execution path, governance integration, and performance/cost tradeoffs; it is not about how the connection is created.

Take the full DE Professional practice test →