Salesforce Exam ANC-201 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?

ACreate two sets of dashboards; one for EMEA, and one for CXOs and VPs while filtering the dashboard on the region.

BUse a field on the user record like Department/Region, and apply row-level security based on that field.

CCreate two separate datasets; one for EMEA, and one for CXOs and VPs.

Show Suggested 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:

Submit Cancel

Mel

1 hours 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

...

Ulysses

19 days 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

1 days 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

3 days 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

20 days 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

27 days 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

Mirta

4 days ago

I agree, it would make it easier to manage access based on department or region.

upvoted 0 times

...

Jani

5 days 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 months 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 months 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 months ago

I think option B) makes sense because we can use the Department/Region field to apply row-level security.

upvoted 0 times

...