MuleSoft-Integration-Architect-I 試験問題を無料オンラインアクセス

An organization has deployed both Mule and non-Mule API implementations to integrate its customer and order management systems. All the APIs are available to REST clients on the public internet.
The organization wants to monitor these APIs by running health checks: for example, to determine if an API can properly accept and process requests. The organization does not have subscriptions to any external monitoring tools and also does not want to extend its IT footprint.
What Anypoint Platform feature provides the most idiomatic (used for its intended purpose) way to monitor the availability of both the Mule and the non-Mule API implementations?

• A.API Functional Monitoring
• B.API Manager
• C.Anypoint Visualizer
• D.Runtime Manager

A mule application is required to periodically process large data set from a back-end database to Salesforce CRM using batch job scope configured properly process the higher rate of records.
The application is deployed to two cloudhub workers with no persistence queues enabled.
What is the consequence if the worker crashes during records processing?

• A.All the records will be processed from scratch by the second worker leading to duplicate processing
• B.Remaining records will be left and processed
• C.Remaining records be processed by second worker
• D.Remaining records will be processed by a new replacement worker

An organization is designing the following two Mule applications that must share data via a common persistent object store instance:
- Mule application P will be deployed within their on-premises datacenter.
- Mule application C will run on CloudHub in an Anypoint VPC.
The object store implementation used by CloudHub is the Anypoint Object Store v2 (OSv2).
what type of object store(s) should be used, and what design gives both Mule applications access to the same object store instance?

• A.Application C and P both use the Object Store connector to access the Anypoint Object Store v2
• B.Application C and P both use the Object Store connector to access a persistent object store
• C.Application P uses the Object Store connector to access a persistent object store Application C accesses this persistent object store via the Object Store REST API through an IPsec tunnel
• D.Application C uses the Object Store connector to access a persistent object Application P accesses the persistent object store via the Object Store REST API

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.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
• B.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
• C.Use a Scatter-Gather within the For Each scope to ensure response message order Configure the Scatter- Gather with a persistent object store
• D.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

An integration Mute application is being designed to process orders by submitting them to a backend system for offline processing. Each order will be received by the Mute application through an HTTPS POST and must be acknowledged immediately. Once acknowledged, the order will be submitted to a backend system.
Orders that cannot be successfully submitted due to rejections from the backend system will need to be processed manually (outside the backend system).
The Mule application will be deployed to a customer-hosted runtime and is able to use an existing ActiveMQ broker if needed.
The backend system has a track record of unreliability both due to minor network connectivity issues and longer outages.
What idiomatic (used for their intended purposes) combination of Mule application components and ActiveMQ queues are required to ensure automatic submission of orders to the backend system, while minimizing manual order processing?

• A.Until Successful component MuleSoft Object Store ActiveMQ is NOT needed or used
• B.Until Successful component ActiveMQ long retry Queue ActiveMQ Dead Letter Queue for manual processing
• C.An On Error scope Non-persistent VM ActiveMQ Dead Letter Queue for manual processing
• D.An On Error scope MuleSoft Object Store ActiveMQ Dead Letter Queue for manual processing