An Order microservice and a Fulfillment microservice are being designed to communicate with their dients through message-based integration (and NOT through API invocations).
The Order microservice publishes an Order message (a kind of command message) containing the details of an order to be fulfilled. The intention is that Order messages are only consumed by one Mute application, the Fulfillment microservice.
The Fulfilment microservice consumes Order messages, fulfills the order described therein, and then publishes an OrderFulfilted message (a kind of event message). Each OrderFulfilted message can be consumed by any interested Mule application, and the Order microservice is one such Mute application.
What is the most appropriate choice of message broker(s) and message destination(s) in this scenario?

• A.Order messages are sent to a JMS queueOrderFulfilled messages are sent to a JMS topic The Order microservice Interacts with one JMS provider (message broker) and the Fulfillment microservice interacts with a different JMS provider, so that both message brokers can be chosen and scaled to best support the load of each microservice
• B.O Order messages are sent to an Anypoint MQ exchange
  OrderFulfilted messages are sent to an Anypoint MQ queue
  Both microservices interact with Anypoint MQ as the message broker, which must therefore scale to support the toad of both microservices
• C.Older messages are sent directly to the Fulfillment microservices
  OrderFulfilled messages are sent directly to the Order microservice
  The Order microserviceInteracts with one AMQP-compatible message broker and the Fulfillment microservice Interactswith a different AMQP-compatible message broker, so that both message brokers can be chosen and scaled to best support the toad each microservice
• D.Order messages are sent to a JMS queueOrderFulfilled messages are sent to a JMS topicBoth microservices Interact with the same JMS provider (message broker) Instance, which must therefore scale to support the load of both microservices

Comment: *

Name: *

Email: *

Verification: *

A Mule application is deployed to a cluster of two(2) cusomter-hosted Mule runtimes. Currently the node name Alice is the primary node and node named bob is the secondary node. The mule application has a flow that polls a directory on a file system for new files.
The primary node Alice fails for an hour and then restarted.
After the Alice node completely restarts, from what node are the files polled, and what node is now the primary node for the cluster?

• A.Files are polled from Alice node
  Alice is now the primary node
• B.Files are polled form Bob node
  Alice is now the primary node
• C.Files are polled from Alice node
  Bob is the now the primary node
• D.Files are polled form Bob node
  Bob is now the primary node

Comment: *

Name: *

Email: *

Verification: *

A Mule application is synchronizing customer data between two different database systems.
What is the main benefit of using XA transaction over local transactions to synchronize these two database system?

• A.Reduce latency
• B.Increase throughput
• C.Simplifies communincation
• D.Ensure consistency

Comment: *

Name: *

Email: *

Verification: *

Refer to the exhibit.

One of the backend systems invoked by an API implementation enforces rate limits on the number of requests a particular client can make. Both the backend system and the API implementation are deployed to several non-production environments in addition to production.
Rate limiting of the backend system applies to all non-production environments. The production environment, however, does NOT have any rate limiting.
What is the most effective approach to conduct performance tests of the API implementation in a staging (non-production) environment?

• A.Create a mocking service that replicates the backend system's production performance characteristics. Then configure the API implementation to use the mocking service and conduct the performance tests
• B.Use MUnit to simulate standard responses from the backend system then conduct performance tests to identify other bottlenecks in the system
• C.Include logic within the API implementation that bypasses invocations of the backend system in a performance test situation. Instead invoking local stubs that replicate typical backend system responses then conduct performance tests using this API Implementation
• D.Conduct scaled-down performance tests in the staging environment against the rate limited backend system then upscale performance results to full production scale

Comment: *

Name: *

Email: *

Verification: *

An organization has decided on a cloudhub migration strategy that aims to minimize the organizations own IT resources. Currently, the organizational has all of its Mule applications running on its own premises and uses an premises load balancer that exposes all APIs under the base URL https://api.acme.com As part of the migration strategy, the organization plans to migrate all of its Mule applications and load balancer to cloudhub What is the most straight-forward and cost effective approach to the Mule applications deployment and load balancing that preserves the public URLs?

• A.Deploy the Mule applications to Cloudhub
  Update the CNAME record for an api.acme.com in the organizations DNS server pointing to the A record of a cloudhub dedicated load balancer(DLB) Apply mapping rules in the DLB to map URLs to their corresponding Mule applications
• B.Deploy the Mule applications to Cloudhub
  Create CNAME record for api.acme.com in the Cloudhub Shared load balancer (SLB) pointing to the A record of the on-premise load balancer Apply mapping rules in the SLB to map URLs to their corresponding Mule applications
• C.For each migrated Mule application, deploy an API proxy Mule application to Cloudhub with all applications under the control of a dedicated load balancer(CLB) Update the CNAME record for api.acme.com in the organization DNS server pointing to the A record of a cloudhub dedicated load balancer(DLB) Apply mapping rules in the DLB to map each API proxy application to its corresponding Mule applications
• D.Deploy the Mule applications to Cloudhub
  Update the CNAME record for api.acme.com in the organization DNS server pointing to the A record of the cloudhub shared load balancer(SLB) Apply mapping rules in the SLB to map URLs to their corresponding Mule applications.

Comment: *

Name: *

Email: *

Verification: *