Salesforce Certified Sharing and Visibility Architect (SP23) Sharing-and-Visibility-Architect Exam Questions with Experts Answers Updated Recently

Disabling “Grant Access Using Hierarchies” and disabling the “View All” permission on all other profiles are two options that would ensure access only to the record owner and the administrator for a custom object with private sharing settings. Disabling “Grant Access Using Hierarchies” would prevent users above the record owner in the role hierarchy from accessing the record. Disabling the “View All” permission on all other profiles would prevent users with other profiles from accessing all records of that object. Disabling the “Create” permission on all other profiles would prevent users with other profiles from creating new records of that object, but not from accessing existing ones. Disabling the “Read” permission on all other profiles would prevent users with other profiles from accessing any record of that object, but also prevent them from creating or modifying records.

To give access to a report folder to someone else in the organization, the user needs to have the “Manage Reports in Public Folders” profile permission and the “Manager” report folder permission. The “Viewer” and “Editor” report folder permissions only allow the user to view or edit the reports in the folder, but not to share the folder with others

 The development team missed using the with Sharing keyword in Apex classes to enforce sharing rules evaluation, and the isAccessible() method in Apex classes to check field accessibility. The with Sharing keyword ensures that the Apex code respects the sharing rules defined for the current user, while the isAccessible() method checks if the user has read access to a specific field1. The run as method in test class is used to test whether a user can perform certain actions, not to enforce permissions2. The isSharable keyword in Apex classes does not exist.