Question 1

A company with MuleSoft Titanium develops a Salesforce System API using MuleSoft out-of-the-box Salesforce Connector and deploys the API to CloudHub.

Which steps provide the average number of requests and average response time of the Salesforce Connector?

AAccess Anypoint Monitoring's built-in dashboard. Select a resource.
Locate the information under the Connectors tab.

BAccess Anypoint Monitoring's built-in dashboard
Seclect a resource.
Create a custom dashboard to retrieve the information.

CAccess Anypoint Monitoring built-in dashboard.
Select a resource.
Locate the information under Log Manager < Raw Data.

DChange the API Implementation to capture the information in the log.
Retrieve the information from the log file.

Answer : A

To get the average number of requests and average response time of the Salesforce Connector, the developer should access Anypoint Monitoring's built-in dashboard, select a resource (such as an application or an API), and locate the information under the Connectors tab. The Connectors tab shows metrics for each connector used by the resource, such as average requests per minute, average response time, and failures. Reference: https://docs.mulesoft.com/monitoring/built-in-dashboard-reference

Question 2

A Mule application contain two policies Policy A and Policy A has order1, and Policy B has order 2. Policy A Policy B, and a flow are defined by he configuration below.

When a HTTP request arrives at the Mule application's endpoint, what will be the execution order?

AA1, B1, F1, B2, A2

BB1, A1, F1, A2, B2

CF1, A1, B1, B2, A2

DF1, B1, A1, A2, B2

Answer : A

Based on the configuration below, when a HTTP request arrives at the Mule application's endpoint, the execution order will be A1, B1, F1, B2, A2. This is because policies are executed before and after the API implementation flow according to their order attribute. Policy A has order 1, which means it is executed first before Policy B, which has order 2. The flow is executed after both policies are executed before the flow. Then, Policy B is executed after the flow before Policy A is executed after the flow. Reference: https://docs.mulesoft.com/api-manager/2.x/policies-policy-order

Question 3

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?

AUse flow variables within every logger processor to log the order ID

BSet a flow variable and edit the log4/2.xml file to output the variable as part of the message pattern

CCreate a custom XML SDK component to wrap the logger processor and automatically add the order ID within the connector

DUse the Tracing module to set logging variables with a Mapped Diagnostic Context

Answer : D

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

Question 4

Refer to the exhibit.

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

AThe HTTP Listener will trust any certificate presented by the HTTP client

BThe HTTP Lister will accept any unauthenticated request

CThe HTTP listener will only accept HTTP requests

DMutual TLS authentication will be enabled between this HTTP Listener and an HTTP client

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

Question 5

An API has been developed and deployed to CloudHub Among the policies applied to this API is an allowlist of IP addresses. A developer wants to run a test in Anypoint Studio and does not want any policies applied because their workstation is not included in the allowlist.

What must the developer do in order to run this test locally without the policies applied?

ACreate a properties file specifically for local development and set the API instance ID to a value that is not used in API Manager

BPass in the runtime parameter ''-Danpow.platform.gatekeeper=disabled''

CDeactivate the API in API Manager so the Autodiscovery element will not find the application when it runs in Studio

DRun the test as-s, with no changes because the Studio runtime will not attempt to connect to API Manager

Answer : A

To run a test locally without the policies applied, the developer should create a properties file specifically for local development and set the API instance ID to a value that is not used in API Manager. This way, the developer can use different configuration properties for different environments and avoid triggering API autodiscovery when running tests locally. API autodiscovery is a mechanism that associates an API implementation with its corresponding API specification and policies in API Manager based on its API instance ID. By setting this ID to a value that does not exist in API Manager, the developer can prevent API autodiscovery from finding and applying any policies to the local test. Reference: https://docs.mulesoft.com/api-manager/2.x/api-auto-discovery-new-concept#configuring-api-autodiscovery https://docs.mulesoft.com/mule-runtime/4.3/configuring-properties

Free MCD-Level-2 Questions for MuleSoft MCD-Level-2 Exam as PDF & Practice Test Software

Question 1

Question 2

Question 3

Question 4

Question 5