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 Exam Sales-Cloud-Consultant Topic 7 Question 85 Discussion

Actual exam question for Salesforce's Salesforce Certified Sales Cloud Consultant Exam exam
Question #: 85
Topic #: 7
[All Salesforce Certified Sales Cloud Consultant Exam Questions]

A consultant for Cloud Kicks is migrating data from an on-premise system to Salesforce. The consultant has imported.

Account records, and is attempting to import the associated Contacts using Data Loader, but the import has failed records. The error messages all read UNABLE TO LOCK ROW,

What could be causing these records to fail?

Show Suggested Answer Hide Answer
Suggested Answer: A

The most likely cause of the records failing is that updates to child records that have the same parent record are being processed simultaneously. This can cause the records to fail because child records must be imported after the parent records have been imported, and if the parent record is being updated at the same time as the child records, the import will fail. The other options are not likely to be the cause of the failed import.


Contribute your Thoughts:

Amber
2 months ago
User 6: The consultant should check their permissions to make sure they can import using Data Loader.
upvoted 0 times
...
Lucina
2 months ago
User 5: It could also be possible that an Apex Trigger on the Account object is causing the import to fail.
upvoted 0 times
...
Viola
3 months ago
User 4: That's a good point, maybe the data needs to be imported together.
upvoted 0 times
...
Omega
3 months ago
User 3: Maybe the Contact records should be included in the same data batch as Account records.
upvoted 0 times
...
Ricki
3 months ago
User 2: I agree, that could be causing the records to fail.
upvoted 0 times
...
Rasheeda
3 months ago
User 1: I think the error could be due to updates to child records happening at the same time.
upvoted 0 times
...
Gearldine
3 months ago
That does make sense. Importing Contact records in the same batch as Account records could potentially solve this issue.
upvoted 0 times
...
Renato
3 months ago
I bet it's those updates to child records. Salesforce can be a real 'lock it down' kind of platform, you know?
upvoted 0 times
...
Kattie
3 months ago
Dude, the consultant's trying to wrangle data like a cowboy at a rodeo. Gotta make sure those permissions are on point, yo!
upvoted 0 times
Jerry
3 months ago
B) Contact records should be imposed in the same data batch as Account records.
upvoted 0 times
...
Yuki
3 months ago
C) An Apex Trigger on the Account object is firing on insert and causing the Contact import to fail.
upvoted 0 times
...
Skye
3 months ago
A) Updates to child records that have the same parent records are being processed simultaneously.
upvoted 0 times
...
...
Mitsue
3 months ago
I'm gonna go with C on this one. Apex Triggers can be real party-crashers when it comes to data imports.
upvoted 0 times
Terrilyn
3 months ago
Yeah, Apex Triggers can definitely cause issues with data imports.
upvoted 0 times
...
Halina
3 months ago
I think it's C too. Those triggers can really mess things up.
upvoted 0 times
...
Miss
3 months ago
Yeah, it's important to check for any triggers that might be interfering with the import process.
upvoted 0 times
...
Carmelina
3 months ago
I agree, Apex Triggers can definitely cause issues with data imports.
upvoted 0 times
...
...
Nguyet
4 months ago
I believe the correct answer is A) Updates to child records that have the same parent records are being processed simultaneously. It makes sense that this could cause record locking issues.
upvoted 0 times
...
Johanna
4 months ago
Hmm, looks like a tricky one. Could be those pesky Apex Triggers playing tricks on us. Or maybe the consultant's login is more like a 'consultant: read-only' situation.
upvoted 0 times
...
Myong
4 months ago
Could it be that an Apex Trigger on the Account object is blocking the Contact import process?
upvoted 0 times
...
Florinda
4 months ago
Maybe there are other processes running that are trying to update the same records at the same time.
upvoted 0 times
...
Gearldine
4 months ago
I think the error message UNABLE TO LOCK ROW is related to record locking issues.
upvoted 0 times
...

Save Cancel
az-700  pass4success  az-104  200-301  200-201  cissp  350-401  350-201  350-501  350-601  350-801  350-901  az-720  az-305  pl-300  

Warning: Cannot modify header information - headers already sent by (output started at /pass.php:70) in /pass.php on line 77