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
A heathcare customer wants to use hospital system data, which includes code that was developed using legacy tools and methods. The customer has created reusable Java libraries in order to read the data from the system.
What is the most effective way to develop an API retrieve the data from the hospital system?
A.
Refer to JAR files in the code
B.
Include the libraries writes deploying the code into the runtime
C.
Create the Java code in your project and invoice the data from the code
D.
Install libraries in a local repository and refer to it in the pm.xml file
Install libraries in a local repository and refer to it in the pm.xml file
Explanation:
To develop an API that retrieves data from a hospital system using reusable Java libraries, the developer should install libraries in a local repository and refer to it in the pom.xml file. This way, the developer can use Maven to manage dependencies and invoke Java code from Mule applications using Java Module operations.
References:
https://docs.mulesoft.com/mule-runtime/4.3/java-module-reference#add-the-java-module-to-your-project
https://docs.mulesoft.com/mule-runtime/4.3/java-module-reference#invoke-java-code
A Mule application uses API autodiscovery to access and enforce policies for a RESTful implementation.
A.
Northing because flowRef is an optional attribute which can be passed runtime
B.
The name of the flow that has APlkit Console to receive all incoming RESTful operation requests.
C.
Any of the APIkit generate implement flows
D.
The name of the flow that has HTTP listener to receive all incoming RESTful operation requests
The name of the flow that has HTTP listener to receive all incoming RESTful operation requests
Explanation:
To use API autodiscovery to access and enforce policies for a RESTful implementation, flowRef must be set to the name of the flow that has HTTP listener to receive all incoming RESTful operation requests. This way, API autodiscovery can identify the API implementation and associate it with the corresponding API specification and policies in API Manager. The flow that has HTTP listener is usually the main flow that contains the APIKit Router.
References:
https://docs.mulesoft.com/api-manager/2.x/api-auto-discovery-new-concept#flowref
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
An order processing system is composed of multiple Mule application responsible for warehouse, sales and shipping. Each application communication using Anypoint 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 order ID
B.
Set a custom Anypoint MQ user property to 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
Wrap all Anypoint MQ Publish operations within a With CorrelationID scope from the Tracing module, setting the correlation ID to the order ID
Explanation:
To propagate the order ID as the correlation ID across each message using Anypoint MQ, the developer should wrap all Anypoint MQ Publish operations within a With CorrelationID scope from the Tracing module, setting the correlation ID to the order ID. The With CorrelationID scope allows setting a custom correlation ID for any event that occurs within it. The Tracing module also enables distributed tracing across different Mule applications and services using Anypoint Monitoring.
References:
https://docs.mulesoft.com/tracing-module/1.0/tracing-module-reference#with-correlation-id-scope
https://docs.mulesoft.com/tracing-module/1.0/tracing-module-concepts
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 Caching policies are evaluated; then the API retrieves the data from the API implementation, and the policy does not store the data in Object Store
In case of a cache it, only the HTTP Caching policy is evaluating; then the cached response is returned to the caller
Explanation:
When an HTTP request is received and the HTTP Caching policy is applied first, it checks if there is a cached response for that request in Object Store. If there is a cache hit, meaning that a valid cached response exists, then only the HTTP Caching policy is evaluated and the cached response is returned to the caller without invoking the OAuth policy or the API implementation. If there is a cache miss, meaning that no valid cached response exists, then both the HTTP Caching policy and the OAuth policy are evaluated before invoking the API implementation.
References:
https://docs.mulesoft.com/api-manager/2.x/http-caching-policy#policy-ordering
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
When a client and server are exchanging messages during the mTLS handshake, what is being agreed on during the cipher suite exchange?
A.
A protocol
B.
The TLS version
C.
An encryption algorithm
D.
The Public key format
An encryption algorithm
Explanation
A cipher suite is a set of cryptographic algorithms that are used to secure the communication between a client and a server. A cipher suite consists of four components: a key exchange algorithm, an authentication algorithm, an encryption algorithm, and a message authentication code (MAC) algorithm. During the cipher suite exchange, the client and the server agree on which encryption algorithm to use for encrypting and decrypting the data.
References: https://docs.mulesoft.com/mule-runtime/4.3/tls-configuration#cipher-suites
| Page 1 out of 6 Pages |
Contact Us - Privacy Policy ... Copyright © - All Rights Reserved