Salesforce Exam Sales Cloud Consultant Topic 7 Question 85 Discussion

Actual exam question for Salesforce's Sales Cloud Consultant exam

Question #: 85
Topic #: 7

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?

AUpdates to child records that have the same parent records are being processed simultaneously.

BContact records should be imposed in the same data batch as Account records.

CAn Apex Trigger on the Account object is firing on insert and causing the Contact import to fail.

DThe consultant has incorrect permissions to import data using Data Loader.

Show Suggested 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.

by Timothy at Mar 07, 2024, 05:08 AM

Limited Time Offer

25%

Off

Get Premium Sales Cloud Consultant Questions as Interactive Web-Based Practice Test or PDF

Contribute your Thoughts:

Submit Cancel

Amber

5 months ago

The consultant should check their permissions to make sure they can import using Data Loader.

upvoted 0 times

...

Lucina

6 months ago

It could also be possible that an Apex Trigger on the Account object is causing the import to fail.

upvoted 0 times

...

Viola

6 months ago

That's a good point, maybe the data needs to be imported together.

upvoted 0 times

...

Omega

6 months ago

Maybe the Contact records should be included in the same data batch as Account records.

upvoted 0 times

...

Ricki

6 months ago

I agree, that could be causing the records to fail.

upvoted 0 times

...

Rasheeda

6 months ago

I think the error could be due to updates to child records happening at the same time.

upvoted 0 times

...

Gearldine

6 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

6 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

6 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

6 months ago

B) Contact records should be imposed in the same data batch as Account records.

upvoted 0 times

...

Yuki

6 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

6 months ago

A) Updates to child records that have the same parent records are being processed simultaneously.

upvoted 0 times

...

Mitsue

7 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

6 months ago

Yeah, Apex Triggers can definitely cause issues with data imports.

upvoted 0 times

...

Halina

6 months ago

I think it's C too. Those triggers can really mess things up.

upvoted 0 times

...

Miss

6 months ago

Yeah, it's important to check for any triggers that might be interfering with the import process.

upvoted 0 times

...

Carmelina

6 months ago

I agree, Apex Triggers can definitely cause issues with data imports.

upvoted 0 times

...

Nguyet

7 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

7 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

...