Universal Container (US) is replacing a home grown CRM solution with Salesforce, UC has decided to migrate operational (Open and active) records to Salesforce, while keeping historical records in legacy system, UC would like historical records to be available in Salesforce on an as needed basis. Which solution should a data architect recommend to meet business requirement?
A.
Leverage real-time integration to pull records into Salesforce.
B.
Bring all data Salesforce, and delete it after a year.
C.
Leverage mashup to display historical records in Salesforce.
D.
Build a chair solution to go the legacy system and display records.
C.
Leverage mashup to display historical records in Salesforce.
Explanation:
A mashup (using iFrames or Lightning Web Components) embeds the legacy system’s UI within Salesforce, letting users view historical records on-demand without data migration. Real-time integration (A) would sync all historical data to Salesforce, violating UC’s "as needed" requirement. Migrating then deleting data (B) is inefficient and loses historical context. A "chair solution" (D) is likely a typo for "custom solution," but rebuilding the legacy UI is redundant. Mashups:
Use Canvas or Connected Apps for secure embedding.
Avoid data duplication and storage costs.
Require no data migration or reconciliation.
This satisfies the requirement for occasional access while keeping historical data externally managed.