Home / DE Professional practice test / Data Governance

Free · 8 questions with explanations

Data Governance: Databricks Data Engineer Professional Practice Questions

Exam-style questions on Data Governance. Pick your answer, then open the explanation to see why it's right — and why the other options are wrong.

Updated November 16, 2026

1 Data Governance

A data engineer must let a BI service principal read only the Gold-layer schema sales.gold, while a separate data science group needs read access to sales.gold and sales.silver but must never see the raw sales.bronze schema. The catalog sales also contains other schemas that neither principal should access. Following least privilege, which grant strategy is correct?

  1. AGrant SELECT on sales.gold to the BI service principal and SELECT on sales.gold and sales.silver to the data science group, with no USE CATALOG or USE SCHEMA grant on the catalog or schemas.
  2. BGrant USE CATALOG and SELECT on the sales catalog to both principals; then revoke SELECT on sales.bronze from the data science group and on sales.silver from the BI principal.
  3. CGrant USE CATALOG on sales to both principals; make the BI service principal the owner of sales.gold and the data science group the owner of sales.silver to give them read access.
  4. DGrant USE CATALOG on sales to both principals; grant USE SCHEMA and SELECT on sales.gold to the BI service principal, and on sales.gold and sales.silver to the data science group.
  5. EAdd both principals to one new group; grant that group USE CATALOG on sales, and USE SCHEMA and SELECT on sales.gold and sales.silver, with no grants to either principal directly.
Show answer & explanation

Correct answer: D

WHY D: Least privilege here means granting traversal (USE CATALOG on sales, USE SCHEMA on the needed schemas) plus SELECT scoped to exactly the schemas each principal requires, and never granting SELECT at the catalog level (which would be inherited by bronze and every other schema). This gives the BI principal gold alone and the data science group gold plus silver, with bronze and the other schemas unreachable. WHY NOT A: This assumes data privileges alone are enough. Without USE CATALOG/USE SCHEMA traversal privileges the SELECT cannot be exercised, so this fails to grant working access; traversal privileges are part of least privilege, not an over-grant. WHY NOT B: A catalog-wide SELECT inherits down to all schemas, including bronze and the other schemas; relying on targeted revokes to claw back access is error-prone and violates least privilege, and a revoke at the schema level does not remove a privilege inherited from the catalog grant. WHY NOT C: Ownership confers full control and management rights over the object, not just read access, which is far more than least-privilege read. It also leaves the data science group without access to sales.gold. WHY NOT E: The BI principal must not read silver; putting both principals in one group with silver and gold over-grants silver to the BI principal, violating least privilege.

2 Data Governance Medium

A data steward is applying tags to Unity Catalog securable objects to improve data discoverability. Which of the following statements about Unity Catalog tags is CORRECT?

  1. ATag inheritance applies to browsing: tags on a catalog appear on the schemas and tables beneath it in Catalog Explorer.
  2. BTags can be queried programmatically through views such as INFORMATION_SCHEMA.TABLE_TAGS and INFORMATION_SCHEMA.COLUMN_TAGS.
  3. CTo tag a table, a non-owner needs the APPLY TAG privilege alone; USE CATALOG and USE SCHEMA on the parents are not required.
  4. DTag keys are case-insensitive, which makes the keys 'PII' and 'pii' resolve to the same tag key when set on the same object.
  5. EA single table can hold at most 10 column tags in total across its columns, counted separately from table-level tags.
Show answer & explanation

Correct answer: B

WHY B: Each catalog created in Unity Catalog includes an INFORMATION_SCHEMA. Its tag views (INFORMATION_SCHEMA.TABLE_TAGS, INFORMATION_SCHEMA.COLUMN_TAGS, INFORMATION_SCHEMA.SCHEMA_TAGS, INFORMATION_SCHEMA.CATALOG_TAGS, and INFORMATION_SCHEMA.VOLUME_TAGS) let tags be retrieved programmatically with SQL. This is a primary mechanism for auditing, reporting, and automating governance based on metadata. WHY NOT A: Tag inheritance in Unity Catalog applies when evaluating ABAC (attribute-based access control) policies. Tags do NOT inherit for browsing or metadata display: a tag on a catalog does not appear as a tag on its schemas or tables. The implicit inheritance is a policy-evaluation mechanism. WHY NOT C: To apply a tag to a table, a user must own the object OR have the APPLY TAG privilege on the object AND USE SCHEMA on the parent schema AND USE CATALOG on the parent catalog. A non-owner therefore needs the three privileges together, not APPLY TAG by itself. WHY NOT D: Tag keys are CASE-SENSITIVE in Unity Catalog. The keys 'PII' and 'pii' are two distinct tag keys and can both exist on the same object. This is an explicit constraint documented in the tags reference. WHY NOT E: A single table can have a maximum of 1,000 column tags in total across its columns (not 10). In addition, each individual securable object (table, column, etc.) can have at most 50 tags assigned to it.

3 Data Governance

A governance requirement states that in the hr.employees table, non-HR users must see the salary column as NULL while HR users see the true value, and all users must only see rows for their own department. The team wants to enforce this centrally on the base table so every downstream query and BI tool inherits the rules, without maintaining a separate secured view. Which Unity Catalog approach implements both requirements directly on the table?

  1. ACreate a dynamic view hr.employees_secure with CASE WHEN is_member('hr') logic for salary and a WHERE clause on department, then revoke SELECT on the base table; a secured view is the only way to combine column and row rules, so downstream tools must point at the view.
  2. BAttach a column mask function to the salary column that returns NULL unless is_account_group_member('hr'), and attach a row filter function to the table that restricts rows to the caller's department; both are Unity Catalog table-level policies that apply to every query against the base table.
  3. CEnable Delta table columnMasking and rowFiltering properties set to true and list the protected column and predicate in TBLPROPERTIES; Unity Catalog reads these properties and enforces masking and filtering automatically without any function.
  4. DGrant SELECT on all columns except salary to non-HR users using column-level GRANT, and partition the table by department so that department-scoped GRANTs restrict rows; column and partition GRANTs together achieve masking and row security on the base table.
  5. EUse two row filters — one that nullifies salary and one that restricts departments — because row filters can both drop rows and rewrite column values; column masks are only for hashing and cannot return NULL conditionally.
Show answer & explanation

Correct answer: B

WHY B: Unity Catalog provides two table-attached fine-grained controls: column masks (a UDF bound to a column that rewrites its returned value, e.g., NULL for non-HR via is_account_group_member) and row filters (a UDF bound to the table that returns a boolean predicate to restrict visible rows, e.g., matching the caller's department). Both are enforced on the base table for every query and tool. WHY NOT A: A dynamic view works but is exactly the 'separate secured view' the requirement wants to avoid; row filters and column masks let you enforce on the base table itself. WHY NOT C: There are no columnMasking/rowFiltering boolean table properties that auto-enforce from a predicate list; masks and filters are implemented as UDF policies attached to the column/table. WHY NOT D: Column-level GRANTs remove a column entirely for a principal (they do not mask to NULL selectively), and partitioning does not enforce per-user row security. WHY NOT E: Column masks CAN conditionally return NULL and are the correct primitive for the salary rule; row filters only include/exclude rows and cannot rewrite a column's value.

4 Data Governance

A data governance lead wants business users to find trustworthy tables by searching for business concepts (e.g., 'PII', 'gold', 'customer 360') and to see human-readable descriptions of tables and columns directly in the catalog. The solution must be queryable and enforceable through Unity Catalog metadata rather than an external spreadsheet. Which combination of Unity Catalog features best supports discoverability at scale?

  1. AAdd COMMENT descriptions to catalogs, schemas, tables, and columns, and apply Unity Catalog key-value tags such as pii=true or layer=gold to tables and columns.
  2. BRecord descriptions and classifications as TBLPROPERTIES key-value pairs on each table, and have business users find them with SHOW TBLPROPERTIES queries.
  3. CKeep descriptions and tags in a Delta catalog_metadata mapping table keyed by table and column name, and join it to information_schema.tables for search.
  4. DEncode concepts in table and column names, such as a pii_ prefix on sensitive columns, and treat COMMENT text as display notes that search does not index.
  5. EPublish descriptions and tags as Databricks Marketplace listings for each internal table, and have business users search a private exchange by concept.
Show answer & explanation

Correct answer: A

WHY A: Unity Catalog supports COMMENT descriptions on every securable level (catalog, schema, table, column) for human-readable documentation, and it supports tags (key-value pairs such as pii=true or layer=gold) on tables and columns for classifying business concepts like PII or medallion layer. Both live in Unity Catalog and are searchable/queryable (including via information_schema and system tables), enabling concept-based discovery at scale. WHY NOT B: Table properties are table-level configuration, not the discovery mechanism: they cannot describe individual columns and are not what catalog search uses. Tags ARE supported on Unity Catalog securables, and restricting metadata to TBLPROPERTIES ignores comments and column-level tagging. WHY NOT C: A hand-maintained mapping table is the external-spreadsheet pattern the stem rules out, just stored in Delta. Unity Catalog can store descriptions and tags natively, so an external mapping table is unnecessary and not the recommended pattern. WHY NOT D: Comments and tags are queryable metadata, not display-only, so name conventions are not the only searchable option and are far less flexible; renaming columns to encode concepts also breaks downstream code. WHY NOT E: Databricks Marketplace and private exchanges share data products with other organizations or workspaces; they are not how internal tables are documented. Discoverability metadata (comments, tags) applies to internal Unity Catalog objects; it is not exclusive to Marketplace.

5 Data Governance Medium

A data governance team wants all users in the Databricks account to be able to discover tables registered in a newly created catalog called analytics — meaning users can view the catalog, its schemas, and table names in Catalog Explorer and search results, even if they cannot yet query the data. The catalog was created via SQL. What is the MINIMUM privilege the team needs to grant, and to which principal?

  1. AGrant USE CATALOG on analytics to All account users.
  2. BGrant SELECT on analytics to All account users.
  3. CGrant BROWSE on analytics to All account users.
  4. DGrant ALL PRIVILEGES on analytics to All account users.
Show answer & explanation

Correct answer: C

WHY C is correct: The BROWSE privilege on a catalog allows users to view an object's metadata — including catalog, schema, and table names — using Catalog Explorer, the schema browser, search results, and the lineage graph without granting any access to actual data. Databricks explicitly recommends granting BROWSE on catalogs to the 'All account users' group to make objects discoverable and allow all users to request access. Crucially, catalogs created via SQL statements, the REST API, or the Databricks CLI do NOT grant BROWSE by default — it must be explicitly granted. USE CATALOG is NOT required to view metadata if the user has BROWSE on the catalog. WHY NOT A: USE CATALOG on a catalog allows a user to interact with objects within the catalog (i.e., run queries), but it does not enable discovery on its own without SELECT or other data access privileges. Granting USE CATALOG to all account users would allow them to traverse the hierarchy but not query data — however, it is a broader grant than needed and is not the targeted discovery mechanism Databricks recommends. WHY NOT B: SELECT grants read access to data in tables and views. This is far broader and more permissive than needed for mere discoverability. Granting SELECT to all account users on the entire catalog would expose all data, violating least privilege. WHY NOT D: ALL PRIVILEGES on a catalog grants every applicable privilege to all users on every existing and future object in the catalog. This is an extreme grant that would expose all data and enable modifications, violating fundamentally the principle of least privilege.

6 Data Governance

An analyst is granted SELECT on finance.reports.revenue but reports they cannot query it — the table does not even appear when they browse the catalog, and SELECT fails with a permission error on the schema. The table owner confirms the SELECT grant on the table itself is present and correct. Which additional privileges does Unity Catalog require for the analyst to successfully read the table?

  1. AThe analyst needs USAGE on the metastore and BROWSE on the catalog; USAGE on the metastore is the top-level privilege that cascades read access down to any table with a SELECT grant.
  2. BThe analyst must be made the owner of the table, because in Unity Catalog only the owner or the metastore admin can run SELECT, regardless of any SELECT grant.
  3. CThe analyst needs MODIFY on the schema in addition to SELECT on the table, since MODIFY is what makes a securable visible in the catalog browser and enables read traversal.
  4. DNo extra grant is needed at the Unity Catalog level; the failure means the analyst lacks the underlying cloud storage credential, so the fix is to grant them direct read access to the table's storage path.
  5. EThe analyst also needs USE CATALOG on finance and USE SCHEMA on finance.reports; these traversal privileges are required to reach a securable, and without them a table-level SELECT cannot be exercised even though it exists.
Show answer & explanation

Correct answer: E

WHY E: To read a table in Unity Catalog, a principal needs the data privilege (SELECT) on the table AND the traversal privileges to reach it: USE CATALOG on the parent catalog and USE SCHEMA on the parent schema. Missing traversal privileges make the object invisible and block the query even when SELECT is granted. WHY NOT B: Ownership is not required to SELECT; a SELECT grant is sufficient once traversal privileges are present. WHY NOT C: MODIFY grants write (insert/update/delete) capability, not catalog visibility or read traversal; the traversal privileges are USE CATALOG/USE SCHEMA. WHY NOT D: Unity Catalog manages storage access via the table's managed/external credential; analysts do not need direct cloud storage grants, and the error is a UC traversal issue, not a raw storage permission. WHY NOT A: BROWSE aids discovery but is not what enables the read, and there is no metastore-level USAGE privilege that cascades SELECT to all tables; traversal is via USE CATALOG/USE SCHEMA.

7 Data Governance Hard

A data engineer runs the following command: ``sql GRANT SELECT ON CATALOG main TO analyst_team; ` A new table called main.reporting.revenue is created one week later. Which of the following statements CORRECTLY describes analyst_team`'s access to this new table?

  1. Aanalyst_team has no access to main.reporting.revenue because privileges must be re-granted after new objects are created.
  2. Banalyst_team has SELECT on main.reporting.revenue but still needs USE SCHEMA on main.reporting and USE CATALOG on main granted separately, since catalog-level grants do not cover navigation privileges.
  3. Canalyst_team can SELECT from main.reporting.revenue only after the table owner explicitly grants SELECT on that specific table.
  4. Danalyst_team can SELECT from main.reporting.revenue because privilege inheritance causes the catalog-level SELECT grant to automatically apply to all current and future tables in the catalog.
Show answer & explanation

Correct answer: D

WHY D is correct: Unity Catalog uses a privilege inheritance model where privileges granted at a higher level in the object hierarchy automatically apply to all current AND future objects beneath it. The documentation explicitly states: 'Since privileges are inherited, you can grant a user the SELECT privilege on a catalog or schema, which automatically grants the user SELECT privilege on all current and future tables, and views in the catalog or schema.' Furthermore, granting SELECT at the catalog level implicitly covers the necessity to traverse the hierarchy — the GRANT at the catalog level encompasses the USE CATALOG privilege on that same catalog. Similarly, USE SCHEMA is also covered by the catalog-level grant because all descendant privileges inherit downward. The analyst team can therefore immediately query main.reporting.revenue without any further explicit grants. WHY NOT A: This is incorrect. Privilege inheritance means existing catalog-level grants propagate to future objects automatically. There is no requirement to re-grant privileges each time a new object is created when the grant was made at the catalog level. WHY NOT C: With a catalog-level SELECT grant in place, there is no need for the table owner to grant SELECT on individual tables. Inheritance eliminates the need for object-by-object grants for users who already have the privilege at a higher level. WHY NOT B: When SELECT is granted at the catalog level, USE CATALOG and USE SCHEMA are implicitly satisfied as part of the catalog-level inheritance. They do not need to be granted separately; the catalog-level grant covers the full navigation chain needed to access objects within that catalog.

8 Data Governance

A data engineer grants a group SELECT on a Unity Catalog catalog analytics and separately grants the same group SELECT on schema analytics.reporting. A new table analytics.reporting.kpis is later created, and a new schema analytics.staging is later created. The engineer must predict, without issuing any further grants, which objects the group can read. Which statement correctly describes Unity Catalog's inheritance behavior?

  1. AOnly the schema-level grant matters because the more specific grant overrides the catalog grant; the group can read tables under analytics.reporting (including kpis) but not under analytics.staging, since the catalog grant is suppressed once a schema-level grant exists.
  2. BPrivileges are not inherited downward in Unity Catalog; the group can read only objects on which it holds an explicit grant, so it can read neither analytics.reporting.kpis nor any table under analytics.staging until each table is granted individually.
  3. CInheritance flows downward but not to objects created after the grant, so the group can read tables that existed when the grant was issued but must be re-granted for analytics.reporting.kpis and the new analytics.staging schema.
  4. DA privilege granted on a securable is inherited by all current and future child securables, so SELECT on the analytics catalog already lets the group read every table in every schema — including the later-created analytics.reporting.kpis and everything under analytics.staging — making the schema-level grant redundant.
  5. EThe catalog grant confers only USE CATALOG visibility, not read access; the group can read tables under analytics.reporting because of the schema grant, but the catalog SELECT does nothing on its own and grants no access to analytics.staging.
Show answer & explanation

Correct answer: D

WHY D: Unity Catalog privileges are inherited by child securables, and inheritance applies to both existing and future children. A SELECT on the analytics catalog therefore already grants read on every table in every schema, including tables and schemas created later (analytics.reporting.kpis, analytics.staging), which makes the additional schema-level grant redundant. WHY NOT B: Unity Catalog DOES inherit privileges downward from catalog to schema to table; access is not limited to explicitly granted objects. WHY NOT C: Inheritance is not frozen at grant time — future child objects also inherit the privilege. WHY NOT A: A more specific grant does not suppress or override a broader inherited grant; grants are additive, so the catalog SELECT still applies to analytics.staging. WHY NOT E: A SELECT granted at the catalog level is a data privilege that is inherited by child tables; it is more than USE CATALOG visibility and does confer read access under new schemas.

Take the full DE Professional practice test →