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?
Choose 2 answers

A large enterprise customer with the following system landscape is planning to implement Salesforce Sales Cloud.

The following business processes need to be supported in Salesforce:
1. Sales Consultants should be able to have access to current inventory.
2. Enterprise Resource Planning System(ERP) is the system of record for pricing information.
3. Quotes should be generated in Salesforce with pricing from ERP.
4. Sales Management uses a Enterprise Business Intelligence (BI) tool to view Sales dashboards.
5. Master Data Management (MDM) is the system of record for customers and prospects.
6. Invoices should be accessible in Salesforce.
Which systems in the landscape should the Integration Consultant consider to be integrated with Salesforce to support the business requirements?

Universal Containers would like to update their accounting system every time an opportunity is changed to Closed-Won their accounting system occasionally is offline for 3-4 hours to support month-end processing, and they would like the integration design to ensure that no transactions are lost during this down time.
Which two integration designs should the architect consider?
Choose 2 answers

Universal Containers has multiple Salesforce orgs as a result of a number of acquisitions over time. They decide to let the subsidiaries continue using their own orgs but would like to streamline their lead processing.
They identified one org that would act as a gateway to receive all the leads for the group and then distribute them to subsidiary orgs based on lead type. Changes to lead status in subsidiary orgs must be reflected in the gateway org They decide to use Salesforce-to-Salesforce for lead distribution.
What limitation of Salesforce-to-Salesforce must be considered to ensure searchless two-way integration?

Northern Trail Outfitters (NTO) use Salesforce to track leads, opportunities, and to capture order details.
However, Salesforce isn't the system that holds or processes orders. After the order details are captured in Salesforce, an order must be created in the remote system, which manages the orders lifecylce. The Integration Architect for the project is recommending a remote system that will subscribe to the platform event defined in Salesforce.
Which integration pattern should be used for this business use case?