SALESFORCE-MULESOFT-DEVELOPER-II Online Practice Questions and Answers

Correct Answer: D

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.

https://docs.mulesoft.com/muleruntime/4.3/about-mule-message#message-attributes

Correct Answer: B

To log all the errors raised by the VM Connector, the developer needs to add an async logger with the name "org.mule.extension.vm' and the level "ERROR' inside the appenders tag of the log4j2.xml file. This will enable logging all error-level events generated by the VM Connector to the console appender. https://docs.mulesoft.com/mule-runtime.3/logging-in-mule#configuringcustom-logging-settings

Correct Answer: D

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 the

response data when it is ready, instead of making the Mule application wait for a long time or poll for a response repeatedly.

Reference:

https://docs.mulesoft.com/mule-runtime.3/http-listener-ref#callback

Correct Answer: C

To configure a common-global-handler flow that can be reused across all of the organization's deployed applications, the developer should create a Mule Plugin project, create a common-globalerror- handler flow inside the plugin project, and

use this plugin as a dependency in all Mule applications. This way, the developer can import the common-global-error-handler flow in any application that needs it and avoid duplicating the error handling logic.

Reference:

https://docs.mulesoft.com/mule-runtime.3/error-handling#global-error-handler

Correct Answer: B

In case of a system failure, in-flight messages in persistent VM queues that have been consumed will be processed after the system comes online. This is because persistent VM queues store messages on disk and guarantee delivery even if there is a system crash or restart. Therefore, any in-flight messages that have been consumed but not processed will be recovered from disk and processed when the system is back online. https://docs.mulesoft.com/mule-runtime.3/vmconnector#persistent-queues

Correct Answer: A

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 send real-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. https://docs.mulesoft.com/connectors/webhook/webhook-connector

Correct Answer: E

To invoke Bioinfo System API using its REST Connector, option E should be added to the pom.xml file.

This option adds a dependency for Bioinfo System API REST Connector with its group ID, artifact ID, version, classifier, and type. The classifier specifies that it is a REST Connector (raml-client), and the type specifies that it is a Mule plugin

(mule-plugin).

Reference:

https://docs.mulesoft.com/apikit.x/apikit-4-generate-from-rest-api-task#add-the-api-dependencyto-the-pom-file

Correct Answer: D

To use API autodiscovery to access and enforce policies for a RESTful implementation, flowRef must be set to the name of the flow that has HTTP listener to receive all incoming RESTful operation requests. This way, API autodiscovery can identify the API implementation and associate it with the corresponding API specification and policies in API Manager. The flow that has HTTP listener is usually the main flow that contains the APIKit Router. https://docs.mulesoft.com/apimanager/ 2.x/api-auto-discovery-new-concept#flowref

Correct Answer: A

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.

Reference:

https://docs.mulesoft.com/api-functional-monitoring/afm-create-monitor#create-a-monitor

Correct Answer: A

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. https://docs.mulesoft.com/api- manager.x/policies-policy-order