Databricks-DE-Pro Data Sharing and Federation Practice Question
A data engineer is managing a Delta Share that includes a table with customer transactions. The share is used by multiple recipients. The engineer needs to update the shared data daily with new transactions and also remove data for customers who have requested deletion (right to be forgotten). The engineer wants to ensure recipients see the updated data without having to recreate the share. What is the best approach?
⚠ Common exam trap
The trap here is thinking that updates require recreating the share or that deletions are not visible, when in fact Delta Sharing reflects the live table state.
Answer choices
Why each option matters
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Update the underlying Delta table with new data and use DELETE to remove records; recipients will see changes on their next query.
Delta Sharing shares the current state of the Delta table. When the provider performs updates or deletes on the table, recipients see the changes on their next query. There is no need to recreate the share or use materialized views. This approach ensures recipients always access the latest data, including deletions for compliance.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Use a materialized view to capture changes and share the view instead of the table.
Why it's wrong here
Materialized views are not directly shareable via Delta Sharing. Delta Sharing shares tables or views, but materialized views are not supported as share objects. Also, refreshing a materialized view would not automatically propagate to recipients. The underlying table should be updated directly.
- ✓
Update the underlying Delta table with new data and use DELETE to remove records; recipients will see changes on their next query.
Why this is correct
Delta Sharing shares the live table. When the provider updates the Delta table (e.g., with MERGE or INSERT) and deletes records, recipients querying the shared table will see the latest version. There is no need to recreate the share. The recipients' queries will reflect the current state of the table, including deletions, as long as they query the latest version.
- ✗
Use Delta Sharing's built-in history sharing to automatically propagate updates and deletions.
Why it's wrong here
Delta Sharing does not automatically propagate updates and deletions unless the shared table is a Delta table with change data feed enabled and the share is configured to share history. However, even then, deletions are not automatically removed from recipients' views unless they query with time travel. The engineer must manage updates explicitly.
- ✗
Recreate the share with the updated table and notify recipients to update their credentials.
Why it's wrong here
Recreating the share is unnecessary and disruptive. Delta Sharing supports live tables, so updates are automatically visible. Recipients would need to reconfigure their access, which is not required. The best practice is to update the table in place.
About these practice questions
One of 267 original Databricks-DE-Pro practice questions on Courseiva, each with a full explanation and wrong-answer analysis — not exam dumps or protected exam content. Learn why practice questions differ from exam dumps →
JA
Written and reviewed by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
Last reviewed September 2026 · checked against the official Databricks exam blueprint
This Databricks-DE-Pro practice question is part of Courseiva's free Databricks certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the Databricks-DE-Pro exam.