Salesforce Sharing and Visibility Certification Practice Exam

How should an Architect troubleshoot unexpected access to Accounts after a role hierarchy change?

1. Use the Field Accessibility Viewer while logged in as the System Administrator.

2. Use the Sharing button while logged in as a Staff member.

3. Inspect the user record of a Staff member for profile and role membership.

4. Check the Roles and Sharing model settings as an Administrator.

The correct answer is: Inspect the user record of a Staff member for profile and role membership.

To thoroughly troubleshoot unexpected access to Accounts after a role hierarchy change, it's essential to inspect the user record of a Staff member for profile and role membership. This approach allows you to directly assess the affected user's access settings and determine how the role change has influenced their ability to view or edit Accounts. By examining the user’s profile, you can identify which permissions are granted or restricted based on their current role and profile. Roles in Salesforce represent a hierarchy that dictates record-level access, so understanding where a user's role sits in relation to other roles can clarify the impact of the recent change. Changes in hierarchy can affect visibility, and its examination becomes crucial in identifying discrepancies between expected and actual access levels. The other methods, while useful in general context, either do not provide the specific insights needed for troubleshooting in this scenario or do not address the root cause directly. For instance, checking the overall sharing model settings and using sharing buttons focus more on broader system settings or functionality rather than on the individual user’s context. Thus, option C provides a targeted approach to understanding and correcting unexpected access issues post-role adjustment.