ExamGecko
Ask Question

Salesforce Certified MuleSoft Developer II Practice Test - Questions Answers, Page 4

List of questions

Question 31

Report
Export
Collapse

Which plugin or dependency is required to unit test modules created with XML SDK?

XMLUnit
XMLUnit
Junit
Junit
MUnit Extensions Maven plugin
MUnit Extensions Maven plugin
MUnit Maven plugin
MUnit Maven plugin
Suggested answer: C

Explanation:

To unit test modules created with XML SDK, the developer needs to use the MUnit Extensions Maven plugin. This plugin allows testing XML SDK modules using MUnit by adding a dependency to the module under test and using a custom processor tag to invoke it.

Reference: https://docs.mulesoft.com/mule-sdk/1.1/xml-sdk#testing

asked 23/09/2024
ENET SOLUTIONS LOGICOM
35 questions

Question 32

Report
Export
Collapse

Which statement is true when working with correlation IDS?

The HTTP Listener regenerates correlation IDs regardless of the HTTP request
The HTTP Listener regenerates correlation IDs regardless of the HTTP request
The Anypoint MQ Connector automatically propagates correlation IDS
The Anypoint MQ Connector automatically propagates correlation IDS
The HTTP Listener generates correlation IDS unless a correlation ID is received in the HTTP request
The HTTP Listener generates correlation IDS unless a correlation ID is received in the HTTP request
The VM Connector does not automatically propagate correction IDs
The VM Connector does not automatically propagate correction IDs
Suggested answer: C

Explanation:

When working with correlation IDs, the HTTP Listener generates correlation IDs unless a correlation ID is received in the HTTP request. In that case, it propagates the received correlation ID throughout the flow execution. Correlation IDs are used to track events across different flows or applications.

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

asked 23/09/2024
Reed G Porter
28 questions

Question 33

Report
Export
Collapse

Refer to the exhibit.

What is the result of the Mule Maven Plugin configuration of the value of property its,keystorePassoword in CloudHub 2.0?

Salesforce Certified MuleSoft Developer II image Question 33 65990 09232024002859000000

CloudHub encrypts the value
CloudHub encrypts the value
The Mule server encrypts the value
The Mule server encrypts the value
Anypoint Studio secures the value
Anypoint Studio secures the value
Runtime Manager masks the value
Runtime Manager masks the value
Suggested answer: D

Explanation:

The result of the Mule Maven Plugin configuration of the value of 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.

Reference: https://docs.mulesoft.com/runtime-manager/runtime-manager-agent-for-mule4#properties-tab

asked 23/09/2024
Luis Hernaiz
40 questions

Question 34

Report
Export
Collapse

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?

Create a Mule plugin projectCreate 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.
Create a Mule plugin projectCreate 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.
Create a common-global-error-handler flow in all Mule Applications Refer to it flow-ref wherever needed.
Create a common-global-error-handler flow in all Mule Applications Refer to it flow-ref wherever needed.
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
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
Create a Mule daman project. Create a common-global-error-handler flow inside the domain project. Use this domain project as a dependency.
Create a Mule daman project. Create a common-global-error-handler flow inside the domain project. Use this domain project as a dependency.
Suggested answer: C

Explanation:

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-global-error-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/4.3/error-handling#global-error-handler

asked 23/09/2024
Nqobile Nxumalo
42 questions

Question 35

Report
Export
Collapse

A Mule API receives a JSON payload and updates the target system with the payload. The developer uses JSON schemas to ensure the data is valid.

How can the data be validation before posting to the target system?

Use a DataWeave 2.09 transform operation, and at the log of the DataWeave script, add: %dw 2.0 Import.json-moduls
Use a DataWeave 2.09 transform operation, and at the log of the DataWeave script, add: %dw 2.0 Import.json-moduls
Using the DataWeave if Else condition test the values of the payload against the examples included in the schema
Using the DataWeave if Else condition test the values of the payload against the examples included in the schema
Apply the JSON Schema policy in API Manager and reference the correct schema in the policy configuration
Apply the JSON Schema policy in API Manager and reference the correct schema in the policy configuration
Add the JSON module dependency and add the validate-schema operation in the flow, configured to reference the schema
Add the JSON module dependency and add the validate-schema operation in the flow, configured to reference the schema
Suggested answer: D

Explanation:

To validate the data before posting to the target system, the developer should add the JSON module dependency and add the validate-schema operation in the flow, configured to reference the schema. The JSON module provides a validate-schema operation that validates a JSON payload against a JSON schema and throws an error if the payload is invalid.

Reference: https://docs.mulesoft.com/json-module/1.1/json-validate-schema

asked 23/09/2024
Aejaz Rab
28 questions

Question 36

Report
Export
Collapse

Which pattern should be used to invoke multiple HTTP APIs in parallel and roll back failed requests in sequence?

A database as a transactional outbox and an Until Successful router to retry any requests
A database as a transactional outbox and an Until Successful router to retry any requests
A Parallel for Each scope with each HTTP request wrapped in a Try scope
A Parallel for Each scope with each HTTP request wrapped in a Try scope
Scatter-Gather as central Saga orchestrator for all API request with compensating actions for failing routes
Scatter-Gather as central Saga orchestrator for all API request with compensating actions for failing routes
VM queues as a reliability pattern with error handlers to roll back any requests
VM queues as a reliability pattern with error handlers to roll back any requests
Suggested answer: C

Explanation:

To invoke multiple HTTP APIs in parallel and roll back failed requests in sequence, the developer should use a Scatter-Gather router as a central Saga orchestrator for all API requests with compensating actions for failing routes. A Scatter-Gather router executes multiple routes concurrently and aggregates the results. A Saga orchestrator coordinates a series of actions across different services and handles failures by executing compensating actions. Therefore, using a Scatter-Gather router as a Saga orchestrator allows invoking multiple HTTP APIs in parallel and rolling back any failed requests in sequence.

Reference: https://docs.mulesoft.com/mule-runtime/4.3/scatter-gather-concept https://docs.mulesoft.com/mule-runtime/4.3/saga

asked 23/09/2024
BRUNO DE BRIDA
38 questions

Question 37

Report
Export
Collapse

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

External callback URL, access token URL, client ID response access token
External callback URL, access token URL, client ID response access token
Token URL, authorization URL, client ID, client secret local callback URL
Token URL, authorization URL, client ID, client secret local callback URL
External callback URL, access token URL, client ID, response refresh token
External callback URL, access token URL, client ID, response refresh token
External callback URL, access token URL, local authorization URL, authorization URL, client ID, client secret
External callback URL, access token URL, local authorization URL, authorization URL, client ID, client secret
Suggested answer: D

Explanation:

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/1.6/http-authentication#oauth-2-0

asked 23/09/2024
Ellee Chen
40 questions

Question 38

Report
Export
Collapse

An order processing system is composed of multiple Mule application responsible for warehouse, sales and shipping. Each application communication using Anypoint MQ. Each message must be correlated against the original order ID for observability and tracing.

How should a developer propagate the order ID as the correlation ID across each message?

Use the underlying HTTP request of Anypoint MQ to set the 'X-CORRELATION_ID' header to the order ID
Use the underlying HTTP request of Anypoint MQ to set the 'X-CORRELATION_ID' header to the order ID
Set a custom Anypoint MQ user property to propagate the order ID and set the correlation ID in the receiving applications.
Set a custom Anypoint MQ user property to propagate the order ID and set the correlation ID in the receiving applications.
Use the default correlation ID, Anypoint MQ will sutomatically propagate it.
Use the default correlation ID, Anypoint MQ will sutomatically propagate it.
Wrap all Anypoint MQ Publish operations within a With CorrelationID scope from the Tracing module, setting the correlation ID to the order ID
Wrap all Anypoint MQ Publish operations within a With CorrelationID scope from the Tracing module, setting the correlation ID to the order ID
Suggested answer: D

Explanation:

To propagate the order ID as the correlation ID across each message using Anypoint MQ, the developer should wrap all Anypoint MQ Publish operations within a With CorrelationID scope from the Tracing module, setting the correlation ID to the order ID. The With CorrelationID scope allows setting a custom correlation ID for any event that occurs within it. The Tracing module also enables distributed tracing across different Mule applications and services using Anypoint Monitoring.

Reference: https://docs.mulesoft.com/tracing-module/1.0/tracing-module-reference#with-correlation-id-scope https://docs.mulesoft.com/tracing-module/1.0/tracing-module-concepts

asked 23/09/2024
Miguel Villanueva
33 questions

Question 39

Report
Export
Collapse

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?

Use flow variables within every logger processor to log the order ID
Use flow variables within every logger processor to log the order ID
Set a flow variable and edit the log4/2.xml file to output the variable as part of the message pattern
Set a flow variable and edit the log4/2.xml file to output the variable as part of the message pattern
Create a custom XML SDK component to wrap the logger processor and automatically add the order ID within the connector
Create a custom XML SDK component to wrap the logger processor and automatically add the order ID within the connector
Use the Tracing module to set logging variables with a Mapped Diagnostic Context
Use the Tracing module to set logging variables with a Mapped Diagnostic Context
Suggested answer: D

Explanation:

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.

Reference: https://docs.mulesoft.com/tracing-module/1.0/tracing-module-reference#set-logging-variables

asked 23/09/2024
David Vicente Martinez
33 questions

Question 40

Report
Export
Collapse

Refer to the exhibit.

What is the result if ''Insecure'' selected as part of the HTTP Listener configuration?

Salesforce Certified MuleSoft Developer II image Question 40 65997 09232024002859000000

The HTTP Listener will trust any certificate presented by the HTTP client
The HTTP Listener will trust any certificate presented by the HTTP client
The HTTP Lister will accept any unauthenticated request
The HTTP Lister will accept any unauthenticated request
The HTTP listener will only accept HTTP requests
The HTTP listener will only accept HTTP requests
Mutual TLS authentication will be enabled between this HTTP Listener and an HTTP client
Mutual TLS authentication will be enabled between this HTTP Listener and an HTTP client
Suggested answer: C

Explanation:

Based on the exhibit 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 applied to incoming requests. The protocol attribute of this listener will be set to HTTP instead of HTTPS.

Reference: https://docs.mulesoft.com/http-connector/1.6/http-listener-ref#insecure

asked 23/09/2024
Robert Miletich
46 questions
Total 60 questions
Go to page: of 6
Search

Related questions