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 Certified Platform Data Architect (Plat-Arch-201) Exam - Topic 2 Question 51 Discussion

Actual exam question for Salesforce's Salesforce Certified Platform Data Architect (Plat-Arch-201) exam
Question #: 51
Topic #: 2
[All Salesforce Certified Platform Data Architect (Plat-Arch-201) Questions]

UC is migrating individual customers (B2C) data from legacy systems to SF. There are millions of customers stored as accounts and contacts in legacy database.

Which object model should a data architect configure within SF?

Show Suggested Answer Hide Answer
Suggested Answer: A

Using Bulk API to export 1 million records from Salesforce is the best option. Bulk API is a RESTful API that allows you to perform asynchronous operations on large sets of data. You can use Bulk API to create, update, delete, or query millions of records in batches. Bulk API is optimized for performance and scalability, and it can handle complex data loading scenarios.


Contribute your Thoughts:

0/2000 characters
Madonna
5 months ago
Not sure if standard objects will handle all the legacy data smoothly.
upvoted 0 times
...
Malissa
5 months ago
Wait, can you really use person accounts for millions of records?
upvoted 0 times
...
Raina
5 months ago
Definitely go with standard accounts and contacts.
upvoted 0 times
...
Jeff
5 months ago
I think custom objects might be overkill here.
upvoted 0 times
...
Arlene
6 months ago
Person accounts are perfect for B2C scenarios!
upvoted 0 times
...
Garry
6 months ago
I’m leaning towards option A, leveraging person accounts, but I need to double-check if that’s the best fit for millions of records.
upvoted 0 times
...
Tuyet
6 months ago
We practiced a similar question about migrating data, and I feel like custom objects might be necessary if the data structure is unique.
upvoted 0 times
...
Raymon
6 months ago
I think leveraging standard account and contact objects makes sense, but I’m a bit confused about how that would handle individual customer data.
upvoted 0 times
...
Christiane
6 months ago
I remember we discussed person accounts in class, but I'm not sure if we should use standard or custom ones for this migration.
upvoted 0 times
...
Jospeh
6 months ago
The key here is to consider the scale of the migration - millions of customers. I'd recommend going with the standard account and contact objects to keep things simple and scalable.
upvoted 0 times
...
Merlyn
6 months ago
I'm a bit confused on the difference between the standard and custom account/contact objects. I'll need to review the pros and cons of each before deciding.
upvoted 0 times
...
Gracia
6 months ago
Okay, I think I've got this. Since we're dealing with individual customers, the person account object would be the best fit to handle the migration.
upvoted 0 times
...
Ayesha
7 months ago
Hmm, this seems like a tricky one. I'll need to think carefully about the differences between the account and contact objects in Salesforce.
upvoted 0 times
...
Cheryll
1 year ago
I think option D is the way to go - the standard account and contact objects are tried and true, and should be able to handle the volume.
upvoted 0 times
Tequila
11 months ago
In that case, sticking with the standard objects might be the best bet.
upvoted 0 times
...
Dewitt
11 months ago
That's true, but it might also add complexity to the migration process.
upvoted 0 times
...
Nobuko
11 months ago
But wouldn't customizing the person account object give us more flexibility?
upvoted 0 times
...
Pilar
12 months ago
I agree, option D seems like the safest choice.
upvoted 0 times
...
...
Helaine
1 year ago
Haha, imagine trying to fit millions of customers into a custom person account object. Talk about a data explosion!
upvoted 0 times
Ryan
11 months ago
C) Leverage custom account and contact object in SF
upvoted 0 times
...
Lashon
11 months ago
Haha, that would definitely be a data explosion!
upvoted 0 times
...
Kayleigh
12 months ago
A) Leverage person account object in Salesforce
upvoted 0 times
...
...
Marjory
1 year ago
I'm not sure. Maybe we should consider leveraging custom account and contact object in SF for more flexibility.
upvoted 0 times
...
Hyman
1 year ago
I'm not sure about using a custom person account object - wouldn't it be better to leverage the standard account and contact objects?
upvoted 0 times
Misty
11 months ago
I'm not sure about using a custom person account object - wouldn't it be better to leverage the standard account and contact objects?
upvoted 0 times
...
Niesha
11 months ago
C) Leverage custom account and contact object in SF
upvoted 0 times
...
Abraham
11 months ago
B) Leverage custom person account object in SF
upvoted 0 times
...
Lisbeth
12 months ago
A) Leverage person account object in Salesforce
upvoted 0 times
...
...
Galen
1 year ago
The person account object seems like the obvious choice here, as it's designed specifically for B2C scenarios.
upvoted 0 times
...
Fatima
1 year ago
I agree with Claudia. Person account object is the best option for migrating individual customer data.
upvoted 0 times
...
Claudia
1 year ago
I think we should leverage person account object in Salesforce.
upvoted 0 times
...

Save Cancel