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?
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.