Universal Containers, a global corporation of 50,000 users, has a 24x7 call center operated by 20,000 users that includes employees and contractors. Their sales organization is 10,000 strong and they started processing about 100,000 updates to opportunity custom fields called Priority and NextStep. They also started processing 20,000 updates to a highly nested territory hierarchy. There was a third mass update on a Next Step field on the Action Plan custom object that has Case as a lookup field. Users started seeing a Group membership lock error in the system. What is a probable cause for this error?

A. Lock contention on Account records because of Opportunity object updates. B. Lock contention due to system-initiated sharing rule recalculationC. Lock contention on Case records because of Action Plan custom object updatesD. Lock contention on Territory object because of Territory object updates

Question

Aubrey Carrillo

Computers & Technology

1 September, 15:15

Universal Containers, a global corporation of 50,000 users, has a 24x7 call center operated by 20,000 users that includes employees and contractors. Their sales organization is 10,000 strong and they started processing about 100,000 updates to opportunity custom fields called Priority and NextStep. They also started processing 20,000 updates to a highly nested territory hierarchy. There was a third mass update on a Next Step field on the Action Plan custom object that has Case as a lookup field. Users started seeing a Group membership lock error in the system. What is a probable cause for this error?

A. Lock contention on Account records because of Opportunity object updates. B. Lock contention due to system-initiated sharing rule recalculationC. Lock contention on Case records because of Action Plan custom object updatesD. Lock contention on Territory object because of Territory object updates

+2

Answers (1)

Know the Answer?

Tatum George · Answer 1

B. Lock contention due to system-initiated sharing rule recalculation

Explanation:

By default all spreadsheet cells are locked. We are dealing with different fields here. And for each of them we have different sharing rules which is being initiated by the system. Hence, there will be a case like Lock contention because of the system-initiated sharing rule calculation. Hence there is going to be an error, and the cause is as above.