* Field Level Security (FLS):
* FLS controls whether a field is visible or editable for a specific profile.
* Search layouts define which fields are searchable, independent of edit permissions.
* Why Option B is Correct:
* Setting FLS for the Banking Rep profile ensures the field is visible but read-only, while granting edit access to the Customer Support Rep profile aligns with the requirement.
* Why Others Are Incorrect:
* Option A: Validation rules are not a scalable solution for controlling field access.
* Option C: Search layout settings do not control field-level visibility or edit permissions.
For details, refer to Salesforce FLS documentation: https://help.salesforce.com/

To allow presenters to edit details on a private custom object (Presentation) based on their relationship through a junction object, Apex Managed Sharing is the best solution:
* Option A: Permission sets provide global permissions, not record-specific access based on a junction object.
* Option B: Adding users to a Sales Team applies to opportunities, not custom objects like Presentation.
* Option C (Correct): Apex Managed Sharing allows the creation of precise, record-specific sharing rules that dynamically grant access based on junction object relationships. This approach ensures presenters can edit only their related Presentation records.
References:
* Apex Managed Sharing for Custom Sharing Logic

* View All Permission: Assigning the "View All" permission for the Opportunity object allows users to see all records of that object, regardless of sharing rules or ownership. This permission meets the need for key sales reporting team members to view Opportunity data without editing rights.
* Why Option C is Correct:
* A permission set is the preferred method for granting additional permissions to specific users without altering their profile.
* "View All" is more restrictive than "View All Data," providing access only to the Opportunity object and respecting the principle of minimal access.
* Why Others Are Incorrect:
* Option A: "View All Data" grants access to all objects and violates UC's privacy principles.
* Option B: While a permission set is correct, granting "View All Data" is overly permissive and unnecessary.
For detailed reference, see Salesforce permissions documentation: https://help.salesforce.com/

* Site User Visibility Setting:
* When "Site User Visibility" is turned off, external users cannot search for or view other external users within the community.
* This setting helps maintain privacy and control user visibility.
* Why Option B is Correct:
* Disabling Site User Visibility directly impacts the ability to search for other external users.
* Why Others Are Incorrect:
* Option A: Updating their user profile is unrelated to this setting.
* Option C: Internal user visibility is not affected by this setting.
For further guidance, see Salesforce Community Sharing Settings documentation: https://help.salesforce.com/

When piloting a new application for a subset of users, the best practice is to clone the existing profile and adjust settings specific to the pilot users. This ensures a clean separation of permissions, while maintaining the ability to grant or revoke access as needed.
* Why Cloning and Adjusting Profiles is Optimal:
* Granular Control: Cloning the Sales Rep profile allows administrators to tailor the access permissions without disrupting the existing permissions for other users.
* Separation of Access: Profiles define baseline access settings, so by creating a new profile, you can hide legacy functionality while enabling access to the pilot application for specific users.
* Simplicity for Administration: Profiles provide a structured way to enforce changes for a defined group of users without introducing overlap or unintended access conflicts.
* Why the Other Options Are Less Suitable:
* Option B (Revoke access in Sales Rep profile and use permission sets):
* Revoking legacy access in the Sales Rep profile impacts all users assigned to that profile, not just the pilot users. This is not suitable when only a subset of users requires changes.
* Permission sets are additive, so they cannot effectively "hide" legacy functionality.
* Option C (Use a permission set for both access and hiding):
* Permission sets are designed to extend access, not revoke or hide functionality.
* Hiding legacy functionality through profiles is more reliable since profiles control baseline access.
Study Guide References:
* Salesforce Sharing and Visibility Architect Study Guide 2023 by SaaS Guru: Emphasizes the use of profile cloning for controlled and scalable access management during pilots or testing.
* Sharing and Visibility Designer Study Guide by Salesforce Chris: Highlights that profiles are ideal for defining baseline permissions, while permission sets are supplementary for additive access.
Relevant Salesforce Documentation:
* https://help.salesforce.com/s/articleView?id=sf.admin_profiles.htm
* https://help.salesforce.com/s/articleView?id=sf.perm_sets_overview.htm