Salesforce-MuleSoft-Developer-II Exam Practice Test Instant Access

Question 1

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?

ADownload the common application from Naxus and copy it to the src/main/resources folder in the API

BCopy the common application's source XML file and out it in a new flow file in the src/main/mule folder

CAdd a Maven dependency in the PCM file with multiple-plugin as <classifier>

DAdd a Maven dependency in the POM file with jar as <classifier>

Answer : D

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 <classifier>. 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. Reference: https://docs.mulesoft.com/mule-runtime/4.3/mmp-concept#add-a-maven-dependency-to-the-pom-file

Question 2

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?

AUse the underlying HTTP request of Anypoint MQ to set the 'X-CORRELATION_ID' header to the order ID

BSet a custom Anypoint MQ user property to propagate the order ID and set the correlation ID in the receiving applications.

CUse the default correlation ID, Anypoint MQ will sutomatically propagate it.

DWrap all Anypoint MQ Publish operations within a With CorrelationID scope from the Tracing module, setting the correlation ID to the order ID

Answer : D

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

Question 3

A company deploys 10 public APIs to CloudHub. Each API has its individual health endpoint defined. The platform operation team wants to configure API Functional Monitoring to monitor the health of the APIs periodically while minimizing operational overhead and cost.

How should API Functional Monitoring be configured?

AFrom one public location with each API in its own schedule

BFrom one private location with all 10 APIs in a single schedule

CFrom one public location with all 10 APIs in a single schedule

DFrom 10 public locations with each API in its own schedule

Answer : C

To configure API Functional Monitoring to monitor the health of 10 public APIs periodically while minimizing operational overhead and cost, the developer should use one public location with all 10 APIs in a single schedule. A public location is a worker that runs in a CloudHub shared environment, which is cheaper and easier to maintain than a private location. A single schedule allows running all 10 APIs tests at the same time and frequency, which reduces complexity and resource consumption. Reference: https://docs.mulesoft.com/functional-monitoring/fm-create-monitor#create-a-monitor

Question 4

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?

AConfigure retrying until a MULERETRY_EXHAUSTED error is raised or the API responds back with a successful response.

BIn Until Successful configuration, set the retry count to 1 for error type HTTP: UNAUTHORIZED.

CPut 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.

DPut 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.

Answer : C

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/4.3/until-successful-scope https://docs.mulesoft.com/mule-runtime/4.3/on-error-continue-concept

Question 5

Refer to the exhibits.

Bioinfo System API is implemented and published to Anypoint Exchange. A developer wants to invoke this API using its REST Connector.

What should be added to the POM?