Databricks Certified Data Engineer Professional Practice Questions

Databricks Certified Data Engineer Professional exam preparation

Databricks Certified Data Engineer Professional practice questions in English: 178 questions with explanations. The mock exam has 60 questions and 120 minutes.

Databricks Certified Data Engineer Professional free question 2 / 10 · Domain 2: Data Ingestion & Acquisition

A provider shares data with a partner through Databricks-to-Databricks OpenSharing. The recipient was created with the sharing identifier of the partner's us-west-2 metastore. The partner now asks to read the same share, still through Databricks-to-Databricks, from a workspace attached to a different metastore in eu-west-1. What does the provider do?

  1. Add the eu-west-1 metastore's sharing identifier to the existing recipient and reattach it
  2. Create another recipient with the eu-west-1 metastore's sharing identifier and grant it the share
  3. Create another recipient with the eu-west-1 metastore's sharing identifier, and give the partner the token it issues so they can read the share
  4. Keep the existing recipient, and have the partner assign the catalog created from the share to both workspaces
Show the answer and explanation

Answer: B

Why this is correct
For Databricks-to-Databricks, a recipient with authentication type DATABRICKS uses a sharing identifier (a string of the form <cloud>:<region>:<uuid>) to represent a specific Unity Catalog metastore, and the data shared with that recipient can be read only in that metastore. To let another metastore read it, create one more recipient with that metastore's sharing identifier and grant it access to the share. One recipient can have multiple shares, but one recipient represents exactly one metastore.

Why the other options are wrong
"Add the eu-west-1 metastore's sharing identifier to the existing recipient and reattach it" … A recipient represents one metastore through one sharing identifier. You cannot add an identifier to make a recipient represent two metastores.
"Create another recipient with the eu-west-1 metastore's sharing identifier, and give the partner the token it issues so they can read the share" … A Databricks-to-Databricks recipient does not need a token to read a share, and the provider does not manage tokens for such recipients. Handing out a token is how Databricks-to-Open recipients work, and it would not give the partner the Databricks-to-Databricks sharing they asked for.
"Keep the existing recipient, and have the partner assign the catalog created from the share to both workspaces" … A catalog created from a share lives in the us-west-2 metastore that the recipient represents. It cannot be used from a workspace attached to the eu-west-1 metastore.

Key point
Even when a provider wants to share data from several metastores with the same party, it defines one recipient for each metastore.

Go to the Databricks Certified Data Engineer Professional practice app (10 free questions; purchase unlocks all questions)

See the full practice set