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 Exam ADA-C01 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:

Karma
5 days 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
...
Elden
11 days 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
...
Matt
16 days 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
...
Marva
21 days ago
You might be right, I'll reconsider my answer.
upvoted 0 times
...
Tamra
23 days ago
I disagree, I believe it's A) CURRENT_ROLE because it grants access based on roles.
upvoted 0 times
...
Marva
24 days ago
I think the answer is B) CURRENT ACCOUNT.
upvoted 0 times
...

Save Cancel
az-700  pass4success  az-104  200-301  200-201  cissp  350-401  350-201  350-501  350-601  350-801  350-901  az-720  az-305  pl-300  

Warning: Cannot modify header information - headers already sent by (output started at /pass.php:70) in /pass.php on line 77