During the implementation of Salesforce, a customer has the following requirements for Sales Order:
1. Sales Order information needs to be shown to users in Salesforce.
2. Sales Orders are maintained in the on-premise enterprise resource planning (ERP).
3. Sales Order information has more than 150 million records.
4. Sales Orders will not be updated in Salesforce.
What should a data architect recommend for maintaining Sales Orders in Salesforce?
The best option for maintaining Sales Orders in Salesforce, given the large volume of records (over 150 million) and the fact that they do not need to be updated in Salesforce, is to use external objects. External objects allow Salesforce to access data stored outside the Salesforce platform, which addresses the requirement of not needing to update the records in Salesforce while providing access to the information within Salesforce interfaces.
B, since the data does not need to be stored or updated in salesforce, external objects are appropriate. https://trailhead.salesforce.com/content/learn/modules/big-data-strategy/compare-data-storage-options Not A. 150 million records should not go on a custom object. This would also require some sort of tool to frequently push and update data, which is unnecessary. Not C, because we do not need to store the data in salesforce. Not D. 150 million records should not be on a custom object. There is nothing more special about a standard object or custom object when it comes to data storage.
the question is pretty clear: What should a data architect recommend for MAINTAINING Sales Orders in Salesforce? -> so in order to maintain such big number of orders in salesforce you need Big Objects if the question was: What should a data architect recommend in order to view Sales Orders in Salesforce? -> external objects and Salesforce Connect (of course depending on the OData or some custom adapter)
B - doesn't need to live in SF, so external objects is best