Salesforce Integration-Architecture-Designer Value Pack (Frequently Bought Together)

Universal Containers (UC) is currently managing a custom monolithic web service that runs on an on-premise server.
This monolithic web service is responsible for Point-to-Point (P2P) integrations between:
1. Salesforce and a legacy billing application
2. Salesforce and a cloud-based Enterprise Resource Planning application
3. Salesforce and a data lake.
UC has found that the tight interdependencies between systems is causing integrations to fail.
What should an architect recommend to decouple the systems and improve performance of the integrations?

• A. Leverage modular design by breaking up the web service into smaller pieces for a microservice architecture.
• B. Move the custom monolithic web service from on-premise to a cloud provider.
• C. Re-write and optimize the current web service to be more efficient.
• D. Use the Salesforce Bulk API when integrating back into Salesforce.

Northern Trail Outfitters needs to use Shield Platform Encryption to encrypt social security numbers in order to meet a business requirement.
Which two considerations should an Integration Architect do prior to the implementation of Shield Platform Encryption?
Choose 2 answers

• A. Encrypt the data using the most current key.
• B. Encrypt all the data so that it is secure.
• C. Review shield platform encryption configurations.
• D. Use Shield Platform Encryption as a user authentication or authorization tool.

Northern Trail Outfitters is creating a distributable Salesforce package for other Salesforce orgs within the company. The package needs to call into a custor Apex REST endpoint in the central org. The security team wants to ensure a specific integration account is used in the central org that they will authorize after installation of the package.
Which three items should an architect recommend to secure the integration in the package?
Choose 3 answers

• A. Contact Salesforce support and create a case to temporarily enable API access for managed packages.
• B. Create a connected app in the central org and add the callback URL of each org the package is installed in to redirect to after successful authentication.
• C. Create an Auth provider in the package and set the consumer key and consumer secret of the connected app in the central org.
• D. Use the Auth Provider configured and select the identity type as Named Principal with OAuth 2.0 as the protocol and Select Start Authentication Flow on Save.
• E. Use an encrypted field to store the password that the security team enters and use password management for external orgs and set the encryption method to TLS 1.2.

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?

• A. Batch Data Synchronization
• B. Remote Call In
• C. Fire and Forget
• D. Request and Reply

A large enterprise customer operating in a high regulated industry is planning to implement Salesforce for customer facing associates in both Sales and Service, and back office staff. The business processes that Salesforce supports are critical to the business.
Salesforce will be integrated to multiple back office systems to provide a single interface for associates.
Reliability and monitoring of these integrations is required as associates support customers.
Which integration solution should the architect consider when planning the implementation?

• A. Build a custom integration gateway to support back office system integrations and ensure reliability and monitoring capabilities.
• B. Architect Services in back office systems to support callouts from Salesforce and build reliability, monitoring and reporting capabilities.
• C. Decouple back office system callouts into separate distinct services that have inbuilt error logging and monitoring frameworks.
• D. Leverage Middleware for all back office system integrations ensuring real time alerting, monitoring and reporting capabilities.