Pass the Salesforce Salesforce MuleSoft Salesforce-MuleSoft-Developer-II Questions and answers with CertsForce

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

Mutual TLS (mTLS) is an extension of TLS that requires both parties (client and server) topresent their certificates to each other during the handshake process. This way, both parties can verify each other’s identity and establish a secure connection. The authentication of the server happens before the authentication of the client, as the server sends its certificate first and then requests the client’s certificate. References:https://docs.mulesoft.com/mule-runtime/4.3/tls-configuration#mutual-a uthentication

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

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

A web API can use HTTP Webhook to notify its client of state changes as soon as they occur. A webhook is an HTTP callback that allows an API to sendreal-time notifications to another system or application when an event happens. The client registers a URL with the API where it wants to receive notifications, and then the API sends an HTTP request to that URL with information about the event. References:https://docs.mulesoft.com/connectors/webhook/webhook-connector

To achieve a publish/subscribe model using Anypoint MQ, where each system receives the same gate change notification event, the developer should publish the gate change notificationto an Anypoint MQ exchange, create different Anypoint MQ queues meant for each of the other subscribing systems, and bind the exchange with each of the queues. An exchange is a message routing agent that can send messages to different queues based on predefined criteria. By binding an exchange with multiple queues, each queue receives a copy of every message sent to that exchange. Therefore, each system can subscribe to its own queue and receive every gate change notification event. References:https://docs.mulesoft.com/anypoint-mq/3.x/anypoint-mq-exchanges

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

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 configurationfor 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/intr oduction/introduction-to-the-pom.html#Project_Inheritance

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

To develop an API that retrieves data from a hospital system using reusable Java libraries, thedeveloper should install libraries in a local repository and refer to it in the pom.xml file. This way, the developer can use Maven to manage dependencies and invoke Java code from Mule applications using Java Module operations. References: https://docs.m ulesoft.com/mule-runtime/4.3/java-module-reference#add-the-java-module-to-your-projecthttps://docs.mulesoft.com/mule-runtime/4.3/java-module-reference#invok e-java-code