What is true about the network connections when a Mule application uses a JMS connector to interact with a JMS provider (message broker)?

• A.To complete sending a JMS message, the JMS connector must establish a network connection with the JMS message recipient
• B.To receive messages into the Mule application, the JMS provider initiates a network connection to the JMS connector and pushes messages along this connection
• C.The JMS connector supports both sending and receiving of JMS messages over the protocol determined by the JMS provider
• D.The AMQP protocol can be used by the JMS connector to portably establish connections to various types of JMS providers

Correct Answer: C

* To send message or receive JMS (Java Message Service) message no separate network connection need to be established. So option A, C and D are ruled out.
Correct answer: The JMS connector supports both sending and receiving of JMS
* JMS Connector enables sending and receiving messages to queues and topics for any message service that implements the JMS specification.
* JMS is a widely used API for message-oriented middleware.
* It enables the communication between different components of a distributed application to be loosely coupled, reliable, and asynchronous.
MuleSoft Doc Reference: https://docs.mulesoft.com/jms-connector/1.7/

Comment: *

Name: *

Email: *

Verification: *

Refer to the exhibit.
A Mule application is being designed to expose a SOAP web service to its clients.
What language is typically used inside the web service's interface definition to define the data structures that the web service Is expected to exchange with its clients?

• A.XSD
• B.JSON Schema
• C.WSDL
• D.RAMI

Comment: *

Name: *

Email: *

Verification: *

Additional nodes are being added to an existing customer-hosted Mule runtime cluster to improve performance. Mule applications deployed to this cluster are invoked by API clients through a load balancer.
What is also required to carry out this change?

• A.API implementations using an object store must be adjusted to recognize the new nodes and persist to them
• B.A new load balancer must be provisioned to allow traffic to the new nodes in a round-robin fashion
• C.External monitoring tools or log aggregators must be configured to recognize the new nodes
• D.New firewall rules must be configured to accommodate communication between API clients and the new nodes

Comment: *

Name: *

Email: *

Verification: *

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 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
• B.Older messages are sent directly to the Fulfillment microservices
  OrderFulfilled messages are sent directly to the Order microservice
  The Order microservice Interacts with one AMQP-compatible message broker and the Fulfillment microservice Interacts with a different AMQP-compatible message broker, so that both message brokers can be chosen and scaled to best support the toad each microservice
• C.Order messages are sent to a JMS queue OrderFulfilled messages are sent to a JMS topic Both microservices Interact with the same JMS provider (message broker) Instance, which must therefore scale to support the load of both microservices
• D.Order messages are sent to a JMS queue OrderFulfilled 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

Correct Answer: D

* If you need to scale a JMS provider/ message broker, - add nodes to scale it horizontally or - add memory to scale it vertically * Cons of adding another JMS provider/ message broker: - adds cost. - adds complexity to use two JMS brokers - adds Operational overhead if we use two brokers, say, ActiveMQ and IBM MQ * So Two options that mention to use two brokers are not best choice. * It's mentioned that "The Fulfillment microservice consumes Order messages, fulfills the order described therein, and then publishes an OrderFulfilled message. Each OrderFulfilled message can be consumed by any interested Mule application." - When you publish a message on a topic, it goes to all the subscribers who are interested - so zero to many subscribers will receive a copy of the message. - When you send a message on a queue, it will be received by exactly one consumer. * As we need multiple consumers to consume the message below option is not valid choice: "Order messages are sent to an Anypoint MQ exchange. OrderFulfilled 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 load of both microservices" * Order messages are only consumed by one Mule application, the Fulfillment microservice, so we will publish it on queue and OrderFulfilled message can be consumed by any interested Mule application so it need to be published on Topic using same broker. * Correct answer: Best choice in this scenario is: "Order messages are sent to a JMS queue. OrderFulfilled messages are sent to a JMS topic. Both microservices interact with the same JMS provider (message broker) instance, which must therefore scale to support the load of both microservices" Tried to depict scenario in diagram:

Comment: *

Name: *

Email: *

Verification: *

What API policy would LEAST likely be applied to a Process API?

• A.Custom circuit breaker
• B.Client ID enforcement
• C.Rate limiting
• D.JSON threat protection

Comment: *

Name: *

Email: *

Verification: *