Home / DE Associate practice test / Governance and Security / Question

Databricks Data Engineer Associate · free practice question

An analyst reports they cannot query main.sales.orders even though the table owner ran GRANT SELECT ON TABLE main.sales.orders to the analyst. The analyst…

Exam-style question on Governance and Security from the free DE Associate practice test, with the answer and a full explanation below.

Updated November 10, 2026

Governance and Security

An analyst reports they cannot query main.sales.orders even though the table owner ran GRANT SELECT ON TABLE main.sales.orders to the analyst. The analyst holds no other grants on the catalog or the schema. What is the minimum additional set of privileges required so the analyst can successfully read this table?

  1. AGrant MODIFY on the table in addition to SELECT; reading rows from a Unity Catalog table depends on holding both the read privilege and the write privilege on that same table before a query returns data.
  2. BGrant SELECT on the parent catalog main; the table-level SELECT is overridden by the missing catalog grant, and a catalog-level SELECT is what propagates downward and lets the analyst read the table.
  3. CGrant ALL PRIVILEGES on the metastore; querying a single table depends on metastore-level access, which then cascades downward through the catalog and the schema to reach the individual table.
  4. DGrant USE CATALOG on main and USE SCHEMA on main.sales; these two privileges are needed alongside SELECT for Unity Catalog to let the analyst reach the table through its parent catalog and schema.
  5. EGrant USE CATALOG on main; access to the catalog is sufficient alongside SELECT, as USE SCHEMA is implied for each schema once a user holds USE CATALOG on the catalog that contains that schema.
Answer & explanation

Correct answer: D

WHY D: To read a table a user needs SELECT on the table plus the traversal privileges USE CATALOG on its catalog and USE SCHEMA on its schema; without traversal the SELECT is unusable.

WHY NOT A: MODIFY is a write privilege and is not required to read; SELECT plus traversal suffices.

WHY NOT B: SELECT does not need to be re-granted at the catalog level. The table-level SELECT is valid and is not overridden; it just needs the traversal privileges.

WHY NOT C: Metastore-level ALL PRIVILEGES is excessive and not the minimum; USE CATALOG and USE SCHEMA are the missing pieces.

WHY NOT E: USE SCHEMA is not implied by USE CATALOG; the user still needs USE SCHEMA on main.sales as a separate grant.

Take the full DE Associate practice test free →

Would you pass today?

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

Start the free test →