Salesforce-Platform-Sharing-and-Visibility-Architect Practice Test
Salesforce Spring 25 Release 77 Questions
Universal Containers (UC) has affiliates who sell containers in countries where UC does
not have a local office. UC uses a Partner Community to manage thesales cycle in those
countries. One of its affiliates has grown substantially and restructured its internal sales
team with the following structure: Sales VP —> Directorof Sales —> Sales Manager —>Sales Reps. Sales Reps should not see each others’opportunities, and visibility of deals
should open up within a Sales Rep's hierarchy.
What is the main problem an architect should address in this situation?
A. The Channel Manager role cannot be shared with Partner Community.
B. Partner User roles arelimited to three Ievels.
C. Partner Community does not support Role Hierarchy.
B. Partner User roles arelimited to three Ievels.
Explanation:
Partner Community licenses restrict partner user role hierarchies to a maximum of three levels beneath the Channel Manager role. UC’s affiliate has four levels (VP → Director → Manager → Rep), but only three can be represented. The architect must address this structural mismatch, either by consolidating levels (e.g., combining Director and Manager) or by using Sharing Sets/Security Groups for finer control.
→ It’s not that the Channel Manager role can’t be shared (A), nor that Partner Communities lack hierarchy entirely (C).
→ The core limitation is the three-level cap, which directly prevents modeling the full affiliate structure in the partner role hierarchy.