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 Certified CRM Analytics and Einstein Discovery Consultant (Analytics-Con-201) Exam - Topic 4 Question 37 Discussion

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?
B) Use a field on the user record like Department/Region, and apply row-level security based on that field.
A) Create two sets of dashboards; one for EMEA, and one for CXOs and VPs while filtering the dashboard on the region.
C) Create two separate datasets; one for EMEA, and one for CXOs and VPs.

Salesforce Certified CRM Analytics and Einstein Discovery Consultant (Analytics-Con-201) Exam - Topic 4 Question 37 Discussion

Actual exam question for Salesforce's Salesforce Certified CRM Analytics and Einstein Discovery Consultant (Analytics-Con-201) exam
Question #: 37
Topic #: 4
[All Salesforce Certified CRM Analytics and Einstein Discovery Consultant (Analytics-Con-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

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:

0/2000 characters
Cory
15 hours ago
Option B seems like the best fit for row-level security.
upvoted 0 times
...
Anika
6 days ago
Nah, I prefer the dashboard approach in Option A.
upvoted 0 times
...
Peggie
11 days ago
I think creating two datasets (Option C) could complicate things.
upvoted 0 times
...
Kristel
16 days ago
Wait, can CXOs really access all data? That seems risky.
upvoted 0 times
...
Gerald
21 days ago
I agree, using user fields is a solid approach!
upvoted 0 times
...
Wilda
26 days ago
Option B seems like the best fit for row-level security.
upvoted 0 times
...
Isaiah
1 month ago
I’m leaning towards option B too, but I’m not clear on how to implement the row-level security effectively for both groups.
upvoted 0 times
...
Huey
1 month ago
I feel like option C could complicate things with maintaining two datasets. It might work, but I’m not confident it’s the best approach for row-level security.
upvoted 0 times
...
Stevie
1 month ago
I remember a practice question where we had to set up different access levels based on roles. Option A seems similar, but I wonder if it’s the most efficient way to handle this.
upvoted 0 times
...
Cecily
3 months ago
I think option B makes sense since it uses a field on the user record, but I'm not entirely sure how that would apply to both scenarios.
upvoted 0 times
...

Save Cancel