Question 820
A developer grants SELECT at the schema level and is surprised that newly created tables are queryable. Which prevention step most appropriately addresses the root cause?
Explanation
Correct Answer
Review inherited grants before applying schema-wide access. This is the most directly relevant preventive control because schema-level grants can propagate to child objects under the Unity Catalog model. A concrete acceptance check is: A newly created restricted table is not visible to the general analyst role. To reduce recurrence: Review inherited grants before applying schema-wide access.
Incorrect Answers
Governance without ownership leaves policy decisions and incident response unassigned. In this situation, schema-level grants can propagate to child objects under the Unity Catalog model.
Incorrect metadata labels can drive unsafe discovery or ABAC behavior. For the observed behavior, schema-level grants can propagate to child objects under the Unity Catalog model.
Recorded data lineage exposes dependencies beyond a single source repository. The controlling issue in this question is that schema-level grants can propagate to child objects under the Unity Catalog model.