Deal of The Day! Hurry Up, Grab the Special Discount - Save 25% - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions

Salesforce Plat-Arch-201 Exam - Topic 2 Question 9 Discussion

UC has a roll-up summary field on Account to calculate the count of contacts associated with an account. During the account load, SF is throwing an ''Unable to lock a row'' error.Which solution should a data architect recommend, to resolve the error?
C) Perform Batch job in serial mode and reduce batch size
A) Leverage data loader platform API to load data.
B) Perform Batch job in parallel mode and reduce Batch size
D) Defer roll-up summary fields calculation during data migration.

Salesforce Plat-Arch-201 Exam - Topic 2 Question 9 Discussion

Actual exam question for Salesforce's Plat-Arch-201 exam
Question #: 9
Topic #: 2
[All Plat-Arch-201 Questions]

UC has a roll-up summary field on Account to calculate the count of contacts associated with an account. During the account load, SF is throwing an ''Unable to lock a row'' error.

Which solution should a data architect recommend, to resolve the error?

Show Suggested Answer Hide Answer
Suggested Answer: C

The best solution to resolve the error of ''Unable to lock a row'' during the account load is to perform batch job in serial mode and reduce batch size. This is because roll-up summary fields are calculated synchronously when the parent record is updated, and asynchronously when the child record is updated. Therefore, updating many child records at once can cause locking issues on the parent record.To avoid this, it is recommended to use serial mode and smaller batch sizes when loading data using tools like Data Loader or Bulk API12. Leverage data loader platform API to load data is not a good option because it does not specify the mode or batch size. Perform batch job in parallel mode and reduce batch size is not a good option because parallel mode can still cause locking issues even with smaller batches.Defer roll-up summary fields calculation during data migration is not a good option because it is not possible to defer or disable roll-up summary fields calculation


Contribute your Thoughts:

0/2000 characters
Hana
5 days ago
I think option C is the best choice. Serial mode helps avoid locking issues.
upvoted 0 times
...
Rima
10 days ago
I’m a bit confused about the batch size. I remember practicing with batch jobs, but I can’t recall if smaller sizes always help with locking issues.
upvoted 0 times
...
Halina
15 days ago
I think we discussed deferring roll-up summary calculations during data loads in class. That might be option D, right?
upvoted 0 times
...
Hector
20 days ago
I feel like option C could be a good choice since running in serial mode might help avoid the locking problem, but I'm not entirely sure.
upvoted 0 times
...
Stefania
25 days ago
I remember something about row locking issues, and I think it might have to do with how the data is being processed.
upvoted 0 times
...

Save Cancel