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

Databricks Certified Data Analyst Associate Exam - Topic 4 Question 1 Discussion

Actual exam question for Databricks's Databricks Certified Data Analyst Associate exam
Question #: 1
Topic #: 4
[All Databricks Certified Data Analyst Associate Questions]

A data analysis team is working with the table_bronze SQL table as a source for one of its most complex projects. A stakeholder of the project notices that some of the downstream data is duplicative. The analysis team identifies table_bronze as the source of the duplication.

Which of the following queries can be used to deduplicate the data from table_bronze and write it to a new table table_silver?

A)

CREATE TABLE table_silver AS

SELECT DISTINCT *

FROM table_bronze;

B)

CREATE TABLE table_silver AS

INSERT *

FROM table_bronze;

C)

CREATE TABLE table_silver AS

MERGE DEDUPLICATE *

FROM table_bronze;

D)

INSERT INTO TABLE table_silver

SELECT * FROM table_bronze;

E)

INSERT OVERWRITE TABLE table_silver

SELECT * FROM table_bronze;

Show Suggested Answer Hide Answer

Contribute your Thoughts:

0/2000 characters
Brice
3 months ago
Option C? Never heard of that syntax before. Is it even valid?
upvoted 0 times
...
Cristina
3 months ago
Totally agree with A! It's the simplest and most effective.
upvoted 0 times
...
Ethan
3 months ago
Wait, can you really use "MERGE DEDUPLICATE"? Sounds off.
upvoted 0 times
...
Melita
4 months ago
I think Option B could work too, but not for deduplication.
upvoted 0 times
...
Raelene
4 months ago
Option A is definitely the way to go!
upvoted 0 times
...
Cristy
4 months ago
I don't think MERGE DEDUPLICATE is a standard SQL command, so Option C seems wrong. But I'm not completely confident about the others either.
upvoted 0 times
...
Brandee
4 months ago
I feel like we practiced a similar question where we had to create a new table without duplicates. Option A sounds familiar, but I can't recall if there were other methods we discussed.
upvoted 0 times
...
Rashad
4 months ago
I'm not entirely sure, but I think INSERT INTO might just add more duplicates instead of removing them. So, maybe not Option D?
upvoted 0 times
...
Josefa
5 months ago
I remember we discussed using DISTINCT to remove duplicates in SQL. Option A seems like the right choice.
upvoted 0 times
...
Deandrea
5 months ago
Option B with the "INSERT *" syntax looks a bit strange to me. I don't think that's valid SQL, so I'll probably rule that one out.
upvoted 0 times
...
Bong
5 months ago
Option C mentions "MERGE DEDUPLICATE", which sounds promising, but I'm not familiar with that syntax. I'll have to double-check the documentation to see if that's a valid SQL operation.
upvoted 0 times
...
Ty
5 months ago
I'm a bit unsure about the difference between Option D and Option E. Both seem to be using INSERT statements, but I'm not sure if there's a meaningful difference between them.
upvoted 0 times
...
Tomoko
5 months ago
Hmm, this looks like a pretty straightforward deduplication task. I think Option A with the DISTINCT keyword is the way to go here.
upvoted 0 times
...
Pearlie
5 months ago
I'm leaning towards Option A as well. The DISTINCT keyword is a classic way to remove duplicates, and it's a simple and reliable solution.
upvoted 0 times
...
Dawne
5 months ago
I think this is a pretty straightforward question. The security guards likely have the right to check IDs and bags for safety reasons, so I'll go with A.
upvoted 0 times
...
Raelene
5 months ago
Hmm, I'm a little unsure about this one. I'll need to carefully review the Scrum principles and how they relate to risk management.
upvoted 0 times
...
Annice
5 months ago
I'm a little unsure here. I'll need to review my notes on the different accounting pronouncements to make sure I choose the right one.
upvoted 0 times
...

Save Cancel