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
The Center for Enablement team published a common application as a reusable module to the central Nexus repository.
How can the common application be included in all API implementations?
A.
Download the common application from Naxus and copy it to the src/main/resources folder in the API
B.
Copy the common application’s source XML file and out it in a new flow file in the src/main/mule folder
C.
Add a Maven dependency in the PCM file with multiple-plugin as <classifier>
D.
Add a Maven dependency in the POM file with jar as <classifier>
Add a Maven dependency in the POM file with jar as <classifier>
Explanation:
To include a common application as a reusable module in all API implementations, the developer should add a Maven dependency in the POM file with jar as <classifier>. This way, the developer can reuse Mule code from another application by packaging it as a JAR file and adding it as a dependency in the POM file of the API implementation. The classifier element specifies that it is a JAR file.
References:
https://docs.mulesoft.com/mule-runtime/4.3/mmp-concept#add-a-maven-dependency-to-the-pom-file
A healthcare portal needs to validate the token that it sends to a Mule API. The developer plans to implement a custom policy using the HTTP Policy Transform Extension to match the token received in the header from the heathcare portal. Which files does the developer need to create in order to package the custom policy?
A.
Deployable ZIP file, YAML configuration file
B.
JSON properties file, YAML configuration file
C.
JSON properties file, XML template file
D.
XML template file, YAML configuration file
XML template file, YAML configuration file
Explanation:
To package a custom policy using the HTTP Policy Transform Extension, the developer needs to create an XML template file and a YAML configuration file. The XML template file defines the policy logic using Mule components and placeholders for user-defined properties. The YAML configuration file defines the metadata of the policy, such as its name, description, category, parameters, and dependencies.
References:
https://docs.mulesoft.com/api-manager/2.x/http-policy-transform#packaging-the-policy
A custom policy needs to be developed to intercept all cutbound HTTP requests made by Mule applications.
Which XML element must be used to intercept outbound HTTP requests?
A.
It is not possible to intercept outgoing HTTP requests, only inbound requests
B.
http-policy:source
C.
htt-policy:operation
D.
http-policy:processor
http-policy:processor
The http-policy:processor element is used to intercept outbound HTTP requests made by Mule applications. It allows customizing the request before it is sent to the target API and modifying the response after it is received from the target API.
References:
https://docs.mulesoft.com/api-manager/2.x/policy-mule4-custom-policy#policy-xml-file
Multiple individual Mute application need to use the Mule Maven plugin to deploy to CloudHub.
The plugin configuration should .. reused where necessary and anything project, specific should be property-based.
Where should the Mule Maven details be configured?
A.
A parent pom.xml
B.
Settings, xml
C.
Pom, xml
D.
A Bill of Materials (BOM) parent pm
A parent pom.xml
Explanation:
To reuse Mule Maven plugin configuration across multiple individual Mule applications, the developer should use a parent pom.xml file. A parent pom.xml file defines common configuration for one or more child projects that inherit from it. The developer can specify common properties and dependencies for all child projects in the parent pom.xml file, such as Mule Maven plugin configuration, and then reference them in each child project’s pom.xml file using placeholders.
References:
https://docs.mulesoft.com/mule-runtime/4.3/mmp-concept#parent-pom
https://maven.apache.org/guides/introduction/introduction-to-the-pom.html#Project_Inheritance
A Mule application deployed to a standardalone Mule runtime uses VM queues to publish messages to be consumed asynchronously by another flow. In the case of a system failure, what will happen to in-flight messages in the VM queues that have been consumed?
A.
For nay type of queue, the message will be processed after the system comes online
B.
For persistent queues, the message will be processed after the system comes online
C.
For transient queues, the message will be processed after the system comes online
D.
For any type of queue, the message will be lost
For persistent queues, the message will be processed after the system comes online
Explanation:
In case of a system failure, in-flight messages in persistent VM queues that have been consumed will be processed after the system comes online. This is because persistent VM queues store messages on disk and guarantee delivery even if there is a system crash or restart. Therefore, any in-flight messages that have been consumed but not processed will be recovered from disk and processed when the system is back online.
References:
https://docs.mulesoft.com/mule-runtime/4.3/vm-connector#persistent-queues
Which command is used to convert a JKS keystore to PKCS12?
A.
Keytool-importkeystore –srckeystore keystore p12-srcstoretype PKCS12 –destkeystore keystore.jks–deststoretype JKS
B.
Keytool-importkeystore –srckeystore keystore p12-srcstoretype JKS –destkeystore keystore.p12–deststoretype PKCS12
C.
Keytool-importkeystore –srckeystore keystore jks-srcstoretype JKS –destkeystore keystore.p13–deststoretype PKCS12
D.
Keytool-importkeystore –srckeystore keystore jks-srcstoretype PKCS12 –destkeystore keystore.p12–deststoretype JKS
Keytool-importkeystore –srckeystore keystore p12-srcstoretype JKS –destkeystore keystore.p12–deststoretype PKCS12
Explanation:
To convert a JKS keystore to PKCS12, the developer needs to use the keytool-importkeystore command with the following options: -srckeystore keystore.jks -srcstoretype JKS -destkeystore keystore.p12 -deststoretype PKCS12. This command imports all entries from a source JKS keystore (keystore.jks) into a destination PKCS12 keystore (keystore.p12).
References:
https://docs.oracle.com/en/java/javase/11/tools/keytool.html#GUID-5990A2E4-78E3-47B7-AE75-6D1826259549
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
| Page 1 out of 6 Pages |
Contact Us - Privacy Policy ... Copyright © - All Rights Reserved