Salesforce Certified MuleSoft Developer II (Mule-Dev-301): SALESFORCE-MULESOFT-DEVELOPER-II

Correct Answer: D

To use the OAuth 2.0 Authorization Code grant type for authentication, the HTTP Connector configuration requires the following properties: token URL, authorization URL, client ID, client secret, and local callback URL. The token URL is the endpoint of the authorization server that provides access tokens. The authorization URL is the endpoint of the authorization server that initiates the user consent flow. The client ID and client secret are the credentials of the Mule application registered with the authorization server. The local callback URL is the endpoint of the Mule application that receives the authorization code from the authorization server. Reference: https://docs.mulesoft.com/http-connector.6/http-authentication#oauth-2-0

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 enrich every log message with the order ID, the developer should use the Tracing module to set logging variables with a Mapped Diagnostic Context (MDC). The Tracing module allows adding custom key-value pairs to log messages using MDC variables. The developer can use Set Logging Variables operation to set the order ID as an MDC variable and then use it in any logger processor within the same thread or event. https:// docs.mulesoft.com/tracing-module.0/tracingmodule-reference#set-logging-variables