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

Correct Answer: C

The Cache scope supports time to live (TTL) as a cache invalidation strategy without having to write any additional code. TTL specifies how long the cached response is valid before it expires and needs to be refreshed. The Cache scope also supports custom invalidation strategies using MEL or DataWeave expressions. https://docs.mulesoft.com/mule-runtime.3/cachescope# cache_invalidation

Correct Answer: A

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 encryption key and sensitive data should be different for each environment to ensure security and avoid accidental exposure of sensitive data. https:// docs.mulesoft.com/mule-runtime.3/secure-configurationproperties

Correct Answer: C

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. https://docs.mulesoft.com/mule-runtime.3/about-mule-message#message-attributes

Correct Answer: C

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. https://docs.mulesoft.com/ mule-runtime.3/scattergather-concept https://docs.mulesoft.com/mule-runtime.3/saga

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: A

Based on the code snippet and MUnit test case below, when the MUnit test case is executed, the expected result is that the test case fails with an assertion error. This is because the assert-equals processor compares two values for equality,

and fails if they are not equal. In this case, the expected value is "Hello World', but the actual value returned by the implementation flow is "Hello Mule'. Therefore, the assertion fails and an error is thrown.

Reference:

https://docs.mulesoft.com/munit.3/assert-equals-processor

Correct Answer: B

To ensure idempotent behavior within a Mule flow that contains a subflow with a Scatter-Gather scope, the developer should ensure an error-handling flow performs corrective actions to roll back all changes if any leg of the Scatter-Gather fails. Idempotency means that multiple identical requests have the same effect as a single request. Therefore, if one of the HTTP requests inside the Scatter- Gather fails, the error-handling flow should undo any changes made by other successful requests to ensure consistency and avoid partial updates. https://docs.mulesoft.com/muleruntime/4.3/scatter-gather-concept https://docs.mulesoft.com/mule-runtime.3/error-handling

Correct Answer: C

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.6/http-listener-ref#insecure

Correct Answer: C

To allow more than one major version of the same API to be exposed by the implementation, the developer should modify the baseUri property in the RAML file to include a variable that indicates the version number. The baseUri property defines the base URL of the API and can include variables that are replaced with actual values when mocking or deploying the API. By using a variable for the version number, the developer can expose different versions of the API using different base URLs and avoid conflicts or confusion. https:// docs.mulesoft.com/api-designer/design-modifyraml-specs#baseuri https://docs.mulesoft.com/api-manager.x/api-versioning