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 Sharing-and-Visibility-Architect Topic 4 Question 44 Discussion

Actual exam question for Salesforce's Salesforce Certified Sharing and Visibility Architect exam
Question #: 44
Topic #: 4
[All Salesforce Certified Sharing and Visibility Architect Questions]

Universal Containers (UC) requested that branch managers and UC branch staff should only see customers and related information in their geographic location.

Which options should be used together to achieve the requirements?

Show Suggested Answer Hide Answer
Suggested Answer: B

Contribute your Thoughts:

Ettie
3 days ago
I agree with Holley, creating Account Team and configuring organization-wide defaults makes sense.
upvoted 0 times
...
Denna
13 days ago
This is a classic case of 'when in doubt, add more layers of complexity.' I'd go with Option B - keep it simple, folks!
upvoted 0 times
...
Tayna
13 days ago
I'm leaning towards Option C. The Role Hierarchy and sharing rules combo seems like the most comprehensive solution.
upvoted 0 times
Marva
2 days ago
I think combining Role Hierarchy with sharing rules is the way to go for this requirement.
upvoted 0 times
...
Yan
7 days ago
Option C sounds like a good choice. Role Hierarchy can help with visibility.
upvoted 0 times
...
...
Holley
14 days ago
I think option A should be used.
upvoted 0 times
...
Madalyn
18 days ago
Option B looks like the way to go. Configuring organization-wide defaults and sharing rules should do the trick.
upvoted 0 times
Kimbery
1 days ago
Creating the Account Team and adding branch manager team members could also be useful in ensuring the right people have access to the right information.
upvoted 0 times
...
Nikita
5 days ago
I agree, setting up sharing rules will definitely help restrict access to customers based on geographic location.
upvoted 0 times
...
Julieta
8 days ago
Option B looks like the way to go. Configuring organization-wide defaults and sharing rules should do the trick.
upvoted 0 times
...
...

Save Cancel
az-700  pass4success  az-104  200-301  200-201  cissp  350-401  350-201  350-501  350-601  350-801  350-901  az-720  az-305  pl-300  

Warning: Cannot modify header information - headers already sent by (output started at /pass.php:70) in /pass.php on line 77