Question 940
A table is moved to a different schema and a team expects old namespace privileges to authorize it forever. How should the team avoid a repeat of this issue in production?
Explanation
Correct Answer
Include effective-grant checks in table moves. This is the most directly relevant preventive control because namespace hierarchy and inheritance affect effective access after object relocation. A concrete acceptance check is: Approved users keep access while former unrelated principals lose it. To reduce recurrence: Include effective-grant checks in table moves.
Incorrect Answers
Recorded data lineage exposes dependencies beyond a single source repository. That consideration does not remove the current constraint: namespace hierarchy and inheritance affect effective access after object relocation.
Incorrect metadata labels can drive unsafe discovery or ABAC behavior. In this situation, namespace hierarchy and inheritance affect effective access after object relocation.
Without metadata consumers cannot assess ownership and meaning reliably. For the observed behavior, namespace hierarchy and inheritance affect effective access after object relocation.