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