Question 190
A table is moved to a different schema and a team expects old namespace privileges to authorize it forever. How should the team correct this issue while preserving the required data contract?
Explanation
Correct Answer
Re-evaluate catalog/schema/table grants and ownership after the move. This is the most directly relevant remediation 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
A table name and schema alone cannot establish operational trust for consumers. That consideration does not remove the current constraint: namespace hierarchy and inheritance affect effective access after object relocation.
Catalog descriptions do not change stored values or validation logic. In this situation, namespace hierarchy and inheritance affect effective access after object relocation.
Recorded data lineage exposes dependencies beyond a single source repository. The controlling issue in this question is that namespace hierarchy and inheritance affect effective access after object relocation.