Salesforce Updated Sharing-and-Visibility-Architect Exam Questions and Answers by dax

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.

Creating a reusable SOQLQueries class without specifying “With” or “Without Sharing” on the class or specifying “With Sharing” or “Without Sharing” on the methods are two ways to meet the requirements. The sharing mode of the class or method will depend on the context of the calling code, which can be either “With Sharing” or “Without Sharing”. Option B is incorrect because the runAs() method is only available in test methods and does not change the sharing mode. Option D is incorrect because it requires creating two separate classes for different sharing modes, which is not reusable.

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

Storing the value in a text field on a protected custom setting in the package is the best way to support this requirement. Protected custom settings are not visible to subscribers, but they can be accessed by the package code and support representatives. The other options either expose the value to subscribers (B and C) or do not allow support representatives to access it (D).