Architect Exams Sharing-and-Visibility-Architect Salesforce Study Notes

Page: 4 / 5

Question 16

Universal Containers (UC) wants to reduce the amount of redundant leads entered into the system. UC also wants to ensure that leads are only edited/reassigned by the lead owner.

Which organization-wide default (OWD) approach should be recommended to help UC implement these requirements?

Options:

Implement a Public Read Only/Transfer OWD on Lead.

Implement 2 Public Read-Only OWD on Lead.

Implement a Private OWD on Lead.

Question 17

Universal Containers (UC) has a partner community for its 200 distributors.

UC customer accounts are assigned an individual distributor. The organization-wide default setting for the custom Delivery object is Private.

How should an architect advise UC to grant all users at a distributor access to delivery records for all customers assigned to a particular distributor?

Options:

Create a criteria based sharing rule that shares delivery records matching a distributor to theDistributor role in the Role Hierarchy.

Create 2 criteria-based sharing rule that shares delivery records matching the Distributor to users of aPublic Group created for the distributor.

Create a Sharing Set for the Distributor profile to grant access to the Delivery object.

Question 18

Sales reps at Universal Containers sometimes create large files as a part of the sales process that are too large to share over email. They would like users to be able to share files with customers, but the CISO hasrequested that any file linksshared must be password-protected.

How can this be accomplished?

Options:

Utilize an AppExchange product for delivering password protected files to customers

Create a content delivery; during creation, the user should select the option to require 3 password to access content.

Set up an Experience Cloud site for customers to access files and share the file with customers via Chatter. Customers can then log in ta the site to access the content.

Question 19

A banking company wants their customers Date of Birth Field searchable by Banking Reps, but only editable by Customer Support Reps.

Which approach is recommended to meet this requirement?

Options:

Create 2 Validation rule in the Data of Birth field so the rule returns true only when user.profilename matches Customer Support Rep.

Set the Field Level Security for the Date of Birth field to be Visible to Customer Support Rep Profile, and set the Date of Birth field Visible and Readonly to Banking Rep profile.

Add Date of Birth field to the Search layout of the Contact Object. Modify the Page layout assigned to Customer Support Rep and add Date of Birth field as Required.