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-R01 Exam - Topic 2 Question 23 Discussion

Actual exam question for Snowflake's ARA-R01 exam
Question #: 23
Topic #: 2
[All ARA-R01 Questions]

Which of the following are characteristics of how row access policies can be applied to external tables? (Choose three.)

Show Suggested Answer Hide Answer
Suggested Answer: C

Enabling the search optimization service on the table can improve the performance of queries that have selective filtering criteria, which seems to be the case here. This service optimizes the execution of queries by creating a persistent data structure called a search access path, which allows some micro-partitions to be skipped during the scanning process. This can significantly speed up query performance without increasing compute costs1.

Reference

* Snowflake Documentation on Search Optimization Service1.


Contribute your Thoughts:

0/2000 characters
Angelo
3 months ago
I think cloning a database with the policy is a bit misleading.
upvoted 0 times
...
Floyd
3 months ago
External tables as mapping tables? That's new to me!
upvoted 0 times
...
Erinn
3 months ago
Wait, you can't add a policy to a virtual column? That's surprising!
upvoted 0 times
...
Marvel
4 months ago
Totally agree, that's a key feature!
upvoted 0 times
...
Deja
4 months ago
A row access policy can be applied to the VALUE column of an existing external table.
upvoted 0 times
...
Ashley
4 months ago
I vaguely remember something about cloning databases and how row access policies are handled, but I can't remember if they get cloned along with the external table.
upvoted 0 times
...
Barrett
4 months ago
I’m pretty certain that a row access policy cannot be added to a virtual column of an external table, but I might be mixing it up with something else.
upvoted 0 times
...
Yuki
4 months ago
I feel like we practiced a question about whether external tables can be used in row access policies, and I think they can be, but I can't recall the specifics.
upvoted 0 times
...
Latonia
5 months ago
I think I remember that a row access policy can be applied to the VALUE column of an existing external table, but I'm not completely sure.
upvoted 0 times
...
Jerrod
5 months ago
I feel pretty good about this one. I remember that row access policies can be applied to external tables, and the table can even be used as a mapping table in the policy. But I don't think the policy can be directly added to a virtual column.
upvoted 0 times
...
Alesia
5 months ago
Okay, let me think this through. I know external tables are supported, and the policy can be applied to the table itself. But I'm not sure about things like virtual columns or using the external table as a mapping table. I'll have to review those details.
upvoted 0 times
...
Winfred
5 months ago
Hmm, I'm a bit unsure about the details here. I know row access policies can be used with external tables, but I'm not sure about the specifics like whether the policy can be applied to the VALUE column or if the policy and table get cloned together.
upvoted 0 times
...
Niesha
5 months ago
I'm pretty confident about this one. I think the key characteristics are that row access policies can be applied to external tables, but not directly to virtual columns, and external tables can be used as mapping tables in the policies.
upvoted 0 times
...
Roslyn
10 months ago
This is all great, but I'm just wondering - can we use row access policies to control who sees the external table's secret ingredient recipe? Asking for a friend, of course.
upvoted 0 times
Alita
9 months ago
F) A row access policy cannot be applied to a view created on top of an external table.
upvoted 0 times
...
Wendell
9 months ago
B) A row access policy can be applied to the VALUE column of an existing external table.
upvoted 0 times
...
Mari
9 months ago
A) An external table can be created with a row access policy, and the policy can be applied to the VALUE column.
upvoted 0 times
...
...
Maryanne
10 months ago
B is a bit surprising. I thought we could only create the policy when the external table is made, not apply it later. Interesting twist!
upvoted 0 times
Darnell
9 months ago
Lenna: That makes sense. It's good to have options when setting up security measures.
upvoted 0 times
...
Erick
9 months ago
User 3: I think it gives more flexibility in managing access to external tables.
upvoted 0 times
...
Lenna
9 months ago
User 2: Yes, it's definitely an interesting twist in how row access policies work.
upvoted 0 times
...
Shenika
10 months ago
User 1: I agree, B is surprising. I didn't know we could apply the policy later.
upvoted 0 times
...
...
Jovita
10 months ago
C and F make sense. Can't apply a policy to a virtual column or a view on an external table. Gotta keep those policies on the base table.
upvoted 0 times
Osvaldo
10 months ago
User3
upvoted 0 times
...
Edison
10 months ago
User2
upvoted 0 times
...
...
Daisy
11 months ago
A, D, and E - Looks like we can create an external table with a row access policy, use it as a mapping table, and even clone the policy along with the table. Handy stuff!
upvoted 0 times
...
Chanel
11 months ago
I'm not sure about E. Does cloning a database really clone both the row access policy and the external table?
upvoted 0 times
...
Shala
11 months ago
I agree with Paris. A, B, and D make sense because external tables can have row access policies applied to them.
upvoted 0 times
...
Paris
11 months ago
I think A, B, and D are the characteristics of how row access policies can be applied to external tables.
upvoted 0 times
...

Save Cancel