New Year Sale 2026! Hurry Up, Grab the Special Discount - Save 25% - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions
Mail Us support@pass4success.com
Location US
Mob_nav_barsMENU

Databricks Certified Data Engineer Professional Exam - Topic 3 Question 40 Discussion

Actual exam question for Databricks's Databricks Certified Data Engineer Professional exam
Question #: 40
Topic #: 3
[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

by Leslee at Nov 24, 2025, 03:20 AM

Limited Time Offer

25%

Off

Get Premium Databricks Certified Data Engineer Professional Questions as Interactive Web-Based Practice Test or PDF

Contribute your Thoughts:

0/2000 characters
Submit Cancel
Novella
9 hours ago
C is the way to go, temp tables make it easy to manage!
upvoted 0 times
...
Tamra
6 days ago
I think B is better, functions are more flexible than UDFs.
upvoted 0 times
...
Lasandra
11 days ago
Option A sounds solid, left outer joins are great for this!
upvoted 0 times
...
Kayleigh
16 days ago
Option C with a temp table? Nah, that's way too much work. Keep it simple!
upvoted 0 times
...
Simona
21 days ago
Haha, I bet the user is really frustrated trying to figure this out. DLT expectations can be tricky!
upvoted 0 times
...
Tyisha
26 days ago
Option D with a view could work too, but a function might be easier to maintain.
upvoted 0 times
...
Maile
1 month ago
I like the idea of using a function to perform the join. Seems more efficient than a temp table.
upvoted 0 times
...
Malcolm
1 month ago
Option B seems like the right approach. A left outer join should do the trick.
upvoted 0 times
...
Chau
1 month ago
I'm a bit confused about the differences between options B and D. Both involve left outer joins, but I'm not clear on which one is more effective for DLT expectations.
upvoted 0 times
...
Sena
2 months ago
I feel like we practiced something similar to option D, where we used views for validation. It might be the right choice here.
upvoted 0 times
...
Reiko
2 months ago
I think option C sounds familiar; creating a temporary table and checking for null values seems like a solid approach, but I can't recall the specifics.
upvoted 0 times
...
Elden
2 months ago
I'm pretty confident that the solution here is to use a left outer join to compare the report table to the validation_copy table. That way, we can identify any records that are missing from the report table. Based on the options provided, I think option B or C would be the best approach. Defining a function or temporary table to perform the join and then checking the results in a DLT expectation seems like a solid strategy.
upvoted 0 times
...
Moon
2 months ago
I remember we discussed using left outer joins in class, but I'm not sure if a SQL UDF is the best way to handle this expectation.
upvoted 0 times
...
Jerilyn
2 months ago
Okay, let me think this through. The user wants to validate that the report table contains all the records from the validation_copy table, but adding an expectation to the report table definition didn't work. I think the best approach here would be to define a function or temporary table that performs a left outer join between the two tables, and then check the results in a DLT expectation. Option B or C seem like the most promising approaches to me.
upvoted 0 times
...
Celeste
3 months ago
Option A seems complicated. UDFs can be tricky to implement.
upvoted 0 times
...
Sylvia
3 months ago
Hmm, this is an interesting one. I think the key here is to find a way to compare the report table to the validation_copy table and check that all the expected records are present. Based on the options provided, it seems like defining a function or a temporary table that performs a left outer join might be the way to go. I'd probably lean towards option B or C, as they seem more straightforward than defining a SQL UDF or a view.
upvoted 0 times
...
Barney
3 months ago
I'm a bit confused by this question. It seems like we need to use DLT expectations to validate that the report table contains all the records from the validation_copy table, but the user has already tried adding an expectation to the report table definition and failed. I'm not sure which approach would be the best way to accomplish this.
upvoted 0 times
Felix
2 months ago
I prefer option B. It directly checks the two tables together.
upvoted 0 times
...
Dana
3 months ago
I think option A could work. A left outer join might show missing records.
upvoted 0 times
...
...

Save Cancel