UC leverages customer MDM as a source of truth. The requirement is to dedupe and store any account or contact created in MDM before the same is created in Salesforce. This ensures data is clean and not duplicated in Salesforce. During peak season, users experience a "Concurrent Request Limit Exceeded" error.
What is the recommended solution?

Universal Containers is a global financial company that sells financial products and services including, bank accounts, loans, and insurance. UC uses Salesforce Service cloud to service their customer via calls, live chat.
The support agents would open bank accounts on the spot for customers who are inquiring about UC bank accounts.
UC Core banking system is the system of record for bank accounts and all accounts opened in salesforce have to be synced in real-time to the core banking system. Support agents need to inform the customers with the newly created bank account ID which has to be generated from the core banking system.
Which integration pattern is recommended for this use case?

Universal Containers has just purchased large volume of contact data from an external vendor. The head of sales would like to use the new data set within the existing production org. The production org currently contains a large volume of contacts.
What should an Architect recommend to prevent data duplication in salesforce?

What are two considerations to make when performing SOAP callouts from within Apex?
Choose 2 answers

Universal Containers (UC) has third-party MDM database which is responsible for maintaining the data for Customer and Contacts information for its organization. UC wants to keep this information up-to-date in Salesforce so that the information is as current as possible. UC wants to provide bi-directional synchronization of the data between the MDM and Salesforce.
What is the recommended approach to solving this problem?