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

Databricks Data Engineer Associate · free practice question

A security team wants to ensure that one specific user can never read main.hr.salaries, even though that user belongs to a group that has been granted SELECT…

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

A security team wants to ensure that one specific user can never read main.hr.salaries, even though that user belongs to a group that has been granted SELECT on the table. Working entirely within Unity Catalog privilege management, what is the correct understanding of how to enforce this restriction?

  1. ARun DENY SELECT ON TABLE main.hr.salaries to the user, because Unity Catalog evaluates an explicit DENY ahead of any group SELECT grant and this is the standard supported way to block a single member of a permitted group.
  2. BRun REVOKE SELECT ON TABLE main.hr.salaries from the user, because a REVOKE issued against the individual overrides the SELECT that the user inherited through the group while leaving the rest of the group entirely unaffected.
  3. CUnity Catalog has no DENY statement, so the engineer cannot explicitly block one user; REVOKE removes only direct grants, so the user must be removed from the group or the group's SELECT grant on the table must be changed.
  4. DAdd the user to a DENY list on the parent catalog main, because a catalog-level deny list in Unity Catalog automatically excludes the listed principals from every child schema and table regardless of any group grant.
  5. EGrant the user a lower-priority SELECT carrying a restrictive condition, because when two conflicting grants exist Unity Catalog applies the most restrictive of them and thereby effectively denies access to that one user.
Answer & explanation

Correct answer: C

WHY C: Unity Catalog has no DENY (only hive_metastore had DENY), and REVOKE only removes a direct grant, so a user cannot be blocked while the group retains SELECT; you must remove the user from the group or change the group grant. WHY NOT A: DENY does not exist in Unity Catalog, so this statement cannot be run. WHY NOT B: REVOKE removes only direct grants; the user has no direct grant here, so revoking from the individual does nothing against the group's SELECT. WHY NOT D: There is no catalog-level deny list feature in Unity Catalog. WHY NOT E: Unity Catalog grants are additive with no priority or most-restrictive-wins conflict resolution, so this does not deny access.

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 →