Databricks Certified Context Engineer Associate Practice Mode

Community Discussion

Written by other learners. Comments can disagree with the marked answer — check the official documentation when in doubt.

• Chose E0

  - Correct answer : E — A grant controls whether a principal can access a table at all, while a row filter restricts which specific rows a principal sees within a table they can already access. A . Incorrect. Unity Catalog grants are not scoped only to Genie spaces; they control access to any securable object (e.g., tables, views) across Databricks. Row filters operate at query time on tables, not exclusively during AI Search indexing, and they limit visible rows regardless of the access interface. B . Incorrect. Grants do not filter columns—that is the role of column masks. Row filters are enforced at query time on the active data, not merely at indexing time; they dynamically restrict rows for each query, rather than being baked into indexes. C . Incorrect. While grants are enforced at query time, row filters are also enforced dynamically at query time and are not limited to table creation. Row filters apply to the live Delta table content and are not permanently baked into the data, so this option misrepresents their enforcement. D . Incorrect. Grants and row filters are distinct mechanisms: grants control object-level access, while row filters restrict row-level visibility. They do not both target columns, and they address retrieval failures differently—row filters do not act as column masks. E . Correct. A Unity Catalog grant (e.g., SELECT) decides whether a principal can access a table at all, acting as a coarse permission. A row filter applies after table access is granted, narrowing the result set to only those rows the principal is allowed to see, thus providing fine-grained control.