When building an integration solution for synchronizing Account data between Salesforce and an external system, which design factors should be considered to ensure resilience during system updates?
A conglomerate is designing a Lightning Web Component (LWC) to display transactions aggregated from different sources. Their current system landscape is as follows:
1. Transactions are created at any time through their various on-premise and cloud-based systems.
2. All necessary transactions are replicated to a custom Transaction object in Salesforce. It is updated periodically so it only has a subset of the necessary transactions between updates.
3. Middleware supports publish-subscribe interactions and provides RESTful Enterprise APIs that can retrieve transactions from on-premise and cloud-based systems.
The company wants to address a usability concern regarding incomplete data displayed on the LWC component. What should the Integration Architect specify so the LWC will be able to display all the required transactions?
Your organization has a legacy system that contains historical customer data. The requirement is to view this customer data within Salesforce when needed, but the data should not be stored in Salesforce. Which integration pattern would be most suitable for this scenario?
A company's security assessment noted vulnerabilities on the un managed packages in their Salesforce orgs, notably secrets that are easily accessible and in plain text, such as usernames, passwords, and OAuth tokens used in callouts from Salesforce.
Which two persistence mechanisms should an integration architect require to be used to ensure that secrets are protected from deliberate or inadvertent exposure?
Your organization is planning an integration between Salesforce and an external e-commerce platform. The company anticipates significant growth in the number of customers in the near future. Which of the following factors should be considered in selecting an appropriate integration solution?