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 changes using Apex managed sharing, it is important to test the access permissions of different users. The 'runAs' system method is specifically designed for this purpose. It allows you to write test methods that verify different users' access to records, ensuring that your sharing logic works as intended. Therefore, a developer should consider using the 'runAs' system method to test the access controls comprehensively.
No one thinks C is a joke ?
May be B
I see on another testing site that that answer is A and B Run as and With Sharing
I'm conflicted on this, but I think of these three most probable could be C. A doesn't make sense because with sharing controls record level access, not FLS. runAs does nothing for implementation, it is just to test in test class if the runAs user has access or not. I think C, without sharing, would give the users system level access to invoice records, which they need for this use case.
Not A: "With Sharing" doesn't do FLS. Not B: "runAs" is for test classes. Between these answers "C" seems more correct. In other materials there's a different answer too: "Use "With Sharing" keyword to make sure record visibility will always be considered." which could be the answer.
I changed my mind. "B" is the answer. It clearly says "testing". Also the answer that doesn't exist here is correct: "With Sharing" keyword to make sure record visibility will always be considered."