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 Engineer Associate Exam - Topic 2 Question 57 Discussion

Actual exam question for Databricks's Databricks Certified Data Engineer Associate exam
Question #: 57
Topic #: 2
[All Databricks Certified Data Engineer Associate Questions]

A data engineer is attempting to drop a Spark SQL table my_table. The data engineer wants to delete all table metadata and data.

They run the following command:

DROP TABLE IF EXISTS my_table

While the object no longer appears when they run SHOW TABLES, the data files still exist.

Which of the following describes why the data files still exist and the metadata files were deleted?

Show Suggested Answer Hide Answer

Contribute your Thoughts:

0/2000 characters
Mohammad
9 hours ago
I think it's C) The table was external. That makes sense.
upvoted 0 times
...
Kyoko
6 days ago
Wait, so if it was managed, the data should be gone too?
upvoted 0 times
...
Mireya
11 days ago
Definitely C, external tables keep the data.
upvoted 0 times
...
Francene
16 days ago
I thought managed tables would delete everything, right?
upvoted 0 times
...
Kris
21 days ago
Haha, looks like the data engineer forgot to specify the location for the table. Classic mistake!
upvoted 0 times
...
Lashaun
26 days ago
D) The table did not have a location
upvoted 0 times
...
Earnestine
1 month ago
Ah, I see! The data files still exist because the table was external, meaning the data was stored outside of the Spark SQL managed tables.
upvoted 0 times
...
Billye
1 month ago
C) The table was external
upvoted 0 times
...
Beckie
1 month ago
I vaguely recall something about the size of the data affecting the drop command, but I can’t remember the specifics. It might not be related to the size at all.
upvoted 0 times
...
Myra
2 months ago
I practiced a similar question where the data files remained because the table was external. I think that’s definitely the case here, so I’ll go with C.
upvoted 0 times
...
Cathrine
2 months ago
I’m not entirely sure, but I feel like if the table was managed, the data should have been deleted too. Maybe it’s option E?
upvoted 0 times
...
Page
2 months ago
I'm leaning towards option C as well. The fact that the data files still exist after dropping the table implies it was an external table, not a managed table.
upvoted 0 times
...
Chana
2 months ago
I remember something about external tables keeping their data even after dropping them, so I think option C might be right.
upvoted 0 times
...
Lizbeth
2 months ago
The table was external, that's why the data files are still there.
upvoted 0 times
...
Carey
2 months ago
Okay, let me think this through. The key piece of information is that the data files still exist, even though the table no longer appears in SHOW TABLES. That suggests the table was external, so I'm going with option C.
upvoted 0 times
...
Denny
3 months ago
Yeah, I agree with C. External tables are tricky like that!
upvoted 0 times
...
Adelle
3 months ago
Hmm, my initial thought was that the table was smaller than 10 GB, so option B might be correct. But the question doesn't mention anything about the table size, so I'm not sure that's the right answer.
upvoted 0 times
...
Yuette
3 months ago
I'm a bit confused on this one. If the table was managed, wouldn't the data files have been deleted? I'm not sure why the metadata would be deleted but the data files would remain.
upvoted 0 times
...
Angelyn
3 months ago
I think the answer is C - the table was external. The question says the data files still exist, which suggests the table was not managed by Spark.
upvoted 0 times
...

Save Cancel