An order processing system is composed of multiple Mule application responsible for warehouse, sales and shipping. Each application communication usingAnypoint MQ. Each message must be correlated against the original order ID for observability and tracing. How should a developer propagate the order ID as the correlation ID across each message?
A. Use the underlying HTTP request of Anypoint MQ to set the‘X-CORRELATION_ID’ header to the orderID
B. Set a custom Anypoint MQ user propertyto propagate the order ID and set the correlation ID in the receiving applications.
C. Use the default correlation ID, Anypoint MQ will sutomatically propagate it.
D. Wrap all Anypoint MQ Publish operations within a With CorrelationID scope from the Tracing module, setting the correlation ID to the order ID
A developer deploys an API to CloudHub and applies an OAuth policy on API Manager. During testing, the API response is slow, so the developer reconfigures the API so that the out-of-the-box HTTP Caching policy is applied first, and the OAuth API policy is applied second. What will happen when an HTTP request is received?
A. In case of a cache hit, both the OAuth and HTTP Caching policies are evaluated; then the cached response is returned to the caller
B. In case of a cache it, only the HTTP Caching policy is evaluating; then the cached response is returned to the caller
C. In case of a cache miss, only the HTTP Caching policy is evaluated; then the API retrieves the data from the API implementation, and the policy stores the data to be cached in Object Store
D. In case of a cache miss, both the OAuth and HTTP Cachingpolicies are evaluated; then the API retrieves the data from the API implementation, and the policy does not store the data in Object Store
Which properties are mandatory on the HTTP Connector configuration in order to use the OAuth 2.0 Authorization Code grant type for authentication?
A.
External callback URL, access token URL, client ID response access token
B.
Token URL, authorization URL, client ID, client secret local callback URL
C.
External callback URL, access token URL, client ID, response refresh token
D.
External callback URL, access token URL, local authorization URL, authorization URL, client ID, client secret
Token URL, authorization URL, client ID, client secret local callback URL
Explanation
To use the OAuth 2.0 Authorization Code grant type for authentication, the HTTP Connector configuration requires the following properties: token URL, authorization URL, client ID, client secret, and local callback URL. The token URL is the endpoint of the authorization server that provides access tokens. The authorization URL is the endpoint of the authorization server that initiates the user consent flow. The client ID and client secret are the credentials of the Mule application registered with the authorization server. The local callback URL is the endpoint of the Mule application that receives the authorization code from the authorization server.
References: https://docs.mulesoft.com/http-connector/1.6/http-authentication#oauth-2-0
A Flight Management System publishes gate change notification events whenever a flight’s arrival gate changes. Other systems, including Baggage Handler System. Inflight Catering System and Passenger Notifications System, must each asynchronously receive the same gate change notification to process the event according. Which configuration is required in Anypoint MQ to achieve this publish/subscribe model?
A.
Publish each client subscribe directly to the exchange.
Have each client subscribe directly to the queue.
B.
Publish the gate change notification to an Anypoint MC queue
Have each client subscribe directly to the queue
C.
Publish the gate change notification to an Anypoint MQ queue.
Create different anypoint MQ exchange meant for each of the other subscribing systems
Bind the queue with each of the exchanges
D.
Publish the gate change notification to an Anypoint MQ exchanhe.
Create different Anypoint MQ queues meant for each of the other subscribing systems.
Bind the exchange with each of the queues.
Publish the gate change notification to an Anypoint MQ exchanhe.
Create different Anypoint MQ queues meant for each of the other subscribing systems.
Bind the exchange with each of the queues.
Explanation:
To achieve a publish/subscribe model using Anypoint MQ, where each system receives the same gate change notification event, the developer should publish the gate change notification to an Anypoint MQ exchange, create different Anypoint MQ queues meant for each of the other subscribing systems, and bind the exchange with each of the queues. An exchange is a message routing agent that can send messages to different queues based on predefined criteria. By binding an exchange with multiple queues, each queue receives a copy of every message sent to that exchange. Therefore, each system can subscribe to its own queue and receive every gate change notification event.
References:
https://docs.mulesoft.com/anypoint-mq/3.x/anypoint-mq-exchanges
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
Create a dedicated endpoint that responds with the API status and reachability of the underlying systems
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
Mule application A is deployed to CloudHub and is using Object Store v2. Mute application B is also deployed to CloudHub.
Which approach can Mule application B use to remove values from Mule application A’S Object Store?
A.
Object Store v2 REST API
B.
CloudHub Connector
C.
Object Store Connector
D.
CloudHub REST API
Object Store v2 REST API
Explanation
To remove values from Mule application A’s Object Store v2, Mule application B can use Object Store v2 REST API. This API allows performing operations on Object Store v2 resources using HTTP methods, such as GET, POST, PUT, and DELETE. Mule application B can use the DELETE method to remove values from Mule application A’s Object Store v2 by specifying the object store ID and the key of the value to delete.
References: https://docs.mulesoft.com/object-store/osv2-apis
A scatter-gather router is configured with four routes:Route A, B, C and D.
Route C false.
A.
Error,errorMesage.payload.results [‘2’]
B.
Payload failures[‘2’]
C.
Error,errorMessage,payload.failures[‘2’]
D.
Payload [‘2’]
Error,errorMessage,payload.failures[‘2’]
Explanation:
The result of accessing route C failure is Error,errorMessage,payload.failures[‘2’]. This is because a scatter-gather router returns an aggregated message that contains an array of results from each route and an array of failures from each route. The failures array contains error objects with information about each failed route execution. To access route C failure, which is the third route (index 2), the developer needs to use Error.errorMessage.payload.failures[‘2’] expression.
References:
https://docs.mulesoft.com/mule-runtime/4.3/scatter-gather-reference#scatter-gather-output
Which pattern can a web API use to notify its client of state changes as soon as they occur?
A.
HTTP Webhock
B.
Shared database trigger
C.
Schedule Event Publisher
D.
ETL data load
HTTP Webhock
Explanation:
A web API can use HTTP Webhook to notify its client of state changes as soon as they occur. A webhook is an HTTP callback that allows an API to send real-time notifications to another system or application when an event happens. The client registers a URL with the API where it wants to receive notifications, and then the API sends an HTTP request to that URL with information about the event.
References:
https://docs.mulesoft.com/connectors/webhook/webhook-connector
| Page 1 out of 6 Pages |
Contact Us - Privacy Policy ... Copyright © - All Rights Reserved