Salesforce Sharing-and-Visibility-Architect - Salesforce Certified Platform Sharing and Visibility Architect (Plat-Arch-205)

To meet the requirement of sharing opportunities for collaboration and automatically expiring access, the following approach is best:

Apex Sharing (Answer A): Apex sharing allows sales managers to share opportunities with specific users. This is essential for ad-hoc and granular sharing that isn't feasible with criteria-based or owner-based sharing rules.

Scheduled Apex Job (Answer B): Use a scheduled Apex job to remove sharing entries after a specific date, ensuring access expires two weeks after the new fiscal year begins. This provides automation and aligns with the requirement for access expiration.

Option C: Sharing rules cannot handle time-based expiration, making them unsuitable for this use case.

Implicit Sharing:

Salesforce provides implicit sharing for parent-child relationships. For example, access to an Opportunity record implicitly grants access to its parent Account record.

Why Option A is Correct:

Since the finance analyst has access to an Opportunity, she also gains implicit access to the related Account record because of the parent-child relationship.

Why Others Are Incorrect:

Option B: Role Hierarchy does not directly affect this situation unless explicitly configured.

Option C: Contact records are not directly accessible via implicit sharing from Opportunity but can be accessed through their relationship to the Account.

For detailed information, refer to Salesforce Implicit Sharing documentation: https://help.salesforce.com/

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/