Deal of The Day! Hurry Up, Grab the Special Discount - Save 25% - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions

Snowflake ADA-C01 Exam - Topic 4 Question 49 Discussion

Actual exam question for Snowflake's ADA-C01 exam
Question #: 49
Topic #: 4
[All ADA-C01 Questions]

When adding secure views to a share in Snowflake, which function is needed to authorize users from another account to access rows in a base table?

Show Suggested Answer Hide Answer
Suggested Answer: C

According to the Working with Secure Views documentation, secure views are designed to limit access to sensitive data that should not be exposed to all users of the underlying table(s). When sharing secure views with another account, the view definition must include a function that returns the identity of the user who is querying the view, such as CURRENT_USER, CURRENT_ROLE, or CURRENT_ACCOUNT. These functions can be used to filter the rows in the base table based on the user's identity. For example, a secure view can use the CURRENT_USER function to compare the user name with a column in the base table that contains the authorized user names. Only the rows that match the user name will be returned by the view. The CURRENT_CLIENT function is not suitable for this purpose, because it returns the IP address of the client that is connected to Snowflake, which is not related to the user's identity.


Contribute your Thoughts:

0/2000 characters
Arlette
17 days ago
Definitely CURRENT_ACCOUNT! Can't believe people get this wrong.
upvoted 0 times
...
Gertude
23 days ago
Wait, is it really CURRENT_ROLE? That seems off.
upvoted 0 times
...
Avery
28 days ago
I thought it was CURRENT_USER, but I guess not.
upvoted 0 times
...
Bobbie
1 month ago
It's CURRENT_ROLE for sure!
upvoted 0 times
...
Cristy
1 month ago
I don't think CURRENT_CLIENT is the answer, but I can't remember what it actually does in this context.
upvoted 0 times
...
German
1 month ago
I feel like CURRENT_USER might be relevant since it deals with user permissions, but I’m not confident.
upvoted 0 times
...
Elenora
2 months ago
I remember a practice question that mentioned CURRENT_ACCOUNT, but I can't recall if it was specifically about secure views.
upvoted 0 times
...
Xochitl
2 months ago
I think we talked about CURRENT_ROLE in class, but I'm not entirely sure if that's the right choice here.
upvoted 0 times
...
Lea
2 months ago
I’m leaning towards CURRENT_CLIENT, but I don’t have a strong memory of it being used for secure views specifically.
upvoted 0 times
...
Kristeen
2 months ago
I feel like CURRENT_USER could be involved, but it seems more about the individual rather than cross-account access.
upvoted 0 times
...
Juan
2 months ago
I remember something about CURRENT_ACCOUNT being relevant in a similar practice question, but I can't recall the exact context.
upvoted 0 times
...
Leonora
2 months ago
I think it might be CURRENT_ROLE, but I’m not entirely sure if that’s the right one for authorizing users from another account.
upvoted 0 times
...

Save Cancel