Universal Containers (UC) has a team that analyzes customer orders looking for fraud. This team needs access to Invoice records (custom object, Private organization-wide default). UC has complex rules to control users’ access. The architect recommended using Apex managed sharing to meet these requirements. Which recommendation should a developer consider when implementing the changes?

When implementing a complex, custom sharing solution like Apex managed sharing, testing is critical to ensure the logic correctly grants or revokes access for different users. The runAs(user) system method in an Apex test class allows the test to execute from the perspective of a specific user. This enables developers to create test scenarios that verify whether a user with a certain profile or role can access a record after the sharing logic has been executed, confirming the implementation meets the requirements. This is a fundamental best practice for validating record visibility rules.

A. Use "Without Sharing” keyword to make sure record visibility will be considered.

This is incorrect. The without sharing keyword causes Apex code to run in system context, explicitly ignoring the running user's record-level sharing settings.

B. Use "With Sharing” keyword to enforce Field-Level Security.

This is incorrect. The with sharing keyword enforces the running user's record-level sharing, but Field-Level Security (FLS) is always enforced in Apex regardless of the sharing keyword.

1. Apex Developer Guide, "runAs Method": "The runAs method enables you to write test methods that change the user context to an existing user or a new user so that the user’s record sharing is enforced. You can use runAs only in test methods. The original system context is resumed after all runAs code completes." This directly supports using runAs to test record sharing.

2. Apex Developer Guide, "Using the with sharing, without sharing, and inherited sharing Keywords": "Use the without sharing keyword when you want to ensure that the Apex code runs in system context and has access to all records... Field-level security is always enforced regardless of the sharing keywords." This confirms that option A's reasoning is backward and option B's link between with sharing and FLS is false.

3. Salesforce Architects, "Record-Level Security": In the section on programmatic sharing, the guide implicitly requires robust testing for such custom solutions. Testing with runAs is the standard mechanism to validate that the programmatic sharing correctly enforces the intended access controls for various user personas.