Black Friday Special 70% Discount Offer - Ends in 0d 00h 00m 00s - Coupon code: save70

Newly Released Salesforce Salesforce-MuleSoft-Developer-II Exam PDF

Salesforce Certified MuleSoft Developer 2 (SU24) Questions and Answers

Question 5

Which properties are mandatory on the HTTP Connector configuration in order to use the OAuth 2.0 Authorization Code grant type for authentication?

Options:

A.

External callback URL, access token URL, client ID response access token

B.

Token URL, authorization URL, client ID, client secret local callback URL

C.

External callback URL, access token URL, client ID, response refresh token

D.

External callback URL, access token URL, local authorization URL, authorization URL, client ID, client secret

Question 6

An organization uses CloudHub to deploy all of its applications.

How can a common-global-handler flow be configured so that it can be reused across all of the organization’s deployed applications?

Options:

A.

Create a Mule plugin project

Create a common-global-error-handler flow inside the plugin project.

Use this plugin as a dependency in all Mute applications.

Import that configuration file in Mute applications.

B.

Create a common-global-error-handler flow in all Mule Applications Refer to it flow-ref wherever needed.

C.

Create a Mule Plugin project

Create a common-global-error-handler flow inside the plugin project.

Use this plugin as a dependency in all Mule applications

D.

Create a Mule daman project.

Create a common-global-error-handler flow inside the domain project.

Use this domain project as a dependency.

Question 7

Which statement is true when working with correlation IDS?

Options:

A.

The HTTP Listener regenerates correlation IDs regardless of the HTTP request

B.

The Anypoint MQ Connector automatically propagates correlation IDS

C.

The HTTP Listener generates correlation IDS unless a correlation ID is received in the HTTP request

D.

The VM Connector does not automatically propagate correction IDs

Question 8

A Mule application for processing orders must log the order ID for every log message output.

What is a best practice to enrich every log message with the order ID?

Options:

A.

Use flow variables within every logger processor to log the order ID

B.

Set a flow variable and edit the log4/2.xml file to output the variable as part of the message pattern

C.

Create a custom XML SDK component to wrap the logger processor and automatically add the order ID within the connector

D.

Use the Tracing module to set logging variables with a Mapped Diagnostic Context