SOL-C01 · Question #68
A data warehouse contains a table named 'ORDERS in schema SALES'. The current owner of the ORDERS' table is the `ANALYST role. The compliance team requires that the ownership be transferred to the 'SE
The correct answer is A. Immediately execute 'ALTER TABLE SALES.ORDERS TRANSFER OWNERSHIP TO ROLE. Transferring ownership directly via ALTER TABLE SALES.ORDERS TRANSFER OWNERSHIP TO ROLE SECURITY_ADMIN (Option A) is correct because it is an atomic, in-place operation - it reassigns ownership metadata instantly without modifying the table's data, structure, or active sessions,
Question
A data warehouse contains a table named 'ORDERS in schema SALES'. The current owner of the ORDERS' table is the `ANALYST role. The compliance team requires that the ownership be transferred to the 'SECURITY ADMIN' role, but without interrupting any existing queries or processes that use the table. What is the recommended approach to transfer ownership with minimal disruption?
Options
- AImmediately execute 'ALTER TABLE SALES.ORDERS TRANSFER OWNERSHIP TO ROLE
- BCreate a clone of the 'ORDERS table, transfer ownership of the clone, then drop the original
- CCreate a view on top of the 'ORDERS' table, transfer ownership of the view to 'SECURITY
- DExecute 'ALTER TABLE SALES.ORDERS TRANSFER OWNERSHIP TO ROLE
- ECreate a new table with the same structure as 'ORDERS' , load data into it, grant all privileges to
How the community answered
(28 responses)- A75% (21)
- B7% (2)
- C14% (4)
- E4% (1)
Explanation
Transferring ownership directly via ALTER TABLE SALES.ORDERS TRANSFER OWNERSHIP TO ROLE SECURITY_ADMIN (Option A) is correct because it is an atomic, in-place operation - it reassigns ownership metadata instantly without modifying the table's data, structure, or active sessions, meaning running queries are never interrupted.
Why the distractors fail:
- B (Clone → transfer → drop original): Cloning creates a different object with a different name; dropping the original breaks all existing references and queries - exactly the disruption you're trying to avoid.
- C (Create a view): Transferring ownership of a view is irrelevant - the underlying
ORDERStable ownership remains withANALYST. This solves nothing. - D: Likely a variation with a problematic flag (e.g.,
REVOKE CURRENT GRANTSor incorrect syntax) that would invalidate existing privileges, causing disruption. - E (New table + load data): Requires a full data migration, introduces downtime risk, and breaks all existing object references - the most disruptive option possible.
Memory tip: Think of ownership transfer like changing the name on a property deed - the house (table, data, sessions) doesn't move, only the recorded owner changes. ALTER ... TRANSFER OWNERSHIP is always the surgical, non-destructive first choice for compliance-driven ownership changes.
Topics
Community Discussion
No community discussion yet for this question.