Deal of The Day! Hurry Up, Grab the Special Discount - Save 25% - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions

Databricks Exam Databricks-Certified-Professional-Data-Engineer Topic 1 Question 22 Discussion

Actual exam question for Databricks's Databricks Certified Data Engineer Professional exam
Question #: 22
Topic #: 1
[All Databricks Certified Data Engineer Professional Questions]

A user wants to use DLT expectations to validate that a derived table report contains all records from the source, included in the table validation_copy.

The user attempts and fails to accomplish this by adding an expectation to the report table definition.

Which approach would allow using DLT expectations to validate all expected records are present in this table?

Show Suggested Answer Hide Answer
Suggested Answer: D

To validate that all records from the source are included in the derived table, creating a view that performs a left outer join between the validation_copy table and the report table is effective. The view can highlight any discrepancies, such as null values in the report table's key columns, indicating missing records. This view can then be referenced in DLT (Delta Live Tables) expectations for the report table to ensure data integrity. This approach allows for a comprehensive comparison between the source and the derived table.


Databricks Documentation on Delta Live Tables and Expectations: Delta Live Tables Expectations

Contribute your Thoughts:

Herminia
3 days ago
Haha, I bet the user's first attempt involved just staring at the report table and willing the records to appear. Option B is where it's at!
upvoted 0 times
...
Temeka
19 days ago
I like the idea of using a temporary table in option C, but defining a view feels more robust and maintainable in the long run.
upvoted 0 times
...
Jacquline
21 days ago
Hmm, that's a good point. Option D) does sound simpler. I might reconsider my choice now.
upvoted 0 times
...
Mitzie
23 days ago
I disagree, I believe option D) is the way to go. Defining a view that performs a left outer join and referencing it in DLT expectations seems more straightforward.
upvoted 0 times
...
Jacquline
25 days ago
I think option A) is the best approach because it involves using a SQL UDF to perform a left outer join and check for null values in the DLT expectation.
upvoted 0 times
...
Paz
25 days ago
Option D seems like the way to go. Defining a view to perform the left outer join and then referencing that in the DLT expectations is a clean and efficient approach.
upvoted 0 times
Luann
8 days ago
Option D seems like the way to go. Defining a view to perform the left outer join and then referencing that in the DLT expectations is a clean and efficient approach.
upvoted 0 times
...
...

Save Cancel