Question 1

A developer deploys an API to CloudHub and applies an OAuth policy on API Manager. During testing, the

API response is slow, so the developer reconfigures the API so that the out-of-the-box HTTP Caching policy

is applied first, and the OAuth API policy is applied second.

What will happen when an HTTP request is received?

Options :

A :

In case of a cache hit, both the OAuth and HTTP Caching policies are evaluated; then the cached

response is returned to the caller

B :

In case of a cache it, only the HTTP Caching policy is evaluating; then the cached response is returned

to the caller

C :

In case of a cache miss, only the HTTP Caching policy is evaluated; then the API retrieves the data from

the API implementation, and the policy stores the data to be cached in Object Store

D :

In case of a cache miss, both the OAuth and HTTP Caching policies are evaluated; then the API

retrieves the data from the API implementation, and the policy does not store the data in Object Store

Answer: B

Question 2

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.

Answer: C

Question 3

A mule application exposes and API for creating payments. An Operations team wants to ensure that the Payment API is up and running at all times in production. Which approach should be used to test that the payment API is working in production?

Options :

A : Create a health check endpoint that listens on a separate port and uses a separate HTTP Listener configuration from the API

B : Configure the application to send health data to an external system

C : Create a health check endpoint that reuses the same port number and HTTP Listener configuration as the API itself

D : Monitor the Payment API directly sending real customer payment data

Answer: A

Question 4

When implementing a synchronous API where the event source is an HTTP Listener, a developer needs to

return the same correlation ID back to the caller in the HTTP response header.

How can this be achieved?

Options :

A : Enable the auto-generate CorrelationID option when scaffolding the flow

B : Enable the CorrelationID checkbox in the HTTP Listener configuration

C : Configure a custom correlation policy

D : NO action is needed as the correlation ID is returned to the caller in the response header by default

Answer: D

Question 5

A Mule application need to invoice an API hosted by an external system to initiate a process. The external APItakes anywhere between one minute and 24 hours to compute its process.Which implementation should be used to get response data from the external API after it completesprocessing?

Options :

A : Use an HTTP Connector to invoke the API and wait for a response

B : Use a Scheduler to check for a response every minute

C : Use an HTTP Connector inside Async scope to invoice the API and wait for a response

D : Expose an HTTP callback API in Mule and register it with the external system

Answer: D

Free DEX660 Mock Exam – Practice Online Confidently

Buying Options: