A group holds SELECT granted at the catalog level on a finance catalog, which is the intended arrangement for most of its schemas. A payroll schema inside that catalog must become unreadable by the group, while every other schema in the catalog stays readable and the catalog-level grant itself stays in place. Which single statement meets the requirement?
GRANT SELECT ON CATALOG finance TO `analysts`;- AIssue REVOKE SELECT ON SCHEMA finance.payroll FROM `analysts`, which removes the inherited privilege at that specific point in the securable hierarchy.
- BBuild a dynamic view over each payroll table and grant SELECT on those views alone, which is the supported way to hide an entire schema from a group.
- CAttach a row filter to every payroll table that returns no rows for members of the group, which blocks the data without touching the catalog-level grant.
- DIssue DENY SELECT ON SCHEMA finance.payroll TO `analysts`, which takes precedence over the SELECT privilege inherited from the parent catalog. Correct
Why A is wrong: It is tempting because REVOKE is the natural opposite of GRANT, but REVOKE only deletes a grant recorded on the object it names, and no grant was ever recorded on the payroll schema, so the inherited privilege survives.
Why B is wrong: It is tempting because dynamic views are a genuine Unity Catalog tool for restricting what a group sees, but they add an object rather than remove access, and the group would keep reading the underlying payroll tables directly.
Why C is wrong: It is tempting because a row filter does suppress rows, but the group retains SELECT and can still read the table structure, and maintaining a filter on every table is not the single statement the requirement asks for.
Why D is correct: Correct. A DENY recorded on a schema overrides any matching privilege inherited from above it, so one statement carves the payroll schema out while the catalog-level grant continues to serve every other schema.