Salesforce Salesforce-MuleSoft-Developer-II Dumps Questions Answers

 Based on the code snippet, schema.json file, and payload below, the outcome of the given code snippet when a request is sent with the payload is that the Mule flow will throw the exception ‘JSON:SCHEMA_NOT_HONOURED’. This is because the payload does not conform to the schema.json file, which specifies that age must be a number greater than or equal to zero. The payload has age as a string with a negative value, which violates the schema. Therefore, the validate-schema operation throws an error with type ‘JSON:SCHEMA_NOT_HONOURED’. References: https://docs.mulesoft.com/json-module/1.1/json-validate-schema

To test that the payment API is working in production, the developer should create a health check endpoint that listens on a separate port and uses a separate HTTP Listener configuration from the API. This way, the developer can isolate the health check endpoint from the API traffic and avoid affecting the performance or availability of the API. The health check endpoint should return a simple response that indicates the status of the API, such as OK or ERROR. References: https://docs.mulesoft.com/api-functional-monitoring/afm-create-monitor#create-a-monitor

Based on the configuration below, when a HTTP request arrives at the Mule application’s endpoint, the execution order will be A1, B1, F1, B2, A2. This is because policies are executed before and after the API implementation flow according to their order attribute. Policy A has order 1, which means it is executed first before Policy B, which has order 2. The flow is executed after both policies are executed before the flow. Then, Policy B is executed after the flow before Policy A is executed after the flow. References: https://docs.mulesoft.com/api-manager/2.x/policies-policy-order