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

Actual exam question for Databricks's Databricks Certified Data Engineer Professional exam

Question #: 5
Topic #: 1

[All Databricks Certified Data Engineer Professional Questions]

The marketing team is looking to share data in an aggregate table with the sales organization, but the field names used by the teams do not match, and a number of marketing specific fields have not been approval for the sales org.

Which of the following solutions addresses the situation while emphasizing simplicity?

ACreate a view on the marketing table selecting only these fields approved for the sales team alias the names of any fields that should be standardized to the sales naming conventions.

BUse a CTAS statement to create a derivative table from the marketing table configure a production jon to propagation changes.

CAdd a parallel table write to the current production pipeline, updating a new sales table that varies as required from marketing table.

DCreate a new table with the required schema and use Delta Lake's DEEP CLONE functionality to sync up changes committed to one table to the corresponding table.

Show Suggested Answer

Suggested Answer: A

Creating a view is a straightforward solution that can address the need for field name standardization and selective field sharing between departments. A view allows for presenting a transformed version of the underlying data without duplicating it. In this scenario, the view would only include the approved fields for the sales team and rename any fields as per their naming conventions.

Databricks documentation on using SQL views in Delta Lake: https://docs.databricks.com/delta/quick-start.html#sql-views

by Van at Mar 19, 2024, 07:15 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:

Submit Cancel

Wenona

3 months ago

B could work, but it feels like overkill for just a few fields.

upvoted 0 times

...

Jodi

3 months ago

Wait, can we really use Delta Lake's DEEP CLONE for this? Sounds too good to be true.

upvoted 0 times

...

Frankie

3 months ago

I like A too, it keeps everything in one place!

upvoted 0 times

...

Tonette

4 months ago

I disagree, A might complicate things with too many aliases.

upvoted 0 times

...

Hortencia

4 months ago

Option A seems the simplest, just rename fields for clarity.

upvoted 0 times

...

Donte

4 months ago

I vaguely recall Delta Lake's DEEP CLONE from our last session, but I'm not sure if it's the best fit here. It seems like it might add unnecessary complexity.

upvoted 0 times

...

Thad

4 months ago

I feel like option C could work too, but it sounds like it might complicate things with having to manage two separate tables.

upvoted 0 times

...

Robt

4 months ago

I'm not entirely sure, but I remember something about CTAS statements from our practice questions. They seem more complex than just creating a view.

upvoted 0 times

...

Noel

5 months ago

I think option A makes the most sense since it focuses on creating a view with the approved fields, which seems simpler than creating a whole new table.

upvoted 0 times

...

Gaynell

5 months ago

I think I'm leaning towards option A as well. Creating a view seems like the most straightforward way to address the field name and approval issues without having to create a whole new table. As long as the view is properly maintained, it should be a simple and effective solution.

upvoted 0 times

...

Audra

5 months ago

Option C, adding a parallel table write to the current production pipeline, seems interesting. That way we can keep the marketing table as-is and have a separate sales table with the required changes. Might be a bit more complex to set up, but could be a good long-term solution.

upvoted 0 times

...

Dante

5 months ago

Hmm, I'm a bit confused by the options. Can we use a CTAS statement to create a new table with the required schema? That seems like it could work, but I'm not sure if it's the "simplest" approach.

upvoted 0 times

...

Annamae

5 months ago

This looks like a straightforward data integration problem. I think option A, creating a view with the approved fields and standardized names, is the simplest and most direct solution.

upvoted 0 times

...