Home / DE Professional practice test / Ensuring Data Security and Compliance / Question

Databricks Data Engineer Professional · free practice question

A team is designing a row-level security solution using Unity Catalog row filters. A data engineer raises a concern about a legacy reporting cluster running…

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

Updated November 16, 2026

Ensuring Data Security and Compliance Medium

A team is designing a row-level security solution using Unity Catalog row filters. A data engineer raises a concern about a legacy reporting cluster running Databricks Runtime 11.3 LTS that will occasionally query the protected table. What is the ACTUAL behavior when that cluster queries a table with a row filter assigned?

  1. AThe query succeeds and returns the unfiltered table, with the row filter skipped on the older runtime.
  2. BThe query returns the rows the current user is allowed to see, with the filter enforced by the metastore.
  3. CThe query fails with an error and returns no data to the cluster, whichever user submits the query.
  4. DThe query succeeds, but the filter runs after the full table is fetched, which slows the query down.
  5. EThe query returns a single row holding a warning that the runtime version does not support row filters.
Answer & explanation

Correct answer: C

WHY C: Unity Catalog row filters and column masks are enforced with a 'fail-secure' design. On Databricks Runtime versions below 12.2 LTS, any query against a table that has row filters or column masks attached fails and returns no data. This prevents accidental exposure of restricted data on older runtimes that cannot correctly enforce the filter logic.

WHY NOT A: Returning unfiltered rows on an unsupported runtime would be a security vulnerability. Databricks explicitly chose the fail-secure approach: no data is returned rather than all data.

WHY NOT B: Row filters are not enforced at the metastore level independently of the compute runtime. Enforcement happens in the query engine, which is runtime-dependent; older runtimes cannot enforce filters, hence the fail-secure fallback.

WHY NOT D: The fail-secure design does not degrade silently. The query does not fetch rows and then apply the filter late; it fails entirely on unsupported runtimes.

WHY NOT E: There is no 'warning row' behavior. The query simply fails with an error and no data, to prevent any data leakage.

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 →