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
Mail Us support@pass4success.com
Location US
Mob_nav_barsMENU

Salesforce ANC-201 Exam - Topic 2 Question 12 Discussion

Actual exam question for Salesforce's ANC-201 exam
Question #: 12
Topic #: 2
[All ANC-201 Questions]

Cloud Kicks has informed CRM Analytics developers that they have two scenarios with restricted row-level security.

The parameters being:

1. Non-CXOs and VPs working in EMEA can have access to EMEA records only.

2. CXOs and VPs should have access to all data irrespective of the region (APAC, EMEA, etc.).

Which sharing method works for this scenario?

Show Suggested Answer Hide Answer
Suggested Answer: B

Predicate is a name for a filter condition that defines row-level access to records in a dataset Example: 'rowLevelSecurityFilter':''AccountOwner' == '$User.Name''

by Benedict at Feb 07, 2023, 12:19 PM

Limited Time Offer

25%

Off

Get Premium ANC-201 Questions as Interactive Web-Based Practice Test or PDF

Contribute your Thoughts:

0/2000 characters
Submit Cancel
Zoila
5 months ago
Two datasets sounds like extra work, C might complicate things.
upvoted 0 times
...
Mica
6 months ago
I’m not sure about B, wouldn’t A work too?
upvoted 0 times
...
Olga
6 months ago
Wait, can CXOs really access all data? That seems risky.
upvoted 0 times
...
Bette
6 months ago
Totally agree, B is the way to go!
upvoted 0 times
...
Lindsey
6 months ago
I think option B makes the most sense for row-level security.
upvoted 0 times
...
Angella
6 months ago
I’m leaning towards option B, but I recall there being some complications with user fields in previous examples we went over.
upvoted 0 times
...
Dean
6 months ago
This question feels similar to one we practiced where we had to set permissions based on roles. I wonder if creating separate datasets might be more efficient.
upvoted 0 times
...
Rolande
6 months ago
I think using a field on the user record could work, but I’m a bit unclear on how that would be implemented in practice.
upvoted 0 times
...
Lauran
7 months ago
I remember discussing row-level security in class, but I'm not sure if creating two dashboards is the best approach.
upvoted 0 times
...
Kimberlie
7 months ago
Enabling BGP on the gateway of Vnet1 seems like a reasonable solution, but I'm not 100% sure if that's the right approach here.
upvoted 0 times
...
Tawna
7 months ago
Hmm, I'm a bit unsure about this one. Creating a separate Lightning App or updating the Lead Assignment Rules don't seem directly relevant to the problem. I'm leaning towards option B, but I'll need to think it through a bit more.
upvoted 0 times
...
Joye
7 months ago
This seems like a straightforward question about the capabilities a modeling tool should have for traceability in requirements engineering. I'll need to carefully consider the options and select the three most relevant ones.
upvoted 0 times
...
Mel
12 months ago
Option B definitely sounds like the most efficient solution. I mean, who wants to deal with the headache of constantly updating multiple dashboards and datasets?
upvoted 0 times
Arlyne
11 months ago
Yeah, it would be a hassle to manage multiple dashboards and datasets. Option B is definitely the way to go.
upvoted 0 times
...
Nicholle
11 months ago
Agreed, using a field on the user record for row-level security is much simpler.
upvoted 0 times
...
Myrtie
11 months ago
Option B definitely sounds like the most efficient solution.
upvoted 0 times
...
...
Ulysses
1 year ago
Haha, I can already see the IT team cringing at the thought of managing two separate datasets. Talk about a maintenance nightmare!
upvoted 0 times
Bronwyn
12 months ago
B) Use a field on the user record like Department/Region, and apply row-level security based on that field.
upvoted 0 times
...
Elvera
12 months ago
A) Create two sets of dashboards; one for EMEA, and one for CXOs and VPs while filtering the dashboard on the region.
upvoted 0 times
...
...
Christiane
1 year ago
I'm not sure creating separate dashboards or datasets is the right approach here. It feels like it would be a lot of maintenance and could lead to inconsistencies.
upvoted 0 times
...
Alyce
1 year ago
Option B seems like the way to go. Using a field on the user record to apply row-level security is a more flexible and scalable solution.
upvoted 0 times
Francoise
11 months ago
Yeah, having separate dashboards could get confusing for users.
upvoted 0 times
...
Glennis
11 months ago
Creating two separate datasets might be more work in the long run.
upvoted 0 times
...
Mirta
12 months ago
I agree, it would make it easier to manage access based on department or region.
upvoted 0 times
...
Jani
12 months ago
Option B seems like the way to go. Using a field on the user record to apply row-level security is a more flexible and scalable solution.
upvoted 0 times
...
...
Miesha
1 year ago
I'm not sure about option A) though. Creating separate dashboards might be confusing for users. I think option B) is the way to go.
upvoted 0 times
...
Malika
1 year ago
I agree with Tawny. Option B) seems like the most efficient way to handle the different access levels based on user roles.
upvoted 0 times
...
Tawny
1 year ago
I think option B) makes sense because we can use the Department/Region field to apply row-level security.
upvoted 0 times
...

Save Cancel