New Year Sale 2026! Hurry Up, Grab the Special Discount - Save 25% - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions

Snowflake ARA-C01 Exam - Topic 5 Question 56 Discussion

Actual exam question for Snowflake's ARA-C01 exam
Question #: 56
Topic #: 5
[All ARA-C01 Questions]

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

Show Suggested Answer Hide Answer
Suggested Answer: C

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 Snowflake is:

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.

The other options are not characteristics of RBAC as used in Snowflake:

A user can use a ''super-user'' access along with securityadmin to bypass authorization checks and access all databases, schemas, and underlying objects. This is not true, as there is no such thing as a ''super-user'' access in Snowflake. The securityadmin role is a predefined role that can manage users and roles, but it does not have any privileges on any database objects by default. To access any object, the securityadmin role must be explicitly granted the appropriate privilege by the object owner or another role with the grant option.

A user can create managed access schemas to support current and future grants and ensure only object owners can grant privileges to other roles. This is not true, as this contradicts the definition of a managed access schema. In a managed access schema, object owners cannot grant privileges on their objects to other roles, and only the schema owner or a role with the MANAGE GRANTS privilege can do so.


Overview of Access Control

A Functional Approach For Snowflake's Role-Based Access Controls

Snowflake Role-Based Access Control simplified

Snowflake RBAC security prefers role inheritance to role composition

Overview of Snowflake Role Based Access Control

Contribute your Thoughts:

0/2000 characters
Carri
1 day ago
C is also valid, managed access schemas are super useful.
upvoted 0 times
...
Colton
7 days ago
Wait, can super-users really bypass everything? Sounds risky!
upvoted 0 times
...
Reena
12 days ago
Totally agree with A, makes managing access easier.
upvoted 0 times
...
Cheryll
17 days ago
A) is correct, privileges can be inherited!
upvoted 0 times
...
Dulce
22 days ago
Definitely D. Snowflake's RBAC is all about granular control and ensuring only object owners can grant privileges.
upvoted 0 times
...
Yuette
27 days ago
D seems like the right answer. Managed access schemas are a key feature of RBAC in Snowflake.
upvoted 0 times
...
Rikki
1 month ago
I think the correct answer is D. It makes the most sense in the context of Snowflake's RBAC.
upvoted 0 times
...
Shasta
1 month ago
I think option D sounds right because it mentions both current and future grants, which seems more comprehensive for managed access schemas.
upvoted 0 times
...
Dino
1 month ago
I feel like the super-user access mentioned in option B is a bit misleading; I thought RBAC was all about restricting access rather than bypassing it.
upvoted 0 times
...
Stacey
2 months ago
I remember something about managed access schemas, but I can't recall if they only support future grants or if they also cover current ones.
upvoted 0 times
...
Dalene
2 months ago
I'm not totally sure, but I think the answer might be A. Privileges in Snowflake RBAC can be granted at the database level and inherited by underlying objects.
upvoted 0 times
...
Casie
2 months ago
I feel confident about this one. The answer is definitely D. Managed access schemas in Snowflake ensure only object owners can grant privileges to other roles.
upvoted 0 times
...
Aliza
2 months ago
I think RBAC in Snowflake allows privileges to be inherited, so I might lean towards option A, but I'm not entirely sure.
upvoted 0 times
...
Tyra
2 months ago
Okay, let me think this through. I know RBAC is about assigning permissions based on roles, not individual users. I think the key here is that the managed access schemas help control who can grant privileges.
upvoted 0 times
...
Candra
2 months ago
I think option A is correct. It makes sense for database management.
upvoted 0 times
...
Elli
3 months ago
Haha, I bet the "super-user" option is just a trap to catch the unwary. Nice try, Snowflake!
upvoted 0 times
...
Melda
3 months ago
D is the way to go. Snowflake's RBAC is designed to prevent unauthorized access and maintain data security.
upvoted 0 times
...
Reita
3 months ago
Hmm, I'm a bit confused on this one. I know RBAC is important for managing access, but I'm not sure about the specifics of how it works in Snowflake.
upvoted 0 times
...
Ayesha
3 months ago
I'm pretty sure the answer is C. RBAC in Snowflake allows you to create managed access schemas to control who can grant privileges.
upvoted 0 times
...

Save Cancel