A company is planning on sending orders from Salesforce to a fulfillment system. The integration architect has been asked to plan for the integration.
Which two questions should the integration architect consider? Choose 2 answers

• A.Can the fulfillment system make a callback into Salesforce?
• B.Is the product catalog data identical at all times in both systems?
• C.Can the fulfillment system implement a contract-first Outbound Messaging interface?
• D.Can the fulfillment system create new addresses within the Order Create service?

Comment: *

Name: *

Email: *

Verification: *

How do redelivery policies enhance message reliability in Mule applications? (Choose Two)

• A.They ensure messages are only delivered once.
• B.They guarantee message delivery in the correct order.
• C.They prevent messages from being lost during transmission.
• D.They attempt to redeliver messages a specified number of times before triggering an error handling routine.

Comment: *

Name: *

Email: *

Verification: *

Which Mule connectors support local transactions?

• A.JMS Connector
• B.HTTP Connector
• C.VM Connector
• D.Salesforce Connector

Comment: *

Name: *

Email: *

Verification: *

A client system sends marketing-related data to a legacy system within the company data center. The Center for Enablement team has identified that this marketing data has no reuse by any other system.
How should the APIs be designed most efficiently using API-led connectivity?

• A.Create an Experience API to take the data from the client, forward the message to a Process API in the Common Data Model, and invoke a System API to insert the data into the legacy system
• B.Create a Process API, route the request to the System API, and insert the data in the legacy system
• C.Create a System API, call the System API from the client application, and insert the data into the legacy system
• D.Create an Experience API, route the data to the System API, and insert the data in the legacy system

Comment: *

Name: *

Email: *

Verification: *

Refer to the exhibit.

A shopping cart checkout process consists of a web store back end that sends a sequence of HTTPS POST requests to an Experience API, which in turn invokes a Process API using HTTPS. The web store back end executes in a Java EE application server. All API implementations are Mule applications executing in a customer-hosted Mule runtime. End-to-end correlation of all HTTP requests and responses belonging to each checkout instance is required. This is to be done through a common correlation ID so that all log entries written by the web store back end, Experience API implementation, and Process API implementation include the same correlation ID for all requests and responses belonging to the same checkout instance. What is the most efficient way (using the least amount of custom coding or configuration) for the web store back end and the implementations of the Experience API and Process API to participate in end-to-end correlation of the API invocations for each checkout instance?

• A.The Experience API implementation generates a correlation ID for each incoming HTTP request and passes it to the web store back end in the HTTP response, which includes it in all subsequent API invocations to the Experience API.
• B.The web store back end generates a new correlation ID value at the start of checkout and sets it on the X-Correlation-ID HTTP request header in each API invocation belonging to that checkout.
• C.The web store back end, being a Java EE application, automatically uses the thread-local correlation ID generated by the Java EE application server and automatically transmits that to the Experience API using standard HTTP headers.
• D.The web store back end sends a correlation ID value in the HTTP request body in the way required by the Experience API.

Comment: *

Name: *

Email: *

Verification: *