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