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 ADA-C01 Exam - Topic 5 Question 22 Discussion

Actual exam question for Snowflake's ADA-C01 exam
Question #: 22
Topic #: 5
[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: D

The SIMULATED_DATA_SHARING_CONSUMER session parameter allows a data provider to test the integrity of secure views based on the account that is accessing that view2. By setting this parameter to the name of the consumer account, the data provider can query the secure view and see the results that a user in the consumer account will see2. This helps to ensure that sensitive data in a shared database is not exposed to unauthorized users1. The other options are not valid session parameters in Snowflake3


Contribute your Thoughts:

0/2000 characters
Vincent
3 months ago
Agreed, CURRENT_ROLE is the right choice!
upvoted 0 times
...
Ernest
3 months ago
Wait, is it really CURRENT_CLIENT? That sounds weird.
upvoted 0 times
...
Rickie
3 months ago
CURRENT_USER seems off to me.
upvoted 0 times
...
Dyan
4 months ago
Definitely not CURRENT_ACCOUNT, that's not it.
upvoted 0 times
...
Alishia
4 months ago
I think it's CURRENT_ROLE for sure.
upvoted 0 times
...
Chan
4 months ago
I’m leaning towards CURRENT_CLIENT, but I can't recall if that’s actually used for row access in secure views.
upvoted 0 times
...
Deandrea
4 months ago
I have a vague memory that CURRENT_ACCOUNT could be relevant, but it seems more about the account itself rather than user authorization.
upvoted 0 times
...
Gwen
4 months ago
I remember practicing a similar question, and I feel like CURRENT_USER was mentioned a lot, but I don't know if it applies here.
upvoted 0 times
...
Raymon
5 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
...
Anabel
5 months ago
I'm a little confused by the wording of this question. Is it asking about the function to authorize users, or the function to actually grant them access? I want to make sure I don't misinterpret what they're looking for.
upvoted 0 times
...
Rosalyn
5 months ago
Okay, I've got this. The function we need to authorize users from another account is CURRENT_USER. That's the one that will let us control access to the base table rows.
upvoted 0 times
...
Jose
5 months ago
Hmm, I'm a bit unsure about this one. Secure views and cross-account access seem tricky. I'll need to review my Snowflake security notes to make sure I understand the right function to use.
upvoted 0 times
...
Ocie
5 months ago
This looks like a straightforward Snowflake security question. I think the key is to focus on the function that authorizes users from another account to access the base table.
upvoted 0 times
...
Melissia
5 months ago
I think the key here is to configure something that will prevent the Start/Stop VMs during off-hours feature from stopping certain VMs. Based on the options, it seems like an Azure Automation account variable or an action group would be the way to go.
upvoted 0 times
...
Catherin
10 months ago
C) CURRENT_USER all the way! I mean, who else would we use to authorize users, right? Unless they're trying to trick us with a red herring. *chuckles*
upvoted 0 times
Blondell
9 months ago
B) CURRENT_ACCOUNT is not the function needed for authorizing users from another account, it is CURRENT_ROLE.
upvoted 0 times
...
Telma
9 months ago
C) CURRENT_USER is not the correct function in this case, it is CURRENT_ROLE that is needed for authorization.
upvoted 0 times
...
Alishia
9 months ago
A) CURRENT_ROLE is actually the correct function to authorize users from another account to access rows in a base table.
upvoted 0 times
...
...
Karma
10 months ago
D) CURRENT_CLIENT? Really? That doesn't seem quite right for this scenario. I'm pretty confident the answer is either A or C.
upvoted 0 times
Kelvin
8 months ago
Let's go with A) CURRENT_ROLE then.
upvoted 0 times
...
Kristine
9 months ago
Yeah, CURRENT_USER is also a possibility.
upvoted 0 times
...
Oneida
9 months ago
I agree, CURRENT_ROLE makes more sense in this context.
upvoted 0 times
...
Harley
10 months ago
I think the answer is A) CURRENT_ROLE.
upvoted 0 times
...
...
Elden
10 months ago
Hmm, I'm not sure about that. I was thinking maybe B) CURRENT_ACCOUNT would be the right function to use. But I'll have to double-check the documentation.
upvoted 0 times
Alise
10 months ago
I believe it's A) CURRENT_ROLE that is needed for authorizing users from another account.
upvoted 0 times
...
Julian
10 months ago
I think it might be C) CURRENT_USER instead.
upvoted 0 times
...
...
Matt
11 months ago
I think the answer is C) CURRENT_USER. That makes sense since we need to authorize users from another account to access the base table.
upvoted 0 times
Juliann
9 months ago
I agree, it should be C) CURRENT_USER.
upvoted 0 times
...
Jerlene
9 months ago
I'm pretty sure it's C) CURRENT_USER.
upvoted 0 times
...
Steffanie
9 months ago
I think it might be A) CURRENT_ROLE actually.
upvoted 0 times
...
Shalon
10 months ago
I believe the answer is C) CURRENT_USER.
upvoted 0 times
...
...
Marva
11 months ago
You might be right, I'll reconsider my answer.
upvoted 0 times
...
Tamra
11 months ago
I disagree, I believe it's A) CURRENT_ROLE because it grants access based on roles.
upvoted 0 times
...
Marva
11 months ago
I think the answer is B) CURRENT ACCOUNT.
upvoted 0 times
...

Save Cancel