Q: 8
A data engineer and data analyst are working together on a data pipeline. The data engineer is
working on the raw, bronze, and silver layers of the pipeline using Python, and the data analyst is
working on the gold layer of the pipeline using SQL. The raw source of the pipeline is a streaming
input. They now want to migrate their pipeline to use Delta Live Tables.
Which of the following changes will need to be made to the pipeline when migrating to Delta Live
Tables?
Options
Discussion
A . Delta Live Tables doesn't force you to drop the medallion layers or change from streaming, so B and D are traps here. You can keep mixing Python and SQL too, so C and E don't fit. Pretty sure it's A unless there's some hidden caveat I'm missing.
Had something like this in a mock before, and A fits since DLT supports both streaming and batch, allows Python and SQL, and keeps the medallion layers. No forced changes as the other options suggest. Pretty confident, but open to corrections.
A tbh, there's no need to change the pipeline structure for DLT. You can mix Python and SQL, and both streaming and batch sources are still supported. The medallion architecture stays as is. Saw similar in Databricks docs and some practice sets. If anyone found a gotcha in the exam, let me know!
A is right here since Delta Live Tables lets you keep the medallion architecture and supports both Python and SQL, plus streaming or batch. So no changes needed from the current setup. Pretty sure on this one, unless I'm missing a hidden detail.
Probably A. Delta Live Tables supports both Python and SQL for defining datasets, and it works with streaming or batch sources, so you don't have to change the current medallion setup. Pretty sure about this, but if anyone caught a trick here let me know.
Nah, it's not D. Delta Live Tables fully supports streaming sources, so A is correct here. That batch-only idea is a trap.
Option A for me, but honestly not 100 percent sure since sometimes Databricks has hidden gotchas. Looks like all the current tech and languages are already supported though. Anyone see a reason it wouldn't be A?
D imo, but does the question mean they require only streaming sources or could batch be allowed too? If the "must use streaming" requirement is relaxed then C could make sense, but Delta Live Tables actually supports both Python and SQL. The only real trap here is B since medallion architecture is supported in DLT.
Be respectful. No spam.
