When the Organization-Wide Default (OWD) for an object is set to Private, users can only see records they own or those shared with them. While the Role Hierarchy automatically grants
"upward" visibility (managers see what subordinates own), it does not naturally allow for "lateral" visibility or visibility across different branches of the hierarchy. To solve this, a Platform Administrator should use Sharing Rules. Sharing Rules allow the admin to create exceptions to the Private OWD based on record ownership or specific criteria. For example, the admin can create an "Owner-based Sharing Rule" that shares all records owned by the "East Coast Sales" role with the VP of Sales (or a Public Group the VP belongs to). This provides a scalable way to grant the necessary visibility for reporting without making the data public to the entire company.
Sharing Rules are a core security feature that ensures the right people have access to the right data while maintaining the principle of least privilege.

In Salesforce, there are different types of sharing: Managed Sharing (Role Hierarchy, Sharing Rules) and Manual Sharing. A critical behavior of the platform is that when a user is deactivated, all their Manual Shares (records shared with them by other users using the "Share" button) are automatically and permanently deleted from the system. Even if the user record is reactivated later, those manual shares do not return. Because the organization uses a "Private" model and does not use criteria-based sharing rules, the user's previous access likely relied on manual sharing or their previous position in the hierarchy. While activating the record and adding them back to teams provides new access, the historical "one-off" shares are gone. Options A and B are unlikely to be the cause of a total loss of visibility. Option D is incorrect because permission sets control what a user can do, not which specific records they can see in a private sharing model.

In Salesforce, validation rules use formulas to verify if the data entered by a user meets specific criteria before saving the record. To check the value of a picklist field like LeadSource, the ISPICKVAL() function must be used, as picklist fields do not support standard text operators like
"=" in validation formulas. The requirement is to block the save if LeadSource is "Other" but the Source__c text field is empty. The ISBLANK() function effectively checks if a text field contains no data. Therefore, the correct logic uses AND() to trigger the error message only when both conditions are met: the picklist is set to "Other" AND the text field is blank. Option A is incorrect because it treats a picklist like a text field. Option B and D use NOT() logic, which would trigger errors in the wrong scenarios.

There are two primary ways to display different picklist values to different groups of users. The first, and most common, is using Record Types (Option C). A single picklist field can have its available values filtered at the Record Type level. By creating a "Sales" record type and a
"Marketing" record type, the admin can select which values are visible for each. These record types are then assigned to the respective users' profiles. The second method (Option D) involves using different Page Layouts and two separate picklist fields. In this scenario, the admin creates two distinct fields (e.g., "Sales Category" and "Marketing Category") and places only the relevant field on the page layout assigned to that specific team. This is less common but effective if the data needs to be stored in entirely different buckets. Option B is incorrect because profiles themselves do not filter picklist values; they only control which record types a user can access.