Integration-Architect Practice Test

A large enterprise customer has decided to implement Salesforce as their CRM. The current system landscape includes the following:
1. An Enterprise Resource Planning (ERP) solution that is responsible for Customer Invoicing and Order fulfillment.
2. A Marketing solution they use for email campaigns.
The enterprise customer needs their sales and service associates to use Salesforce to view and log their interactions with customers and prospects in Salesforce. Which system should be the System of record for their customers and prospects?

A.

ERP with all prospect data from Marketing and Salesforce.

B.

Marketing with all customer data from Salesforce and ERP.

C.

Salesforce with relevant Marketing and ERP information.

D.

New Custom Database for Customers and Prospects.

Northern Trail Outfitters uses a custom Java application to display code coverage and test results for all of their enterprise applications and is planning to include Salesforce as well. Which Salesforce API should an Integration Architect use to meet the requirement?

A.

SOAP API

B.

Analytics REST API

C.

Metadata API

D.

Tooling API

Universal Containers (UC) uses Salesforce to track the following customer data:
1. Leads,
2. Contacts
3. Accounts
4. Cases

Salesforce is considered to be the system of record for the customer. In addition to Salesforce, customer data exists in an Enterprise Resource Planning (ERP) system, ticketing system, and enterprise data lake. Each of these additional systems have their own unique identifier. UC plans on using middleware to integrate Salesforce with the external systems. UC has a requirement to update the proper external system with record changes in Salesforce and vice versa. Which two solutions should an Integration Architect recommend to handle this requirement?

Choose 2 answers

A.

Locally cache external ID'S at the middleware layer and design business logic to map updates between systems.

B.

Store unique identifiers in an External ID field in Salesforce and use this to update the proper records across systems.

C.

Use Change Data Capture to update downstream systems accordingly when a record changes.

D.

Design an MDM solution that maps external ID's to the Salesforce record ID.

Northern Trail Outfitters (NTO) is looking to integrate three external systems that run nightly data enrichment processes in Salesforce. NTO has both of the following security and strict auditing requirements:
1. The external systems must follow the principle of least privilege, and
2. The activities of the eternal systems must be available for audit.
What should an Integration Architect recommend as a solution for these integrations?

A.

A shared integration user for the three external system integrations.

B.

A shared Connected App for the three external system integrations.

C.

A unique integration user for each external system integration.

D.

A Connected App for each external system integration.

A customer's enterprise architect has identified requirements around caching, queuing, error handling, alerts, retries, event handling, etc. The company has asked the Salesforce integration architect to help fulfill such aspects with their Salesforce program. Which three recommendations should the Salesforce integration architect make? Choose 3 answers

A.

Transform a fire-and-forget mechanism to request-reply should be handled bymiddleware tools (like ETL/ESB) to improve performance.

B.

Provide true message queueing for integration scenarios (including
orchestration,process choreography, quality of service, etc.) given that a middleware solution is required.

C.

Message transformation and protocol translation should be done within Salesforce. Recommend leveraging Salesforce native protocol conversion capabilities as middle watools are NOT suited for such tasks

D.

Event handling processes such as writing to a log, sending an error or recovery process, or sending an extra message, can be assumed to be handled by middleware.

E.

Event handling in a publish/subscribe scenario, the middleware can be used to route requests or messages to active data-event subscribers from active data event publishers.