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

Salesforce Exam ANC-301 Topic 4 Question 56 Discussion

Actual exam question for Salesforce's ANC-301 exam
Question #: 56
Topic #: 4
[All ANC-301 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

For Cloud Kicks' requirements regarding access to data based on roles and geographic regions, the most efficient and scalable approach is to implement row-level security using fields on the user record, like Department or Region. Here's the rationale for choosing this approach:

Scalability and Maintenance: By applying security rules based on user record fields, Cloud Kicks can manage access dynamically without needing to maintain multiple dashboards or datasets. This reduces administrative overhead and simplifies updates as roles or regional structures change.

Flexibility: Using a field on the user record to control access allows for easy expansion or modification of security policies as new regions or roles are added.

Simplicity: This method ensures a clear and straightforward security model that can be easily audited and understood by administrators and compliance teams.


Contribute your Thoughts:

Sherita
1 days ago
Hmm, I'm not sure. Creating two separate datasets feels like overkill, and filtering the dashboard on the region might get messy. I'd go with B as well.
upvoted 0 times
...
Oliva
2 days ago
I think option B) makes sense, using a field on the user record for row-level security.
upvoted 0 times
...
Gussie
20 days ago
I think the answer is B. Using a field on the user record like Department/Region and applying row-level security based on that field seems like the most straightforward solution for this scenario.
upvoted 0 times
Jesusita
11 hours ago
B) Use a field on the user record like Department/Region, and apply row-level security based on that field.
upvoted 0 times
...
...

Save Cancel