Home / DE Professional practice test / Cost & Performance Optimisation / Question

Databricks Data Engineer Professional · free practice question

A data engineering team is migrating from external tables to Unity Catalog managed tables to reduce operational overhead. After the migration and enabling…

Exam-style question on Cost & Performance Optimisation from the free DE Professional practice test, with the answer and a full explanation below.

Updated November 16, 2026

Cost & Performance Optimisation Medium

A data engineering team is migrating from external tables to Unity Catalog managed tables to reduce operational overhead. After the migration and enabling predictive optimization at the catalog level, a DBA asks what maintenance operations will be automatically handled by Databricks that previously required manual scheduling. Which of the following accurately describes ALL operations automatically executed by predictive optimization for Unity Catalog managed tables?

  1. AOPTIMIZE alone: it compacts small files and incrementally clusters new data, while VACUUM and statistics collection stay on manual schedules.
  2. BOPTIMIZE, VACUUM, ANALYZE, and ZORDER: it runs the three maintenance commands and also Z-orders files on frequently filtered columns.
  3. COPTIMIZE and VACUUM: it compacts files and removes unreferenced data, while ANALYZE is run separately to refresh optimizer statistics.
  4. DVACUUM and ANALYZE: it cleans up storage and refreshes statistics, while file compaction is left to user-scheduled OPTIMIZE jobs.
  5. EOPTIMIZE, VACUUM, and ANALYZE: it compacts and clusters files, removes unreferenced data files, and incrementally updates statistics.
Answer & explanation

Correct answer: E

WHY E: Predictive optimization for Unity Catalog managed tables automatically runs three operations: OPTIMIZE (file compaction and incremental liquid clustering), VACUUM (removes data files no longer referenced by the table, reducing storage costs), and ANALYZE (collects statistics to enable data skipping, improving query performance). All three are triggered without manual scheduling.

WHY NOT A: VACUUM and ANALYZE are also part of predictive optimization; ANALYZE incrementally updates statistics when data is written, enabling intelligent data skipping.

WHY NOT C: ANALYZE is also automated. Predictive optimization collects statistics as data is written, which is a core benefit for reducing query overhead.

WHY NOT D: OPTIMIZE is a primary operation of predictive optimization: it compacts small files and triggers incremental liquid clustering. Omitting it would defeat a major maintenance benefit.

WHY NOT B: ZORDER is NOT run by predictive optimization. The documentation states that OPTIMIZE does not run ZORDER when executed with predictive optimization; tables using Z-order have their Z-ordered files ignored. Liquid clustering (not ZORDER) is the recommended approach for managed tables.

Take the full DE Professional practice test free →

Would you pass today?

This question is one of 60 in the free, timed Databricks Data Engineer Professional practice test. Take it and get a section-by-section score.

Start the free test →