Free Databricks Certified Data Engineer Associate Actual Exam Questions - Question 1 Discussion

D makes the most sense. MERGE INTO is designed to handle situations where you want to update existing rows or insert new ones without creating duplicates. INSERT INTO just adds rows blindly and doesn’t check for duplicates. Options like A and C don’t really relate to MERGE’s purpose, and B/E are about table types that might not support MERGE at all. So, avoiding duplicate records in the target table fits best with MERGE INTO.

D/B? MERGE INTO is great for updates or avoiding duplicates, but it only works if the target table supports those operations—usually a Delta table, not external ones. That rules out B mostly, so D fits best.

Guessing D here since MERGE INTO lets you update or insert records to keep the table free of duplicates, unlike plain INSERT which just adds new rows regardless.

D/E? MERGE INTO is ideal for avoiding duplicates, but it needs a Delta table as the target. Option E reminds me that without a Delta table, MERGE won’t work properly.

Probably D. MERGE INTO is mainly used to update existing records or insert new ones, which helps prevent duplicates—something INSERT INTO alone can’t efficiently handle. The other options don’t really match MERGE’s use case.

D imo, since MERGE handles duplicates better than simple INSERT.