Unity Catalog objects, privileges and storage responsibility
Resolve objects in their hierarchy
Unity Catalog uses a catalog, schema and object hierarchy for a fully qualified table name. A metastore has its supported regional and workspace relationships; attachment is not a substitute for data authorization. An object’s existence does not mean every user can discover or query it. To read a table, evaluate the applicable parent usage privileges and SELECT under the actual privilege model, as well as workspace bindings and other relevant controls. A schema-level inherited privilege can affect existing and future children without removing those other conditions.
Keep cloud storage and table lifecycle distinct
A storage credential represents relevant cloud-access authority, while an external location associates that authority with a governed path. Creating an external table requires the appropriate parent and location privileges in the selected model. The same cloud path should not become an uncontrolled alternate route around governance. Managed and external tables assign different lifecycle responsibilities: removing external-table metadata is not automatically deletion of its data. Managed-table removal follows the supported lifecycle and recovery behavior; do not infer an instantaneous irreversible file erasure from a simplified DROP example.
Authorize the minimum relevant operation
Privileges, ownership and administrative capabilities are different concepts. A role able to manage grants should not be assumed to have automatically received SELECT, yet its power to change permissions still makes it sensitive. A revoke removes a particular grant; inherited, group or alternative grants can leave effective access. Do not invent an explicit deny mechanism or assume that revoking one path proves access is gone. Review the effective principal, parent privileges, ownership and any supported fine-grained policy.
Govern sharing and evidence
Row filters, column masks and governed views can restrict supported query results, but their exact owner, compute and function semantics require the current model. A tag labels an asset and does not automatically create an enforcement rule. Delta Sharing provides controlled sharing mechanisms under supported recipient arrangements; credential scope and recipient handling still matter. Lineage and audit records support investigation and impact analysis within their actual capture coverage, not a guarantee that every possible external operation is visible. Treat these observations as potentially sensitive. No grant, table deletion, external connection or share is created by this written exercise, and its editorial practice mix is not a complete official current platform blueprint.