What does Snowflake recommend regarding database object ownership? (Select TWO).

Question

Options

• ACreate objects with ACCOUNTADMIN and do not reassign ownership.
• BCreate objects with SYSADMIN.
• CCreate objects with SECURITYADMIN to ease granting of privileges later.
• DCreate objects with a custom role and grant this role to SYSADMIN.
• EUse only MANAGED ACCESS SCHEMAS for66 objects owned by ACCOUNTADMIN.

• A
  8% (2)
• B
  88% (23)
• C
  4% (1)

Explanation

Snowflake's role hierarchy best practice keeps ACCOUNTADMIN reserved for account-level administration only, not for owning database objects. The recommended pattern is: (B) use SYSADMIN as the top-level object owner for all database objects, and (D) create custom roles for specific object ownership and grant those custom roles TO SYSADMIN. This keeps the privilege hierarchy clean - SYSADMIN inherits all privileges from custom roles, and ACCOUNTADMIN inherits from SYSADMIN. Option A is wrong because ACCOUNTADMIN ownership is an anti-pattern. Option C is wrong because SECURITYADMIN is for managing users and roles, not owning objects. Option E is incorrect because MANAGED ACCESS SCHEMAS control who can grant privileges on schema objects - they are unrelated to the ownership recommendation.

No community discussion yet for this question.