Salesforce Data-Architect Exam With Confidence Using Practice Dumps

The recommended data model for consumer account data to be stored in Salesforce is to use the Account object with Person Accounts and a new B2C page layout. Person Accounts are a special type of accounts that allow you to store information about individual consumers who are not associated with a business account2. Person Accounts have the following advantages3:

They allow you to use the same standard objects and features that you use for business accounts, such as contacts, opportunities, cases, etc.

They enable you to create different page layouts and record types for B2C and B2B customers, which allows you to customize the user interface and business logic for each segment.

They support large data volumes and can scale up to 50 million records or more, which meets the expected growth of consumers over the next five years.

According to the Data Modeling unit on Trailhead, some of the key actions that should be done when data modeling in Salesforce are identifying data elements, mapping legacy data, and implementing legacy data model. The unit states that “Before you start creating objects and fields in Salesforce, you need to identify the data elements that you want to store and work with. … Next, you need to map your legacy data to Salesforce objects and fields. … Finally, you need to implement your data model in Salesforce by creating custom objects and fields using declarative tools or Metadata API.” Therefore, these are the correct actions for migrating a legacy client server app to Salesforce.

Using an AppExchange package for Data Quality is a good way to match Salesforce data against a trusted source, such as an MDM system. You can use tools like Cloudingo, DupeCatcher, or DemandTools to identify and merge duplicate records, standardize data formats, and enrich data with external sources