DATABRICKS-DEP Question 110

Question

A platform team manages hundreds of Unity Catalog managed Delta tables and does not have the capacity to manually choose and periodically revisit clustering keys as BI dashboards evolve. They want Databricks to observe query history and select clustering keys automatically, changing them only when the switch is expected to pay for itself in reduced maintenance cost. Which configuration satisfies this requirement?
A. Create or alter the tables with `CLUSTER BY AUTO` so Databricks Runtime 15.4 LTS or later analyzes each table's query history and updates clustering keys only when the savings outweigh the reclustering cost.
B. Set the table property `delta.autoOptimize.autoCompact = true` on each table so Delta Lake automatically infers and rewrites clustering keys during every small write to keep files evenly sized.
C. Configure a nightly job that runs `ANALYZE TABLE COMPUTE STATISTICS` on each table and manually swaps the `CLUSTER BY` columns whenever the column statistics distribution changes significantly.
D. Enable predictive optimization at the catalog level so Databricks schedules `OPTIMIZE FULL` on a fixed interval, which re-evaluates and reselects the most selective columns for `ZORDER BY` on each scheduled run.

Accepted Answer

Marked answer: A. Create or alter the tables with `CLUSTER BY AUTO` so Databricks Runtime 15.4 LTS or later analyzes each table's query history and updates clustering keys only when the savings outweigh the reclustering cost.

DATABRICKS-DEP Question 110

Community Discussion

Preparing Practice Exam…

DATABRICKS-DEP Question 110

Community Discussion