Universal Containers wishes to move data between 3 back office systems: ERP, financial and a legacy home-grown shipping system that will be replaced 3 months after integration is scheduled to be complete.
What integration pattern should an architect recommend to ensure minimal throwaway code?

Universal containers(UC) leverages the standard opportunity and opportunity product objects to manage their orders in Salesforce. When a deal is closed, all opportunity information, including products and billing contacts, must be send to their ERP application for order fulfillment. As UC has an "express shipping" guarantee, leadership would like order information sent to ERP as quickly as possible after the deal is closed?
How should an Architect fulfill this requirement?

What are two benefits of canvas that an Integration Architect should consider when exposing external systems from within Salesforce?Choose 2 Answers

What should an integration Architect consider when building a visulaforce page that makes client-side callouts to multiple domains that may violate the browser's same-origin policy?Choose 2 answers

Universal Containers would like to integrate to an external system from Salesforceover a secure channel however the external system does not support HTTP-basic authentication. What approach should an integration Architect recommend that enables the external system to trust the data being received?