Pass Sharing-and-Visibility-Architect Exam Guide

The Internal Default sharing settings for a custom object can be either Public Read/Write or Public Read Only if the External Default sharing setting is set to Public Read Only1. Controlled by Parent and Private are not valid options because they would not allow external users to access the custom object records.

The architect does not need to do anything to ensure field-level security is enforced on a custom Visualforce page using the standard lead controller. This is because the standard controller automatically enforces field-level security based on the user’s profile and permission sets. The user will only see the fields that they have read access to, and will only be able to edit the fields that they have edit access to

The Architect can support this request by creating a Permission Set with read-only access to the Category field and assigning it to the 3 users who need it. This will override the profile permissions and restrict their access to the field.

By turning off the Customer User Visibility feature in its Customer Community, Universal Containers can expect that community functionality related to searching for other external users will be affected. The Customer User Visibility feature allows customer community users to find and collaborate with other customer community users who belong to different accounts. If this feature is turned off, customer community users can only see other users who belong to the same account as them. Turning off this feature will not affect creating new customer community users, updating their user profile, or searching for internal users.