Free Salesforce Plat-Dev-210 Actual Exam Questions s - Question 11 Discussion
data is updated in Salesforce. A Data Mapper Load saves the dat
a. What error could cause this behavior?
Choose 2 answers
Makes sense that B and D fit since read-only blocks updates and a misspelled ContextId stops correct record targeting. B,
Maybe A and D since wrong JSON paths or misspelled ContextId can block updates.
B, C - read-only fields and wrong record type can cause partial updates.
I’m thinking B and C here. If some fields are read-only (B), they just won’t update regardless of everything else. And if the RecordId is from the wrong record type (C), the Data Mapper might partially update fields that exist on that record but ignore others, which fits the partial update issue. So these two together explain why only some data gets saved after the OmniScript runs.
C imo, because using the wrong record type RecordId would lead to partial updates or no updates on some fields. Plus, B could be valid too—read-only fields definitely won’t update, so they explain missing changes.
Makes sense that A’s wrong JSON paths stop some fields from updating, and D’s typo in ContextId messes with the RecordId passing. That combo explains partial updates better than B or C. So I’d go with A and D.
C. If the RecordId in the Data Mapper preview is from the wrong record type, the update could affect a different record or fail silently on some fields. That would explain why only some data updates. Also, B makes sense too—if certain fields are read-only, those won’t update at all, so you’d see partial updates. The misspelled ContextId (D) might cause bigger errors, not just partial updates, and if the JSON paths were off (A), I’d expect more fields to be missing rather than just some. So C and B feel like solid choices here.
Maybe D and B. If the fields are read-only in Salesforce, they definitely won’t update, so B fits. And D seems possible because if the RecordId isn’t passed correctly due to a misspelled ContextId, the update might happen on the wrong record or fail silently for some fields. That could explain why only some data updates. A and C focus more on data mapping and record type, but here I think the issue might be with the actual record reference or permissions on fields.
Option A makes sense because if the JSON paths don’t match, data won’t map correctly. Option C could also cause missing updates if the RecordId points to the wrong record type, so those two seem solid.
Option A makes sense because if the JSON paths don’t match, data won’t map correctly. Option D could also be an issue if the RecordId isn’t passed properly due to a typo. Does the question specify which fields aren’t updating?