Q: 4
You have a Fabric tenant tha1 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:
EXPLAIN TABLE customer
Does this meet the goal?
Options
Discussion
B for me. Had something like this in a mock and EXPLAIN TABLE only gives you the plan, not any info about maintenance tasks like OPTIMIZE or VACUUM. Could be wrong but pretty sure about B, unless anyone saw differently?
B tbh, EXPLAIN TABLE just gives you the execution plan, not maintenance info. If you want to check maintenance like OPTIMIZE or VACUUM, you'd have to look at table history. Open to other views if I missed something.
Pretty sure B is right. EXPLAIN TABLE just gives you the plan for how the query will run, but it doesn't tell you if OPTIMIZE or VACUUM were used on the Delta table. Official docs and practice tests mention you need to check table history or logs for maintenance status. Anyone tried confirming this in a lab yet?
Option A, Would the answer change if it asked about query performance instead of maintenance history?
Be respectful. No spam.
