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
Mail Us support@pass4success.com
Location US
Mob_nav_barsMENU

Databricks Machine Learning Professional Exam - Topic 6 Question 28 Discussion

Actual exam question for Databricks's Databricks Machine Learning Professional exam
Question #: 28
Topic #: 6
[All Databricks Machine Learning Professional Questions]

After a data scientist noticed that a column was missing from a production feature set stored as a Delta table, the machine learning engineering team has been tasked with determining when the column was dropped from the feature set.

Which of the following SQL commands can be used to accomplish this task?

Show Suggested Answer Hide Answer
Suggested Answer: C

by Cecily at Sep 17, 2024, 11:47 AM

Limited Time Offer

25%

Off

Get Premium Databricks Machine Learning Professional Questions as Interactive Web-Based Practice Test or PDF

Contribute your Thoughts:

0/2000 characters
Submit Cancel
Ira
3 months ago
I thought TIMESTAMP could do it, but I guess not!
upvoted 0 times
...
Doretha
3 months ago
VERSION won't help with that, it's not the right command.
upvoted 0 times
...
Titus
3 months ago
Wait, can you really track when a column was dropped?
upvoted 0 times
...
Marget
4 months ago
Definitely, it shows the changes over time.
upvoted 0 times
...
Iluminada
4 months ago
I think DESCRIBE HISTORY is the way to go!
upvoted 0 times
...
Desmond
4 months ago
I think DESCRIBE HISTORY is the best option here since it should provide a detailed log of changes, including dropped columns.
upvoted 0 times
...
Una
4 months ago
I feel like DESCRIBE could give us some information, but it might not show the historical changes we're looking for.
upvoted 0 times
...
Howard
4 months ago
I remember practicing with the HISTORY command in a similar question, but I can't recall if it specifically shows when columns were dropped.
upvoted 0 times
...
Filiberto
5 months ago
I think we might need to use the DESCRIBE HISTORY command to see the changes made to the Delta table, but I'm not entirely sure.
upvoted 0 times
...
Rebbecca
5 months ago
Ugh, I'm really not sure about this one. There are a lot of SQL commands to choose from, and I'm not confident I know which one will give me the information I need. Guess I'll just have to make an educated guess and hope for the best.
upvoted 0 times
...
Lettie
5 months ago
I've got this! The VERSION command will show me the different versions of the Delta table, and then I can use DESCRIBE HISTORY on each version to pinpoint when the column disappeared. Easy peasy!
upvoted 0 times
...
Gail
5 months ago
I'm a bit confused on this one. I know the DESCRIBE command can give me information about the table structure, but I'm not sure if that will tell me when a column was dropped. Maybe the HISTORY command would be better?
upvoted 0 times
...
Kenneth
5 months ago
Okay, let's see here. I'm pretty sure the DESCRIBE HISTORY command is the way to go - it should show the changes made to the table over time, including when columns were added or removed.
upvoted 0 times
...
Buddy
5 months ago
Hmm, this seems like a tricky one. I'll need to think through the different SQL commands carefully to determine which one is best for finding when the column was dropped.
upvoted 0 times
...
Viki
5 months ago
Hmm, this one has me a bit stumped. I'm not totally sure which stakeholder would have the best handle on the technical constraints. The project manager might have a good overview, but the suppliers would probably have the most detailed technical knowledge. I'll have to think this through carefully.
upvoted 0 times
...
Felicia
9 months ago
I'm torn between B) DESCRIBE and D) DESCRIBE HISTORY. Either one could give us the details we need, but I think D) is the safer bet.
upvoted 0 times
...
Truman
9 months ago
Haha, I bet the Delta table is missing more than just a column. Probably the whole data science team dropped the ball on this one!
upvoted 0 times
Tarra
9 months ago
C) HISTORY
upvoted 0 times
...
Paris
9 months ago
B) DESCRIBE
upvoted 0 times
...
Reyes
9 months ago
A) VERSION
upvoted 0 times
...
...
Salome
10 months ago
I'm going with E) TIMESTAMP. If we can get the timestamp of when the column was dropped, that should give us the information we need.
upvoted 0 times
Donette
9 months ago
C) HISTORY
upvoted 0 times
...
Nadine
10 months ago
B) DESCRIBE
upvoted 0 times
...
Alisha
10 months ago
A) VERSION
upvoted 0 times
...
...
Marnie
10 months ago
Hmm, I'm not sure. Maybe C) HISTORY would work too? That could show the changes made to the table over time.
upvoted 0 times
Tom
9 months ago
I agree, let's try using C) HISTORY to see when the column was dropped.
upvoted 0 times
...
Buddy
9 months ago
I think C) HISTORY is the right choice. It should show the history of changes made to the table.
upvoted 0 times
...
...
Kathrine
10 months ago
I'm not sure, but I think D) DESCRIBE HISTORY might also work to accomplish the task.
upvoted 0 times
...
Rebecka
10 months ago
I think the answer is D) DESCRIBE HISTORY. It sounds like the best way to check the history of the Delta table and see when the column was dropped.
upvoted 0 times
...
Johnathon
11 months ago
I agree with Wade, using HISTORY command can help determine when the column was dropped.
upvoted 0 times
...
Wade
11 months ago
I think the answer is C) HISTORY.
upvoted 0 times
...

Save Cancel