A mule application uses an HTTP request operation to involve an external API.
The external API follows the HTTP specification for proper status code usage.
What is possible cause when a 3xx status code is returned to the HTTP Request operation from the external API?

• A.The request was not accepted by the external API
• B.The request was Redirected to a different URL by the external API
• C.The request was NOT RECEIVED by the external API
• D.The request was ACCEPTED by the external API

Comment: *

Name: *

Email: *

Verification: *

An organization is creating a set of new services that are critical for their business. The project team prefers using REST for all services but is willing to use SOAP with common WS-" standards if a particular service requires it.
What requirement would drive the team to use SOAP/WS-* for a particular service?

• A.Must use XML payloads for the service and ensure that it adheres to a specific schema
• B.Must publish and share the service specification (including data formats) with the consumers of the service
• C.Must support message acknowledgement and retry as part of the protocol
• D.Must secure the service, requiring all consumers to submit a valid SAML token

Comment: *

Name: *

Email: *

Verification: *

Refer to the exhibit. A Mule 4 application has a parent flow that breaks up a JSON array payload into 200 separate items, then sends each item one at a time inside an Async scope to a VM queue.
A second flow to process orders has a VM Listener on the same VM queue. The rest of this flow processes each received item by writing the item to a database.
This Mule application is deployed to four CloudHub workers with persistent queues enabled.
What message processing guarantees are provided by the VM queue and the CloudHub workers, and how are VM messages routed among the CloudHub workers for each invocation of the parent flow under normal operating conditions where all the CloudHub workers remain online?

• A.EACH item VM message is processed AT LEAST ONCE by ONE ARBITRARY CloudHub worker Each of the four CloudHub workers can be expected to process some item VM messages
• B.EACH item VM message is processed AT MOST ONCE by ONE CloudHub worker, with workers chosen in a deterministic round-robin fashion Each of the four CloudHub workers can be expected to process 1/4 of the item VM messages (about 50 items)
• C.ALL item VM messages are processed AT LEAST ONCE by the SAME CloudHub worker where the parent flow was invoked This one CloudHub worker processes ALL 200 item VM messages
• D.ALL item VM messages are processed AT MOST ONCE by ONE ARBITRARY CloudHub worker This one CloudHub worker processes ALL 200 item VM messages

Comment: *

Name: *

Email: *

Verification: *

An Integration Mule application is being designed to synchronize customer data between two systems. One system is an IBM Mainframe and the other system is a Salesforce Marketing Cloud (CRM) instance. Both systems have been deployed in their typical configurations, and are to be invoked using the native protocols provided by Salesforce and IBM.
What interface technologies are the most straightforward and appropriate to use in this Mute application to interact with these systems, assuming that Anypoint Connectors exist that implement these interface technologies?

• A.IBM: DB access CRM: gRPC
• B.IBM: REST CRM:REST
• C.IBM: Active MQ CRM: REST
• D.IBM:QCS CRM: SOAP

Comment: *

Name: *

Email: *

Verification: *

Refer to the exhibit.

A Mule application is deployed to a cluster of two customer-hosted Mute runtimes. The Mute application has a flow that polls a database and another flow with an HTTP Listener.
HTTP clients send HTTP requests directly to individual cluster nodes.
What happens to database polling and HTTP request handling in the time after the primary (master) node of the cluster has railed, but before that node is restarted?

• A.Database polling continues Only HTTP requests sent to the remaining node continue to be accepted
• B.Database polling stops All HTTP requests continue to be accepted
• C.Database polling continues All HTTP requests continue to be accepted, but requests to the failed node Incur increased latency
• D.Database polling stops All HTTP requests are rejected

Comment: *

Name: *

Email: *

Verification: *