- Email support@dumps4free.com
A Mule application need to invoice an API hosted by an external system to initiate a process. The external API takes anywhere between one minute and 24 hours to compute its process. Which implementation should be used to get response data from the external API after it completes processing?
A. Use an HTTP Connector to invoke the API and wait for a response
B. Use a Scheduler to check for a response every minute
C. Use an HTTP Connector inside Async scope to invoice the API and wait for a response
D. Expose an HTTP callback API in Mule and register it with the external system
Explanation:
To get response data from the external API after it completes processing, the developer should expose an HTTP callback API in Mule and register it with the external system. This way, the external API can invoke the callback API with the response data when it is ready, instead of making the Mule application wait for a long time or poll for a response repeatedly. References: https://docs.mulesoft.com/mule-runtime/4.3/http-listener-ref#callback
A Mule application for processing orders must log the order ID for every log message output. What is a best practice to enrich every log message with the order ID?
A. Use flow variables within every logger processor to log the order ID
B. Set a flow variable and edit the log4/2.xml file to output the variable as part of the message pattern
C. Create a custom XML SDK component to wrap the logger processor and automatically add the order ID within the connector
D. Use the Tracing module to set logging variables with a Mapped Diagnostic Context
Explanation:
To enrich every log message with the order ID, the developer should use the Tracing module to set logging variables with a Mapped Diagnostic Context (MDC). The Tracing module allows adding custom key-value pairs to log messages using MDC variables. The developer can use Set Logging Variables operation to set the order ID as an MDC variable and then use it in any logger processor within the same thread or event.
References: https://docs.mulesoft.com/tracing-module/1.0/tracing-module-reference#set-logging-variables
Which statement is true when using XML SDK for creating custom message processors?
A. Properties are fields defined by an end user of the XML SDK component and serve as a global configuration for the entire Mule project in which they are used
B. An XML SDK provides both inbound and outbound operations
C. Operations can be reused in recursive calls
D. All operations are public
Explanation:
When using XML SDK for creating custom message processors, all operations are public by default and can be used by any Mule application that imports them. There is no way to make an operation private or protected in XML SDK. References: https://docs.mulesoft.com/mule-sdk/1.1/xml-sdk#operations
A system API that communicates to an underlying MySQL database is deploying to CloudHub. The DevOps team requires a readiness endpoint to monitor all system APIs. Which strategy should be used to implement this endpoint?
A. Create a dedicated endpoint that responds with the API status and reachability of the underlying systems
B. Create a dedicated endpoint that responds with the API status and health of the server
C. Use an existing resource endpoint of the API
D. Create a dedicated endpoint that responds with the API status only
Explanation:
To implement a readiness endpoint to monitor all system APIs, the developer should create a dedicated endpoint that responds with the API status and reachability of the underlying systems. This way, the DevOps team can check if the system API is ready to receive requests and if it can communicate with its backend systems without errors. References: https://docs.mulesoft.com/mule-runtime/4.3/deployment-strategies#readiness-probes
Which pattern should be used to invoke multiple HTTP APIs in parallel and roll back failed requests in sequence?
A. A database as a transactional outbox and an Until Successful router to retry any requests
B. A Parallel for Each scope with each HTTP request wrapped in a Try scope
C. Scatter-Gather as central Saga orchestrator for all API request with compensating actions for failing routes
D. VM queues as a reliability pattern with error handlers to roll back any requests
Explanation:
To invoke multiple HTTP APIs in parallel and roll back failed requests in sequence, the developer should use a Scatter-Gather router as a central Saga orchestrator for all API requests with compensating actions for failing routes. A Scatter-Gather router executes multiple routes concurrently and aggregates the results. A Saga orchestrator coordinates a series of actions across different services and handles failures by executing compensating actions. Therefore, using a Scatter-Gather router as a Saga orchestrator allows invoking multiple HTTP APIs in parallel and rolling back any failed requests in sequence. References: https://docs.mulesoft.com/mule-runtime/4.3/scatter-gather-concept https://docs.mulesoft.com/mule-runtime/4.3/saga
| Page 3 out of 13 Pages |
| Previous |