Had something like this in a mock, and I’m pretty sure it’s C since you want strict data separation by geography. Setting Account OWD to Private plus sharing rules matches the branch-based model. Role hierarchy gives too much visibility above branch level, so I wouldn’t pick A. Agree?
Q: 14
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?
Options
Discussion
C . Role hierarchy (A) gives too much access if managers are above branch level, that's the classic trap here.
C
C for me. Org-wide defaults plus sharing rules limit visibility to just the right group, so only branch staff/managers see their own customers. Pretty sure that's the intended Salesforce pattern here, unless I'm missing something obvious.
I always think Role Hierarchy matters for manager visibility, so I'd pick A. Sharing rules alone might not cover manager escalation.
A . I think role hierarchy plus sharing rules works since managers inherit access to their staff, and you can make rules by branch. Account Team feels less relevant here, but maybe I missed something.
C tbh. Org-wide defaults and sharing rules are made for this kind of location-based access. Role hierarchy (A) often trips people up here since it can leak beyond just the one branch if the org chart’s more complex. Not 100% but C fits best.
C tbh. The trap is A because role hierarchy would give branch managers access to more than just their location, especially if roles are set up above branch level. Sharing rules plus OWD Private matches the requirement best.
C I think it's C from what I remember, but not 100% sure. Can someone confirm if sharing rules alone cover all cases?
Be respectful. No spam.
Question 14 of 15