Salesforce SALESFORCE-MULESOFT-DEVELOPER-II Online Practice Questions and Exam Preparation

Salesforce SALESFORCE-MULESOFT-DEVELOPER-II Online Questions & Answers

• Question 41:

  Mule application A is deployed to CloudHub and is using Object Store v2. Mute application B is also deployed to CloudHub. Which approach can Mule application B use to remove values from Mule application A'S Object Store?

  A. Object Store v2 REST API
  B. CloudHub Connector
  C. Object Store Connector
  D. CloudHub REST API
  A. Object Store v2 REST API

  ---

  Explanation/Reference:

  To remove values from Mule application A's Object Store v2, Mule application B can use Object Store v2 REST API. This API allows performing operations on Object Store v2 resources using HTTP methods, such as GET, POST, PUT, and DELETE. Mule application B can use the DELETE method to remove values from Mule application A's Object Store v2 by specifying the object store ID and the key of the value to delete. https:// docs.mulesoft.com/object-store/osv2-apis

• Question 42:

  Refer to the exhibit.

  

  A Mule application pom.xml configures the Maven Resources plugin to exclude parsing binary files in the project's src/main/resources/certs directory. Which configuration of this plugin achieves a successful build?

  

  

  A. Option A
  B. Option B
  C. Option C
  D. Option D
  C. Option C

  ---

  Explanation/Reference:

  To configure the Maven Resources plugin to exclude parsing binary files in the project's src/main/resources/ certs directory, option C should be used. This option specifies that any files with .cer or .jks extensions under the certs directory should be excluded from filtering. Filtering is a process of replacing placeholders with actual values in resource files during the build process. Binary files should not be filtered because they may become corrupted or unusable. Reference: https://maven.apache.org/plugins/maven-resources-plugin/examples/filter.html https://maven.apache.org/ plugins/maven-resources-plugin/examples/include-exclude.html

• Question 43:

  Refer to the exhibit.

  

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

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

  ---

  Explanation/Reference:

  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

• Question 44:

  When registering a client application with an existing API instance or API Group instance, what is required to manually approve or reject request access?

  A. To configure the SLA tier for the application and have the role of Organization Administrator, API Manager Environment Administrator, or the Manage Contacts permission
  B. To configure the SLA tier for the application and have the Exchange Administrator permission
  C. To configure the SLA tier for the application
  D. To only have Exchange Administrator permission
  D. To only have Exchange Administrator permission

  ---

  Explanation/Reference:

  To manually approve or reject request access when registering a client application with an existing API instance or API Group instance, it is required to configure the SLA tier for the application and have one of the following roles or

  permissions: Organization Administrator, API Manager Environment Administrator, or Manage Contracts permission. These roles or permissions allow managing client applications and contracts in API Manager.

  Reference:

  https://docs.mulesoft.com/api-manager.x/client-applications#managing-client-applications-andcontracts

• Question 45:

  A scatter-gather router is configured with four routes:Route A, B, C and D. Route C false.

  A. Error,errorMesage.payload.results ["2']
  B. Payload failures["2']
  C. Error,errorMessage,payload.failures["2']
  D. Payload ["2']
  A. Error,errorMesage.payload.results ["2']

  ---

  Explanation/Reference:

  The result of accessing route C failure is Error,errorMessage,payload.failures["2']. This is because a scatter- gather router returns an aggregated message that contains an array of results from each route and an array of failures from each

  route. The failures array contains error objects with information about each failed route execution. To access route C failure, which is the third route (index 2), the developer needs to use Error.errorMessage.payload.failures["2'] expression.

  Reference:

  https://docs.mulesoft.com/mule-runtime.3/scatter-gather-reference#scatter-gather-output

• Question 46:

  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?

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

  ---

  Explanation/Reference:

  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. https://docs.mulesoft.com/tracing-module.0/tracing- module-reference#withcorrelation-id-scope https://docs.mulesoft.com/tracing-module.0/tracing-module-concepts

• Question 47:

  Refer to the exhibit.

  

  The flow name is "implementation'' with code for the MUnit test case. When the MUnit test case is executed, what is the expected result?

  A. The test case fails with an assertion error
  B. The test throws an error and does not start
  C. The test case fails with an unexpected error type
  D. The test case passes
  A. The test case fails with an assertion error

  ---

  Explanation/Reference:

  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

• Question 48:

  The Center for Enablement team published a common application as a reusable module to the central Nexus repository. How can the common application be included in all API implementations?

  A. Download the common application from Naxus and copy it to the src/main/resources folder in the API
  B. Copy the common application's source XML file and out it in a new flow file in the src/main/mule folder
  C. Add a Maven dependency in the PCM file with multiple-plugin as
  D. Add a Maven dependency in the POM file with jar as
  D. Add a Maven dependency in the POM file with jar as

  ---

  Explanation/Reference:

  To include a common application as a reusable module in all API implementations, the developer should add a Maven dependency in the POM file with jar as . This way, the developer can reuse Mule code from another application by packaging it as a JAR file and adding it as a dependency in the POM file of the API implementation. The classifier element specifies that it is a JAR file. https://docs.mulesoft.com/mule-runtime.3/mmp-concept#add-a-maven-dependencytothe-pom-file

• Question 49:

  A Mule implementation uses a HTTP Request within an Unit Successful scope to connect to an API. How should a permanent error response like HTTP:UNAUTHORIZED be handle inside Until Successful to reduce latency?

  A. Configure retrying until a MULERETRY_EXHAUSTED error is raised or the API responds back with a successful response.
  B. In Until Successful configuration, set the retry count to 1 for error type HTTP: UNAUTHORIZED.
  C. Put the HTTP Request inside a try scope in Unit Successful. In the error handler, use On Error Continue to catch permanent errors like HTTP UNAUTHORIZED.
  D. Put the HTTP Request inside a try scope in Unit Successful. In the error handler, use On Error Propagate to catch permanent errors like HTTP UNAUTHORIZED.
  C. Put the HTTP Request inside a try scope in Unit Successful. In the error handler, use On Error Continue to catch permanent errors like HTTP UNAUTHORIZED.

  ---

  Explanation/Reference:

  To handle a permanent error response like HTTP:UNAUTHORIZED inside Until Successful, the developer should put the HTTP Request inside a try scope in Unit Successful, and use On Error Continue to catch permanent errors like HTTP UNAUTHORIZED in the error handler. This way, the developer can avoid retrying requests that will always fail due to a permanent error, and reduce latency. On Error Continue allows the flow to continue processing after handling the error. Reference: https://docs.mulesoft.com/mule-runtime.3/until-successful-scope https://docs.mulesoft.com/mule-runtime.3/on-error-continue-concept

• Question 50:

  Which command is used to convert a JKS keystore to PKCS12?

  A. Keytool-importkeystore "srckeystore keystore p12-srcstoretype PKCS12 "destkeystore keystore.jks "deststoretype JKS
  B. Keytool-importkeystore "srckeystore keystore p12-srcstoretype JKS "destkeystore keystore.p12 " deststoretype PKCS12
  C. Keytool-importkeystore "srckeystore keystore jks-srcstoretype JKS "destkeystore keystore.p13 " deststoretype PKCS12
  D. Keytool-importkeystore "srckeystore keystore jks-srcstoretype PKCS12 "destkeystore keystore.p12 "deststoretype JKS
  B. Keytool-importkeystore "srckeystore keystore p12-srcstoretype JKS "destkeystore keystore.p12 " deststoretype PKCS12

  ---

  Explanation/Reference:

  To convert a JKS keystore to PKCS12, the developer needs to use the keytool-importkeystore command with the following options: -srckeystore keystore.jks -srcstoretype JKS -destkeystore keystore.p12 -deststoretype PKCS12. This

  command imports all entries from a source JKS keystore (keystore.jks) into a destination PKCS12 keystore (keystore.p12).

  Reference:

  https://docs.oracle.com/en/java/javase/tools/keytool.html#GUID-5990A2E4-78E3-47B7-AE75-6D1826259549