Salesforce exams4sure pass Mulesoft-integration-architect-i Exam Guide by Cory q27 vce pdf

Page: 18 / 20

Exam Name:	Salesforce Certified MuleSoft Platform Integration Architect (Mule-Arch-202)
Exam Code:	MuleSoft-Integration-Architect-I Dumps
Vendor:	Salesforce	Certification:	Salesforce MuleSoft
Questions:	273 Q&A's	Shared By:	cory

Question 72

An organization's security requirements mandate centralized control at all times over authentication and authorization of external applications when invoking web APIs managed on Anypoint Platform.

What Anypoint Platform feature is most idiomatic (used for its intended purpose), straightforward, and maintainable to use to meet this requirement?

Options:

Client management configured in access management

Identity management configured in access management

Enterprise Security module coded in Mule applications

External access configured in API Manager

Discussion

Question 73

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?

Options:

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

Order 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 load of each microservice

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

Discussion

Question 74

When designing an upstream API and its implementation, the development team has been advised to not set timeouts when invoking downstream API. Because the downstream API has no SLA that can be relied upon. This is the only donwstream API dependency of that upstream API. Assume the downstream API runs uninterrupted without crashing. What is the impact of this advice?

Options:

The invocation of the downstream API will run to completion without timing out.

An SLA for the upstream API CANNOT be provided.

A default timeout of 500 ms will automatically be applied by the Mule runtime in which the upstream API implementation executes.

A load-dependent timeout of less than 1000 ms will be applied by the Mule runtime in which the downstream API implementation executes.