Data-Architect Exam Dumps : Salesforce Certified Platform Data Architect Plat-Arch-201

The best design pattern to satisfy the requirement of accessing order data from an on-premise database with REST API access without consuming SF storage limits is to use SF Connect to virtualize the data in SF and avoid storage limits. SF Connect is an integration tool that allows users to access and integrate data from external sources using external objects. External objects are similar to custom objects, except that the data resides in another system and is accessed in real time via web service callouts. SF Connect supports various adapters to connect to different types of external data sources, such as OData, cross-org, or Apex custom adapter11. Migrate and persist the data in SF to take advantage of native functionality is not a good option because it would consume SF storage limits and require data synchronization between systems. Develop a bidirectional integration between the on-premise system and Salesforce is not a good option because it would be complex and costly to implement and maintain, and it would also consume SF storage limits. Build a UI for the on-premise system and iframe it in Salesforce is not a good option because it would not provide a seamless user experience and it would not allow users to search, report, or perform actions on the external data.

Leverage an External ID from source system orders to import related order lines. This is the recommended solution because it allows you to use the upsert operation to match records based on the External ID field, which is indexed and unique. This avoids the need to query the parent order IDs in Salesforce before importing the order line items, which can cause time-out errors or long delays1.

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.