Free Practice Questions for Salesforce Salesforce-MuleSoft-Developer-II Exam

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

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

Based on theexhibit below, if ‘Insecure’ is selected as part of the HTTP Listener configuration, the HTTP listener will only accept HTTP requests. This means that no TLS context will be configured for this listener and no encryption or authentication will be appliedto incoming requests. The protocol attribute of this listener will be set to HTTP instead of HTTPS. References:https://docs.mulesoft.com/http-connector/1.6/http-liste ner-ref#insecure

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

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

To remove values from Mule application A’s Object Store v2, Mule application B can use Object Store v2 REST API. This API allows performing operations on Object Store v2resources using HTTP methods, such as GET, POST, PUT, and DELETE. Mule application B can use the DELETE method to remove values from Mule application A’s Object Store v2 by specifying the object store ID and the key of the value to delete. References:https://docs.mulesoft.com/object-store/osv2-apis

To handle a permanent error response like HTTP:UNAUTHORIZED inside Until Successful, the developer should put the HTTP Request inside a try scope in Unit Successful, and use On Error Continue to catch permanenterrors like HTTP UNAUTHORIZED in the error handler. This way, the developer can avoid retrying requests that will always fail due to a permanent error, and reduce latency. On Error Continue allows the flow to continue processing after handling the error. References: https://docs.mulesoft.com/mule-runtime/4.3/until-successful-scope https://docs.mulesoft.com/mule-runtime/4.3/on-error-continue-concept

When implementing a synchronous API where the event source is an HTTP Listener, Mule automatically propagates some message attributes between flows via outbound and inbound properties. One of these attributes is correlation ID, which is returned to the caller in the response header by default as MULE_CORRELATION_ID. References: https://docs.mulesoft.com/mule-runtime/4.3/about-mule-message#mess age-attributes