Exam Certified Data Engineer Professional topic 1 question 8 discussion

Actual exam question from Databricks's Certified Data Engineer Professional

Question #: 8
Topic #: 1

[All Certified Data Engineer Professional Questions]

An upstream source writes Parquet data as hourly batches to directories named with the current date. A nightly batch job runs the following code to ingest all data from the previous day as indicated by the date variable:

Assume that the fields customer_id and order_id serve as a composite key to uniquely identify each order.
If the upstream system is known to occasionally produce duplicate entries for a single order hours apart, which statement is correct?

A. Each write to the orders table will only contain unique records, and only those records without duplicates in the target table will be written.
B. Each write to the orders table will only contain unique records, but newly written records may have duplicates already present in the target table.
C. Each write to the orders table will only contain unique records; if existing records with the same key are present in the target table, these records will be overwritten.
D. Each write to the orders table will only contain unique records; if existing records with the same key are present in the target table, the operation will fail.
E. Each write to the orders table will run deduplication over the union of new and existing records, ensuring no duplicate records are present.

Show Suggested Answer

Suggested Answer: B 🗳️

by thxsgod at Sept. 7, 2023, 12:03 p.m.

Comments

Submit Cancel

Eertyy

Highly Voted 1 year, 10 months ago

B. Each write to the orders table will only contain unique records, but newly written records may have duplicates already present in the target table. Explanation: In the provided code, the .dropDuplicates(["customer_id","order_id"]) operation is performed on the data loaded from the Parquet files. This operation ensures that only unique records, based on the composite key of "customer_id" and "order_id," are retained in the DataFrame before writing to the "orders" table. However, this operation does not consider duplicates that may already exist in the "orders" table. It only filters duplicates from the current batch of data. If there are duplicates in the "orders" table from previous batches, they will remain in the table. So, newly written records will not have duplicates within the batch being written, but duplicates from previous batches may still exist in the target table.

upvoted 21 times

meatpoof

6 months, 2 weeks ago

The question doesn't say orders already exists. Arekm's answer is more correct

upvoted 1 times

...

KadELbied

Most Recent 3 months ago

Selected Answer: B

suretly B

upvoted 1 times

...

arekm

7 months, 1 week ago

Selected Answer: B

No duplicates in the current batch - that is obvious. The duplicates may happen since the source occasionally produces duplicates hours apart. This means that one record can be generated by the source and processed on day 1, the duplicate on day 2. Since there is no logic checking if the corresponding record exists in the target - you get the duplicates there given we use append mode.

upvoted 2 times

...

Anithec0der

8 months ago

Selected Answer: B

yeah B is the correct answer cause in the current code it will look for duplicates in the currentDF based on composite keys and not for the duplicates which are already in the target table. if we want to insert for the rows which are not there in target table then we can make use of Merge Into statement of databricks.

upvoted 1 times

...

benni_ale

10 months, 3 weeks ago

Selected Answer: B

Append method does not take in consideration any key in the target table, it simply add all rows of the input table to the target table.

upvoted 1 times

...

panya

1 year, 1 month ago

Yes it should be B

upvoted 1 times

...

imatheushenrique

1 year, 2 months ago

B. Each write to the orders table will only contain unique records, but newly written records may have duplicates already present in the target table. Using merge this problem would not happen

upvoted 1 times

...