Salesforce Salesforce-MuleSoft-Developer-II - Salesforce Certified MuleSoft Developer 2 (SP25)

To allow more than one major version of the same API to be exposed by the implementation, the developer should modify the baseUri property in the RAML file to includea variable that indicates the version number. The baseUri property defines the base URL of the API and can include variables that are replaced with actual values when mocking or deploying the API. By using a variable for the versionnumber, the developer can expose different versions of the API using different base URLs and avoid conflicts or confusion. References: https://docs.mulesoft.com/api-designer/design-modify-raml-specs#baseuri https://docs.mulesoft.com/api-manager/2.x/api-versioning

 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 theschema. 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 invoke multiple HTTP APIs in parallel and roll back failed requests in sequence, the developer should use a Scatter-Gather router as a central Saga orchestrator for all API requests with compensating actions for failing routes. A Scatter-Gather router executes multiple routes concurrently and aggregates the results. A Saga orchestrator coordinates a series of actions across different services and handles failures byexecuting compensating actions. Therefore, using a Scatter-Gather router as a Saga orchestrator allows invoking multiple HTTP APIs in parallel and rolling back any failed requests in sequence. References: https://docs.mulesoft.com/mule-runtime/4.3/scatter -gather-concepthttps://docs.mulesoft.com/mule-runtime/4.3/saga

When the HTTP Request operation raises an HTTP CONNECTIVITY error, it triggers an on-error-continue handler that sets a payload with ‘Error in processing your request’. Since no status code is explicitly setin this handler, it defaults to 500 (INTERNAL SERVER ERROR). Therefore, the web client receives an HTTP response with status code 500 and body ‘Error in processing your request’. References:https://docs.mulesoft.com/mule-runtime/4.3/error-handling#on-error-continue

To get response data from the external API after it completes processing, the developer should expose an HTTP callback API in Mule and register it with the external system. This way, the external API can invoke the callback API with theresponse data when it is ready, instead of making the Mule application wait for a long time or poll for a response repeatedly. References:https://docs.mulesoft.com/mule -runtime/4.3/http-listener-ref#callback

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

The result of the Mule Maven Plugin configuration of the valueof property its,keystorePassword in CloudHub 2.0 is that Runtime Manager masks the value. This means that Runtime Manager hides or obscures the value from anyone who views it in Runtime Manager or Anypoint Platform. References:https://docs.mulesoft.com/runtime-manager/runtime-manager-agent-for-mule4#properties-tab

The MuleSoft recommended method to encrypt sensitive property data is to use the Secure Properties Tool that comes with Anypoint Studio. This tool allows encrypting properties files with a secret key and then decrypting them at runtime using the same key. The encryptionkey and sensitive data should be different for each environment to ensure security and avoid accidental exposure of sensitive data. References:https://docs.mulesof t.com/mule-runtime/4.3/secure-configuration-properties