Deal of The Day! Hurry Up, Grab the Special Discount - Save 25% - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions

Microsoft Exam DP-600 Topic 2 Question 27 Discussion

Actual exam question for Microsoft's DP-600 exam
Question #: 27
Topic #: 2
[All DP-600 Questions]

You have a Fabric tenant that contains a takehouse named lakehouse1. Lakehouse1 contains a Delta table named Customer.

When you query Customer, you discover that the query is slow to execute. You suspect that maintenance was NOT performed on the table.

You need to identify whether maintenance tasks were performed on Customer.

Solution: You run the following Spark SQL statement:

DESCRIBE HISTORY customer

Does this meet the goal?

Show Suggested Answer Hide Answer
Suggested Answer: D

To identify surrogate key columns with the 'Summarize By' property set to a value other than 'None,' the Best Practice Analyzer in Tabular Editor is the most efficient tool. The Best Practice Analyzer can analyze the entire model and provide a report on all columns that do not meet a specified best practice, such as having the 'Summarize By' property set correctly for surrogate key columns. Here's how you would proceed:

Open your Power BI model in Tabular Editor.

Go to the Advanced Scripting window.

Write or use an existing script that checks the 'Summarize By' property of each column.

Execute the script to get a report on the surrogate key columns that do not have their 'Summarize By' property set to 'None'.

You can then review and adjust the properties of the columns directly within the Tabular Editor.


Contribute your Thoughts:

Lemuel
21 days ago
Ha, DESCRIBE HISTORY? More like DESCRIBE 'HISTORY' amirite? I wonder if the table has been keeping a secret diary this whole time. Maybe it's been planning a coup against the data engineers. *dramatic music plays*
upvoted 0 times
...
Marsha
24 days ago
I'm not so sure this is the right approach. Isn't there a more straightforward way to check for maintenance tasks? Maybe we're overthinking this. I bet the answer is B) No, just to throw us off!
upvoted 0 times
Ellsworth
21 hours ago
User1: I think we should try a different approach to check for maintenance tasks.
upvoted 0 times
...
...
Ressie
1 months ago
Definitely, the DESCRIBE HISTORY command is the way to go. I remember learning about that in my Databricks certification prep - it's like reading the table's diary to see what's been happening behind the scenes.
upvoted 0 times
Jani
4 days ago
User2: Yes, that command will show the history of maintenance tasks on the table.
upvoted 0 times
...
My
23 days ago
User1: A) Yes
upvoted 0 times
...
...
Rashad
2 months ago
Oh, I see. So the correct answer is actually B) No. Thanks for clarifying!
upvoted 0 times
...
Stefany
2 months ago
The DESCRIBE HISTORY statement should give us information about the maintenance tasks performed on the Customer table, so I think this solution meets the goal. Let's hope it's not too complicated to read through the output!
upvoted 0 times
Ilona
9 days ago
User 4: Fingers crossed that we can quickly identify if maintenance tasks were performed on the Customer table.
upvoted 0 times
...
Evan
14 days ago
User2: Agreed, let's check the output and see if maintenance tasks were performed on the Customer table.
upvoted 0 times
...
Delisa
20 days ago
User 3: Hopefully the output is clear and easy to understand.
upvoted 0 times
...
Shenika
21 days ago
User 2: I agree, the DESCRIBE HISTORY statement should provide us with the information we need.
upvoted 0 times
...
Percy
1 months ago
User 1: A) Yes
upvoted 0 times
...
Leota
1 months ago
User1: I think running DESCRIBE HISTORY customer will give us the information we need.
upvoted 0 times
...
...
Lizbeth
2 months ago
I disagree. The correct statement should be DESCRIBE HISTORY Customer.
upvoted 0 times
...
Rashad
2 months ago
I think the solution is correct. It should show the history of maintenance tasks on the Customer table.
upvoted 0 times
...

Save Cancel