Plat-Arch-201 Exam Questions & Answers

The best object model to configure within SF for migrating individual customers (B2C) data from legacy systems is to leverage person account object in Salesforce.Person accounts are a special type of accounts that store information about individual people by combining certain account and contact fields into a single record4. Person accounts are useful for B2C scenarios where there is no need to associate a company name with a contact.Person accounts also support standard Salesforce features and functionality, such as leads, campaigns, reports, dashboards, etc5. Leverage custom person account object in SF is not a good option because there is no such thing as a custom person account object. Leverage custom account and contact object in SF is not a good option because it would require creating and maintaining additional objects and fields that may not be necessary or compatible with standard Salesforce features. Leverage standard account and contact object in SF is not a good option because it would require filling in dummy values for the account name field, which is mandatory for standard accounts.

The correct answer is B, data export wizard. The data export wizard is a tool that allows you to export your data in CSV format, schedule the export process to run once per week, and configure the export settings through the Salesforce UI. The data export wizard can handle up to 51 million records per export. The bulk API, third-party ETL tools, and data loader are also tools that can export data, but they are not as simple or user-friendly as the data export wizard.

Data storage limits and API request limits are two important factors that affect the data integration and storage in Salesforce. Data storage limits determine how much data can be stored in Salesforce, and API request limits determine how many API calls can be made to Salesforce in a 24-hour period. Both of these limits depend on the edition and license type of the Salesforce org. Workflow rule limits and webservice callout limits are not directly related to data integration and storage, but rather to business logic and external services.

Indexing key fields used in report criteria can speed up the query execution and reduce the report run time. Indexes can be created by Salesforce automatically or manually by request. Creating one skinny table per report can also improve the reporting performance by storing frequently used fields in a separate table that does not include complex formulas or joins.

The two solutions that a data architect should recommend to preserve the date timestamps and ownership on records being migrated are:

Enable update records with Inactive Owners Permission: This permission allows users to update record owner and sharing-based records with inactive owners.This can help preserve the original ownership of records that belong to users who are no longer active in Salesforce8.

Enable Set Audit fields upon Record Creation Permission: This permission allows users to set audit fields (such as Created By or Last Modified By) when they create a record via API importing tools like Data Loader.This can help preserve the original date timestamps of records that were created or modified in another system9.

Log a case with SF to update these fields is not a good solution because it is not necessary or feasible to ask Salesforce support to update these fields manually or programmatically.Enable modify all and view all permission is not a good solution because it does not affect the ability to preserve the date timestamps and ownership on records, but rather grants users access to all records regardless of sharing settings