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 life cylce. 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.Request and Reply
• B.Batch Data Synchronization
• C.Remote Call In
• D.Fire and Forget

Comment: *

Name: *

Email: *

Verification: *

A conglomerate is designing a Lightning Web Component (LWC) to display transactions aggregated from different sources. Their current system landscape is as follows:
1. Transactions are created at any time through their various on-premise and cloud-based systems.
2. All necessary transactions are replicated to a custom Transaction object in Salesforce. It is updated periodically so it only has a subset of the necessary transactions between updates.
3. Middleware supports publish-subscribe interactions and provides RESTful Enterprise APIs that can retrieve transactions from on-premise and cloud-based systems.
The company wants to address a usability concern regarding incomplete data displayed on the LWC component. What should the Integration Architect specify so the LWC will be able to display all the required transactions?

• A.Call the Enterprise APIs directly from the LWC's JavaScript code and redisplay the LWC on receipt of the API response.
• B.Publish a Platform Event, have the middleware subscribe and update the custom object on receipt of Platform Event.
• C.Use the Continuation class to call the Enterprise APIs and then process the response in a callback method.
• D.Let the Lightning Data Service with an ©wire adapter display new values when the custom object records change.

Comment: *

Name: *

Email: *

Verification: *

A developer has been tasked by the integration architect to build a solution based on the Streaming API. The developer has done some research and has found there are different implementations of the events in Salesforce (Push Topic Events, Change Data Capture, Generic Streaming, Platform Events), but is unsure of to proceed with the implementation.The developer asks the system architect for some guidance.
What should the architect consider when making the recommendation?

• A.Apex triggers can subscribe to Generic Events.
• B.Change Data Capture does not have record access support.
• C.Push Topic Event can define a custom payload.
• D.Change Data Capture can be published from Apex.

Comment: *

Name: *

Email: *

Verification: *

An enterprise customer that has more than 10 Million customers has the following systems and conditions in their landscape:

• A.Salesforce CRM (CRM)- Customer information, Sales and Support information is maintained in CRM.
• B.Enterprise Billing System (EBS) - All customer's monthly billing is generated by this system.
• C.Enterprise Document Management System (DMS) Bills mailed to customers are maintained in the Document Management system.

Comment: *

Name: *

Email: *

Verification: *

A customer of Salesforce has used Platform Events to integrate their Salesforce instance with an external third-party Artificial Intelligence (AI) system. The AI system provides a prediction score for each lead that is received by Salesforce. Once the prediction score is received, the lead information is saved to Platform events for other processes. The trigger on the Platform Events is failing once this was rolled out to Production.
What type of monitoring should the Integration Consultant have considered to monitor this integration?

• A.Monitor the volume of leads that are created in Salesforce.
• B.Set up debug logs for Platform Event triggers to monitor performance.
• C.Monitor Platform Events created per hour limits across the Salesforce instance.
• D.Validate the Platform Event definition matches leads definition.

Comment: *

Name: *

Email: *

Verification: *