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

Posted by Alica on Jun 27, 2026 at 08:14 AM

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?

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


Get Premium Plat-Arch-201 Questions as Interactive Web-Based Practice Test or PDF Real Exam Format Detailed Explanations Instant Access Get Your Practice Test
23 comments · newest first
CA
Callie 2 days ago
I feel like D is the best choice overall.
JA
Janet 7 days ago
D helps with performance too.
KA
Kathrine 13 days ago
C keeps it simple and controlled.
DA
Darell 18 days ago
D is good for large data loads.
CA
Callie 23 days ago
Right, C avoids row locking.
JA
Janet 28 days ago
A could work, but might not solve the lock issue.
KA
Kathrine 1 month ago
I prefer D. Less hassle with calculations.
DA
Darell 1 month ago
I think option C is the safest.
CA
Callie 1 month ago
This question is tricky.
AS
Ashley 2 months ago
Reducing batch size is always a good idea in these cases!
LA
Lashawn 2 months ago
Isn't using the API (option A) a bit risky for this?
JO
Johnna 2 months ago
Wow, I didn't know roll-up summaries could cause locking issues!
LO
Lou 2 months ago
I disagree, D seems more efficient to me.
TO
Tomoko 2 months ago
I think option C is the best choice here.
AL
Alpha 2 months ago
Reducing batch size is always a good practice, but I'm not sure about parallel vs. serial.
LE
Leota 3 months ago
Isn't the API option A a bit risky for this scenario?
SE
Serina 3 months ago
Wow, I didn't know roll-up summaries could cause locking errors!
FL
Floyd 3 months ago
I disagree, D seems more efficient for data migration.
HA
Hana 3 months ago
I think option C is the best choice. Serial mode helps avoid locking issues.
RI
Rima 3 months 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.
HA
Halina 4 months ago
I think we discussed deferring roll-up summary calculations during data loads in class. That might be option D, right?
HE
Hector 4 months 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.
ST
Stefania 4 months ago
I remember something about row locking issues, and I think it might have to do with how the data is being processed.
0/2000 characters

Save Cancel