* Account Data Skew: Data skew occurs when a single user owns a disproportionately large number of records (e.g., more than 10,000). This can cause performance degradation due to sharing recalculations and record locking during updates.
* Why Option A is Correct:
* With each donation rep owning over 50,000 records, performance issues arise due to ownership- based sharing recalculations and potential lock contention.
* Addressing this requires redistributing ownership or using features like queues or groups to mitigate skew.
* Why Others Are Incorrect:
* Option B: Access configuration is not directly related to performance degradation in this context.
* Option C: Sharing recalculation is a symptom, not the root cause.
For more information, see Salesforce Sharing and Data Skew Best Practices: https://help.salesforce.com/

* Grant Access Using Hierarchies:
* By default, Salesforce allows access to records up the Role Hierarchy for objects where "Grant Access Using Hierarchies" is enabled. If this setting is disabled, users in higher roles cannot see records owned by users in lower roles.
* Why Option C is Correct:
* For the custom Shipment object, the "Grant Access Using Hierarchies" setting needs to be enabled to allow sales managers to access shipment records owned by their team members.
* Why Others Are Incorrect:
* Option A: Implicit sharing cannot be disabled by an admin; it is always active for certain relationships.
* Option B: Ownership-based sharing rules are unnecessary if the Role Hierarchy is functioning correctly.
For more details, see Salesforce documentation on Object Sharing Settings: https://help.salesforce.com/

In Salesforce, users must have object-level access (Read permission) to see records shared through sharing rules or any other mechanism. If some users in the public group lack the Read permission for the Account object, they will not be able to see the accounts, even though they are part of the public group with a sharing rule granting access.
* Option A (Correct): Lack of object-level permissions for the Account object explains why some users cannot view the shared accounts.
* Option B: Page layouts only affect how records are displayed, not record visibility.
* Option C: Role Hierarchy does not impact this issue, as it is related to public group sharing.
References:
* Object Permissions Overview

* Dynamic Forms: Salesforce Dynamic Forms enable administrators to create field sections that adapt based on device form factors (mobile, desktop, or tablet). This helps align data properly on different devices without requiring custom code.
* Why Option C is Correct:
* Dynamic Forms allow flexibility to display relevant fields and layouts for different devices without creating separate overrides or custom components.
* It adheres to the company's objective of improving productivity by offering a user-friendly interface across form factors.
* Why Others Are Incorrect:
* Option A: Custom LWC overrides add unnecessary complexity and require more maintenance.
* Option B: Visualforce is outdated for modern Salesforce solutions and not recommended for such use cases.
For more details, refer to the Salesforce documentation on Dynamic Forms: https://help.salesforce.com/

The organization-wide default (OWD) for Pricebook should be set to Use to allow sales agents to view pricebooks and their products, as well as to select a pricebook when creating Opportunities. The Use access enables users to add products from the pricebook to their opportunities while preventing unauthorized changes to the pricebook or its entries. Setting the OWD to Public Read-Only or View could provide unnecessary access or restrict essential functionality, such as associating products with opportunities. (developer.salesforce.
com)