Home / DE Professional practice test / Data Modelling / Question

Databricks Data Engineer Professional · free practice question

A data engineering team enables automatic liquid clustering (`CLUSTER BY AUTO`) on a Unity Catalog managed Delta table using Databricks Runtime 15.4 LTS. Which…

Exam-style question on Data Modelling from the free DE Professional practice test, with the answer and a full explanation below.

Updated November 16, 2026

Data Modelling Medium

A data engineering team enables automatic liquid clustering (CLUSTER BY AUTO) on a Unity Catalog managed Delta table using Databricks Runtime 15.4 LTS. Which of the following statements CORRECTLY describes how automatic liquid clustering selects and maintains clustering keys?

  1. AAutomatic liquid clustering selects the highest-cardinality column at table creation and keeps it as the clustering key while query patterns evolve.
  2. BAutomatic liquid clustering takes an initial set of clustering columns from the engineer and then tunes their order while keeping the same columns.
  3. CAutomatic liquid clustering picks keys from the table's historical query workload and changes them when predicted savings exceed the clustering cost.
  4. DAutomatic liquid clustering applies clustering synchronously during each write, reclustering the existing records on each INSERT to keep the layout.
Answer & explanation

Correct answer: C

WHY C: The Databricks documentation describes automatic liquid clustering as follows: (1) 'Analyzes query workload: Databricks analyzes the table's historical query workload and identifies the best candidate columns for clustering.' (2) 'Adapts to changes: If your query patterns or data distributions change over time, automatic liquid clustering selects new keys to optimize performance.' (3) 'Cost-aware selection: Databricks changes clustering keys only when the predicted cost savings from data skipping improvements outweigh the data clustering cost.' Additionally, automatic key selection requires predictive optimization and runs asynchronously as a maintenance operation, not during writes.

WHY NOT A: Automatic liquid clustering does NOT select a fixed column at creation time and hold it. Its defining characteristic is adaptation: if query patterns change over time, the platform selects new clustering keys to reflect the updated workload. Cardinality alone does not determine key selection; historical query filter patterns are the primary signal.

WHY NOT B: CLUSTER BY AUTO does NOT require the engineer to specify initial clustering columns. The point is that Databricks selects the keys based on workload analysis. Engineers specify CLUSTER BY AUTO (or ALTER TABLE ... CLUSTER BY AUTO) and the platform handles key selection.

WHY NOT D: Automatic liquid clustering does NOT recluster the existing records on every INSERT. OPTIMIZE operations trigger the incremental physical reclustering, and they run asynchronously via predictive optimization. Write operations apply clustering on write only when data in the transaction meets a defined size threshold. Reclustering every record on every write would be prohibitively expensive for large 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 →