Salesforce Certified Platform Data Architect Plat-Arch-201 Exam Questions

Answer : A, B, E

According to theData Modelingunit 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.

Answer : A

Using a third-party data source to update contact information in Salesforce is the best solution to reduce the amount of returned mails.This way, the data architect can ensure that the contact information is accurate and up-to-date without relying on manual verification or deletion of contacts

Answer : D

To help uniquely identify customer across multiple systems, a data architect should recommend creating a custom field as external ID to maintain the customer ID from the MDM solution. An external ID is a custom field that has the ''External ID'' attribute enabled, which means that it contains unique record identifiers from a system outside of Salesforce. By using the customer ID from the MDM solution as an external ID in Salesforce CRM, Contract Management system, and Marketing solution, the data architect can ensure that each customer can be easily identified and integrated across these systems. Option A is incorrect because storing the Salesforce ID in all the solutions to identify the customer will not work if the customer records are created or updated in other systems besides Salesforce CRM. Option B is incorrect because creating a custom object that will serve as a cross reference for the customer ID will require additional configuration effort and may not be consistent with the actual customer records in each system. Option C is incorrect because creating a customer database and using this ID in all systems will require additional infrastructure cost and maintenance effort.

Answer : C

To provide the sales team with the required functionality, a data architect should use a mashup page that will present the billing system records within Salesforce. A mashup page is a web page that combines data from multiple sources into a single integrated view. A mashup page can be created using Visualforce or Lightning Web Components, and can use Salesforce Connect or custom integrations to access external data from the on-premise web-based billing and invoice system. This will allow the sales team to pull a customer record and view their account status, invoice history, and opportunities without navigating outside of Salesforce. Option A is incorrect because creating a custom object and migrating the last 12 months of invoice data into Salesforce so it can be displayed on the account layout will consume a lot of storage space and may not reflect the latest data from the billing system. Option B is incorrect because writing an Apex callout and populating a related list to display on the account record will require additional development effort and may not be scalable or performant for large volumes of data. Option D is incorrect because creating a visual force tab with the billing system encapsulated within an iframe will not allow the sales team to view the billing system records within the customer record, but rather in a separate tab.

Answer : D

Storing the data in a staging database and de-duplicating identical records (option D) is the best solution for a successful migration to mitigate the pain point, as it allows the data architect to identify and merge duplicate customers before they are imported into Salesforce. Hiring an intern manually de-duplicate the records after migrating to Salesforce (option A) is not a good solution, as it may be time-consuming and error-prone, and it does not prevent duplicate records from being created in Salesforce. Migrating the data as is and using Salesforce's de-duplicating feature (option B) is also not a good solution, as it may cause data quality issues and conflicts, and it does not address the root cause of the duplication. Having the users manually clean the data in the old system prior to migration (option C) is also not a good solution, as it may be unrealistic and impractical, and it does not leverage any automated tools or processes.

Answer : B, C

To build a custom big object to support storing more than 100 million records in Salesforce, a data architect should use Metadata API or Big Object in setup. Metadata API is an API that allows developers to create, retrieve, update, or delete metadata components in Salesforce programmatically. Big Object in setup is a user interface that allows admins to create big objects declaratively without writing code. Both tools can be used to define custom big objects and their fields, indexes, and relationships in Salesforce. Option A is incorrect because DX (Developer Experience) is a set of tools that allows developers to create and manage applications on Salesforce Platform, but it does not support creating big objects directly. Option D is incorrect because Object Manager in setup is a user interface that allows admins to create and manage standard and custom objects in Salesforce, but it does not support creating big objects declaratively.

Answer : C, D

Integrate SAP with Salesforce, SAP to legacy CRM but not legacy CRM to Salesforce. This is a good recommendation because it allows both Salesforce and the legacy CRM to interact with the ERP system, which can be the source of truth for some data entities. However, it avoids creating a direct connection between Salesforce and the legacy CRM, which can cause data duplication and synchronization issues. Suggest MDM solution and link MDM to salesforce and SAP.This is another good recommendation because it can help manage the data lifecycle and quality across multiple systems, as well as provide a single view of the customer data