What is a characteristic of Role-Based Access Control (RBAC) as used in Snowflake?

Question

Options

• APrivileges can be granted at the database level and can be inherited by all underlying objects.
• BA user can use a "super-user" access along with securityadmin to bypass authorization checks
• CA user can create managed access schemas to support future grants and ensure only schema
• DA user can create managed access schemas to support current and future grants and ensure only

• A
  5% (2)
• B
  2% (1)
• C
  90% (38)
• D
  2% (1)

Explanation

Role-Based Access Control (RBAC) is the Snowflake Access Control Framework that allows privileges to be granted by object owners to roles, and roles, in turn, can be assigned to users to restrict or allow actions to be performed on objects. A characteristic of RBAC as used in Privileges can be granted at the database level and can be inherited by all underlying objects. This means that a role that has a certain privilege on a database, such as CREATE SCHEMA or USAGE, can also perform the same action on any schema, table, view, or other object within that database, unless explicitly revoked. This simplifies the access control management and reduces the number of grants required. A user can create managed access schemas to support future grants and ensure only schema owners can grant privileges to other roles. This means that a user can create a schema with the MANAGED ACCESS option, which changes the default behavior of object ownership and privilege granting within the schema. In a managed access schema, object owners lose the ability to grant privileges on their objects to other roles, and only the schema owner or a role with the MANAGE GRANTS privilege can do so. This enhances the security and governance of the schema and its objects.

No community discussion yet for this question.