Architect Exams Changed Sharing-and-Visibility-Architect Questions

The two options that the Architect should consider when designing the solution are B and D. Option B ensures that the national accounts are only visible to the sales directors and above in the role hierarchy, as they inherit access from the owner. Option D ensures that the sales reps who are added to the opportunity team for a national account can access the account data, as they are granted access through implicit sharing

Apex runs in system mode, which means it does not respect the current user’s permissions and sharing settings. Therefore, the development team needs to enforce record visibility by using the WITH SECURITY_ENFORCED clause or the Security.stripInaccessible method

The user groups that can add team members on the Account are the current Account Owner and someone above the Account Owner in the Role Hierarchy with read access3. The user specified as the Manager on the Owner’s User record and any Account Team Member with read access on the Account cannot add team members on the Account.

Disabling Grant Access Using Hierarchies for the object and creating a sharing rule to enable sharing to the Director of Support are the steps to ensure proper sharing in this role hierarchy structure. This way, the Team Leads will not have access to the Reimbursement records of their subordinates, but the Director of Support will have access to all Reimbursement records. Option A is incorrect, as setting the View All permission on the profile will grant access to all users with that profile, not just the Director of Support. Option B is incorrect, as changing the owner of the Reimbursement record will remove the access from the original submitter. Option D is incorrect, as by default, Grant Access Using Hierarchies is enabled for custom objects, which means that Team Leads will have access to their subordinates’ Reimbursement records.