Home / Data Analyst practice test / Analyzing Queries / Question

Databricks Data Analyst Associate · free practice question

A data analyst in a Databricks SQL Editor frequently reruns the same complex query during iterative development. She notices that after the first run…

Exam-style question on Analyzing Queries from the free Data Analyst practice test, with the answer and a full explanation below.

Updated November 10, 2026

Analyzing Queries

A data analyst in a Databricks SQL Editor frequently reruns the same complex query during iterative development. She notices that after the first run, subsequent reruns return almost instantly. Which Databricks mechanism is responsible for this behavior, and what is a potential drawback the analyst should be aware of?

  1. ALiquid Clustering — co-locates related rows in fewer files, which shortens scans on reruns of the same query; the drawback is that clustering is applied asynchronously and newly written rows stay unclustered until OPTIMIZE runs
  2. BQuery result caching — an identical rerun is served from the cached result instead of executing again on the warehouse; the drawback is that no Query Profile is generated for cache-served runs, which can obscure performance diagnostics
  3. CDisk cache (Delta cache) — keeps decompressed copies of the table files on local NVMe storage for fast repeated scans; the drawback is that the cache is per-node and is lost on restart, with the next cold run paying for full scans again
  4. DPhoton vectorized execution — the first run warms the Photon JIT compiler and later runs of the query reuse the compiled code; the drawback is that the warmup takes about three executions of the query to reach full acceleration
  5. EMaterialized view auto-refresh — reruns reuse pre-computed results from a materialized view that covers the query pattern; the drawback is that the view needs a schedule or TRIGGER ON UPDATE and can serve stale rows between refreshes
Answer & explanation

Correct answer: B

WHY B: Databricks SQL has a query result cache. When an identical query is run again, the cached result is returned almost instantly without compute execution. The documented drawback is that no Query Profile is available for cache-served queries; to get a fresh profile, the analyst has to make a trivial change to the query.

WHY NOT A: Liquid Clustering speeds up file pruning at scan time but does not return instant results; the query is still executed on each rerun.

WHY NOT C: Disk caching warms up scan I/O but does not return pre-computed result sets; query execution still runs on every rerun.

WHY NOT D: Photon does not have a JIT warmup phase that spans several executions of a query in the way described.

WHY NOT E: Materialized views are separate objects that have to be created explicitly; they do not intercept and cache ad hoc queries run in the SQL Editor.

Take the full Data Analyst practice test free →

Would you pass today?

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

Start the free test →