What condition requires using a CloudHub Dedicated Load Balancer?

• A.When cross-region load balancing is required between separate deployments of the same Mule application
• B.When custom DNS names are required for API implementations deployed to customer-hosted Mule runtimes
• C.When API invocations across multiple CloudHub workers must be load balanced
• D.When server-side load-balanced TLS mutual authentication is required between API implementations and API clients

Comment: *

Name: *

Email: *

Verification: *

An organization is implementing a Quote of the Day API that caches today's quote. What scenario can use the CloudHub Object Store connector to persist the cache's state?

• A.When there is one deployment of the API implementation to CloudHub and another one to customer hosted mule runtime that must share the cache state.
• B.When there are two CloudHub deployments of the API implementation by two Anypoint Platform business groups to the same CloudHub region that must share the cache state.
• C.When there is one CloudHub deployment of the API implementation to three workers that must share the cache state.
• D.When there are three CloudHub deployments of the API implementation to three separate CloudHub regions that must share the cache state.

Comment: *

Name: *

Email: *

Verification: *

A Mule application is being designed to perform product orchestration. The Mule application needs to join together the responses from an Inventory API and a Product Sales History API with the least latency.
To minimize the overall latency, what is the most idiomatic (used for its intended purpose) design to call each API request in the Mule application?

• A.Call each API request in a separate lookup call from a DataWeave reduce operator
• B.Call each API request in a separate Async scope
• C.Call each API request in a separate route of a Scatter-Gather
• D.Call each API request in a separate route of a Parallel For Each scope

Comment: *

Name: *

Email: *

Verification: *

Mule application A receives a request Anypoint MQ message REQU with a payload containing a variable-length list of request objects. Application A uses the For Each scope to split the list into individual objects and sends each object as a message to an Anypoint MQ queue.
Service S listens on that queue, processes each message independently of all other messages, and sends a response message to a response queue.
Application A listens on that response queue and must in turn create and publish a response Anypoint MQ message RESP with a payload containing the list of responses sent by service S in the same order as the request objects originally sent in REQU.
Assume successful response messages are returned by service S for all request messages.
What is required so that application A can ensure that the length and order of the list of objects in RESP and REQU match, while at the same time maximizing message throughput?

• A.Use a Scatter-Gather within the For Each scope to ensure response message order Configure the Scatter-Gather with a persistent object store
• B.Perform all communication involving service S synchronously from within the For Each scope, so objects in RESP are in the exact same order as request objects in REQU
• C.Use an Async scope within the For Each scope and collect response messages in a second For Each scope in the order In which they arrive, then send RESP using this list of responses
• D.Keep track of the list length and all object indices in REQU, both in the For Each scope and in all communication involving service Use persistent storage when creating RESP

Comment: *

Name: *

Email: *

Verification: *

Correct Answer is Option B i.e (Perform all communication involving service S synchronously from within the For Each scope, so objects in RESP are in the exact same order as request objects in REQU). Then why it is mentioned Correct Answer: D i.e(Keep track of the list length and all object indices in REQU, both in the For Each scope and in all communication involving service Use persistent storage when creating RESP)

Shandy  

Feb 06, 2024

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: *