Refer to the exhibits.
The my-app xml file contains an Error Handier scope named "global-error-handler"
The Error Handler scope needs to be set to be the default error handler for every flow in the Mule application
Where and how should the value "global-error-handler" be added in the Mule project so that the Error Handler scope is the default error handler of the Mule application?
How are query parameters dynamically passed to an outbound REST request using an HTTP Request operation?
In General > Request > Query Parameters, click the plus icon (+) to add a parameter to a request. Type a name and value for the parameter or use a DataWeave expression to define the name and value.
A REST connect module is generated for a RAML specification. and then the rest connect module is imported in mule application in Anypoint Studio. For each method of the RAML specification , what does the REST connect module provide?
Correct answer is an operation. For each method of the RAML specification , REST connect module provide an operation.
Please refer to the below screenshot.
An SLA based policy has been enabled in API Manager. What is the next step to configure the API proxy to enforce the new SLA policy?
Correct answer is Add required headers to RAML specification and redeploy new API proxy
MuleSoft Doc Ref : https://docs.mulesoft.com/api-manager/2.x/tutorial-manage-an-api
Steps are as below :
Add the Required RAML Snippet
SLA-based rate limiting requires adding a RAML or OAS snippet to your API. This procedure demonstrates adding a RAML snippet.
Specify the client ID and secret as query parameters.
Add a section called traits: at the RAML root level to define query parameters:
traits:
- client-id-required:
queryParameters:
client_id:
type: string
client_secret:
type: string
Add the client-id-required trait to every method that requires these query parameters:
/users:
get:
is: [client-id-required]
description: Gets a list of JSONPlaceholder users.
Step 2 : Add the SLA Tier in API Manager
Step 3 : Apply the policy and redeploy
Refer to the exhibits.
A Mule application has an HTTP Request that is configured with hardcoded values. To change this, the Mule application is configured to use a properties file named config.yaml.
what valid expression can the HTTP Request host value be set to so that it is no longer hardcoded?
Correct answer is ${training.host}
--------------------------------------------------------------------------------------------------------------------------------------------------
How to Configure Properties to Mule 4.X Platform?
1)Go to/src/main/resourcesproject directory.
2)Create a configuration file with the name configuration.yaml inside the newly created config folder.
3)Go To Project >Global Element> Create > General >select the configuration.yaml file create in step-2)
4)To verify develop a simple flow with HTTP listener which has above entries. Put the logger that prints the values on console.
5)Additional info:Similarly, when you want to access this port in DataWeave you need to use p function
