Dec-2023 MuleSoft MCD-Level-2 Actual Questions and Braindumps
MCD-Level-2 Dumps To Pass MuleSoft Exam in 24 Hours - Pass4suresVCE
NEW QUESTION # 19
A custom policy needs to be developed to intercept all cutbound HTTP requests made by Mule applications.
Which XML element must be used to intercept outbound HTTP requests?
- A. htt-policy:operation
- B. http-policy:processor
- C. http-policy:source
- D. It is not possible to intercept outgoing HTTP requests, only inbound requests
Answer: B
Explanation:
Explanation
The http-policy:processor element is used to intercept outbound HTTP requests made by Mule applications. It allows customizing the request before it is sent to the target API and modifying the response after it is received from the target API. References:
https://docs.mulesoft.com/api-manager/2.x/policy-mule4-custom-policy#policy-xml-file
NEW QUESTION # 20
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. CloudHub REST API
- B. Object Store v2 REST API
- C. CloudHub Connector
- D. Object Store Connector
Answer: B
Explanation:
Explanation
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.
References: https://docs.mulesoft.com/object-store/osv2-apis
NEW QUESTION # 21
Which pattern should be used to invoke multiple HTTP APIs in parallel and roll back failed requests in sequence?
- A. Scatter-Gather as central Saga orchestrator for all API request with compensating actions for failing routes
- B. VM queues as a reliability pattern with error handlers to roll back any requests
- C. A database as a transactional outbox and an Until Successful router to retry any requests
- D. A Parallel for Each scope with each HTTP request wrapped in a Try scope
Answer: A
Explanation:
Explanation
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. References:
https://docs.mulesoft.com/mule-runtime/4.3/scatter-gather-concept
https://docs.mulesoft.com/mule-runtime/4.3/saga
NEW QUESTION # 22
Which configurations are required for HTTP Listener to enable mTLS authentication?
- A. Set an appropriate reconnection strategy and use persistent connections for the listener
- B. Set an appropriate truststore configuration and reconnection strategy for the listener
- C. Set an appropriate keystore configuration and use persistent connections for the listener
- D. Set an appropriate keystore and truststore configuration for the listener
Answer: D
Explanation:
Explanation
To enable mTLS authentication for HTTP Listener, the developer needs to set an appropriate keystore and truststore configuration for the listener. The keystore contains the certificate and private key of the Mule application that are used to prove its identity to clients. The truststore contains the certificates of trusted clients that are allowed to access the Mule application. References:
https://docs.mulesoft.com/mule-runtime/4.3/tls-configuration#mutual-authentication
NEW QUESTION # 23
Multiple individual Mute application need to use the Mule Maven plugin to deploy to CloudHub.
The plugin configuration should .. reused where necessary and anything project, specific should be property-based.
Where should the Mule Maven details be configured?
- A. A Bill of Materials (BOM) parent pm
- B. Pom, xml
- C. Settings, xml
- D. A parent pom.xml
Answer: D
Explanation:
Explanation
To reuse Mule Maven plugin configuration across multiple individual Mule applications, the developer should use a parent pom.xml file. A parent pom.xml file defines common configuration for one or more child projects that inherit from it. The developer can specify common properties and dependencies for all child projects in the parent pom.xml file, such as Mule Maven plugin configuration, and then reference them in each child project's pom.xml file using placeholders. References:
https://docs.mulesoft.com/mule-runtime/4.3/mmp-concept#parent-pom
https://maven.apache.org/guides/introduction/introduction-to-the-pom.html#Project_Inheritance
NEW QUESTION # 24
A Mule application includes a subflow containing a Scatter.Gather scope. Within each log of the Scatter.Gatter. an HTTP connector calls a PUT endpoint to modify records in different upstream system. The subflow is called inside an Unit successful scope to retry if a transitory exception is raised.
A technical spike is being performed to increase reliability of the Mule application.
Which steps should be performed within the Mule flow above the ensure idempontent behavior?
- A. None, the flow already exhibits idempotent behavior
- B. Ensure an error-handling flow performs corrective actions to roll back all changes if any leg of the Scatter-Gather fails
- C. Remove the Put requests from the Scatter-Getter and perform them sequentially
- D. Change the PUT requests inside the Scatter-Gather to POST requests
Answer: B
Explanation:
Explanation
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.
References: https://docs.mulesoft.com/mule-runtime/4.3/scatter-gather-concept
https://docs.mulesoft.com/mule-runtime/4.3/error-handling
NEW QUESTION # 25
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?
- A. 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
- B. In case of a cache hit, both the OAuth and HTTP Caching policies are evaluated; then the cached response is returned to the caller
- C. 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
- D. In case of a cache it, only the HTTP Caching policy is evaluating; then the cached response is returned to the caller
Answer: D
Explanation:
Explanation
When an HTTP request is received and the HTTP Caching policy is applied first, it checks if there is a cached response for that request in Object Store. If there is a cache hit, meaning that a valid cached response exists, then only the HTTP Caching policy is evaluated and the cached response is returned to the caller without invoking the OAuth policy or the API implementation. If there is a cache miss, meaning that no valid cached response exists, then both the HTTP Caching policy and the OAuth policy are evaluated before invoking the API implementation. References:
https://docs.mulesoft.com/api-manager/2.x/http-caching-policy#policy-ordering
NEW QUESTION # 26
The flow is invoicing a target API. The API's protocol is HTTPS. The TLS configuration in the HTTP Request Configuration global element is set to None. A web client submits a request to
http:localhost:8081/vehicles.
If the certificate of the target API is signed by a certificate authority (CA), what is true about the HTTP Request operation when the flow executes?
- A. The HTTP Request operation will always fail regardless of the CA
- B. The HTTP Request operation will succeed if the CA's certificate is present in the JRE's default truststore.
- C. The HTTP Request operation will succeed if the CA'S certificate is present in the JRE's default keystore
- D. The HTTP Request operation will always succeed regardless of the CA
Answer: B
Explanation:
Explanation
The HTTP Request operation will use the default truststore of the JRE to validate the certificate of the target API. If the CA's certificate is present in the truststore, the operation will succeed. Otherwise, it will fail with a handshake exception. References: https://docs.mulesoft.com/mule-runtime/4.3/tls-configuration#tls-default
NEW QUESTION # 27
A Mule application deployed to a standardalone Mule runtime uses VM queues to publish messages to be consumed asynchronously by another flow.
In the case of a system failure, what will happen to in-flight messages in the VM queues that have been consumed?
- A. For transient queues, the message will be processed after the system comes online
- B. For persistent queues, the message will be processed after the system comes online
- C. For nay type of queue, the message will be processed after the system comes online
- D. For any type of queue, the message will be lost
Answer: B
Explanation:
Explanation
In case of a system failure, in-flight messages in persistent VM queues that have been consumed will be processed after the system comes online. This is because persistent VM queues store messages on disk and guarantee delivery even if there is a system crash or restart. Therefore, any in-flight messages that have been consumed but not processed will be recovered from disk and processed when the system is back online.
References: https://docs.mulesoft.com/mule-runtime/4.3/vm-connector#persistent-queues
NEW QUESTION # 28
A developer has created the first version of an API designed for business partners to work commodity prices.
What should developer do to allow more than one major version of the same API to be exposed by the implementation?
- A. In Design Center, open the RAML and modify each operation to include the major version number
- B. In Anypoint Studio, generate scaffolding from the RAML, and then modify the flow names generated by APIKit to include a variable with the major version number
- C. In Design Center, open the RAML and modify baseUn to include a variable that indicates the version number
- D. In Anypoint Studio, generate scaffolding from the RAML, and the modify the <http:listerner> in the generated flows to include a parameter to replace the version number
Answer: C
Explanation:
Explanation
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. References:
https://docs.mulesoft.com/api-designer/design-modify-raml-specs#baseuri
https://docs.mulesoft.com/api-manager/2.x/api-versioning
NEW QUESTION # 29
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. 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. - C. In Until Successful configuration, set the retry count to 1 for error type 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.
Answer: B
Explanation:
Explanation
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. References:
https://docs.mulesoft.com/mule-runtime/4.3/until-successful-scope
https://docs.mulesoft.com/mule-runtime/4.3/on-error-continue-concept
NEW QUESTION # 30
An API has been built to enable scheduling email provider. The front-end system does very little data entry validation, and problems have started to appear in the email that go to patients. A validate-customer'' flow is added validate the data.
What is he expected behavior of the 'validate-customer'' flow?
- A. If the email address is invalid, processing continues to see if the appointment data and customer name are also invalid
- B. If the appointment date and customer name are invalid, a
SCHEDULE:INVALID_APPOINTMENT_DATE error is raised - C. If only the email address Is invalid a VALIDATION.INVALID_EMAIL error is raised
- D. If all of the values are invalid the last validation error is
raised:SCHEDULE:INVALID_CUSTOMER_NAME
Answer: C
Explanation:
Explanation
The validate-customer flow uses an until-successful scope to validate each field of the customer data. The until-successful scope executes its processors until they succeed or exhausts the maximum number of retries.
If any processor fails, it raises an error and stops executing the remaining processors. Therefore, if only the email address is invalid, a VALIDATION.INVALID_EMAIL error is raised and the validation of appointment date and customer name is skipped. References:
https://docs.mulesoft.com/mule-runtime/4.3/until-successful-scope
NEW QUESTION # 31
A Mule API receives a JSON payload and updates the target system with the payload. The developer uses JSON schemas to ensure the data is valid.
How can the data be validation before posting to the target system?
- A. Using the DataWeave if Else condition test the values of the payload against the examples included in the schema
- B. Use a DataWeave 2.09 transform operation, and at the log of the DataWeave script, add:
%dw 2.0
Import.json-moduls - C. Add the JSON module dependency and add the validate-schema operation in the flow, configured to reference the schema
- D. Apply the JSON Schema policy in API Manager and reference the correct schema in the policy configuration
Answer: C
Explanation:
Explanation
To validate the data before posting to the target system, the developer should add the JSON module dependency and add the validate-schema operation in the flow, configured to reference the schema. The JSON module provides a validate-schema operation that validates a JSON payload against a JSON schema and throws an error if the payload is invalid. References:
https://docs.mulesoft.com/json-module/1.1/json-validate-schema
NEW QUESTION # 32
Which command is used to convert a JKS keystore to PKCS12?
- A. Keytool-importkeystore -srckeystore keystore jks-srcstoretype JKS -destkeystore keystore.p13
-deststoretype PKCS12 - B. Keytool-importkeystore -srckeystore keystore p12-srcstoretype PKCS12 -destkeystore keystore.jks
-deststoretype JKS - C. Keytool-importkeystore -srckeystore keystore jks-srcstoretype PKCS12 -destkeystore keystore.p12
-deststoretype JKS - D. Keytool-importkeystore -srckeystore keystore p12-srcstoretype JKS -destkeystore keystore.p12
-deststoretype PKCS12
Answer: D
Explanation:
Explanation
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). References:
https://docs.oracle.com/en/java/javase/11/tools/keytool.html#GUID-5990A2E4-78E3-47B7-AE75-6D182625954
NEW QUESTION # 33
In a Mule project, Flow-1 contains a flow-ref to Flow-2 depends on data from Flow-1 to execute successfully.
Which action ensures the test suites and test cases written for Flow-1 and Flow-2 will execute successfully?
- A. Use ''Before Test Case'' To collect data from Flow-1 test cases before running Flow-2 test cases
- B. Use 'After Test Case' to produce the data needed from Flow-1 test cases to pass to Flow-2 test cases
- C. Chain together the test suites and test cases for Flow-1 and Flow-2
- D. Use ''Set Event to pass the input that is needed, and keep the test cases for Flow-1 and Flow-2 independent
Answer: D
Explanation:
Explanation
To ensure the test suites and test cases written for Flow-1 and Flow-2 will execute successfully, the developer should use a Set Event processor to pass the input that is needed by Flow-2, and keep the test cases for Flow-1 and Flow-2 independent. This way, the developer can isolate the testing of each flow and avoid coupling them together. References: https://docs.mulesoft.com/munit/2.3/munit-test-flow
NEW QUESTION # 34
Which properties are mandatory on the HTTP Connector configuration in order to use the OAuth 2.0 Authorization Code grant type for authentication?
- A. External callback URL, access token URL, client ID response access token
- B. Token URL, authorization URL, client ID, client secret local callback URL
- C. External callback URL, access token URL, client ID, response refresh token
- D. External callback URL, access token URL, local authorization URL, authorization URL, client ID, client secret
Answer: B
Explanation:
Explanation
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.
References: https://docs.mulesoft.com/http-connector/1.6/http-authentication#oauth-2-0
NEW QUESTION # 35
A Mule application need to invoice an API hosted by an external system to initiate a process. The external API takes 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 completes processing?
- A. Use an HTTP Connector inside Async scope to invoice the API and wait for a response
- B. Use a Scheduler to check for a response every minute
- C. Expose an HTTP callback API in Mule and register it with the external system
- D. Use an HTTP Connector to invoke the API and wait for a response
Answer: C
Explanation:
Explanation
To get response data from the external API after it completes processing, the developer should expose an HTTP callback API in Mule and register it with the external system. This way, the external API can invoke the callback API with the response data when it is ready, instead of making the Mule application wait for a long time or poll for a response repeatedly. References:
https://docs.mulesoft.com/mule-runtime/4.3/http-listener-ref#callback
NEW QUESTION # 36
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?
- A. Access Anypoint Monitoring built-in dashboard.
Select a resource.
Locate the information under Log Manager < Raw Data. - B. Access Anypoint Monitoring's built-in dashboard. Select a resource.
Locate the information under the Connectors tab. - C. Access Anypoint Monitoring's built-in dashboard
Seclect a resource.
Create a custom dashboard to retrieve the information. - D. Change the API Implementation to capture the information in the log.
Retrieve the information from the log file.
Answer: B
Explanation:
Explanation
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. References:
https://docs.mulesoft.com/monitoring/built-in-dashboard-reference
NEW QUESTION # 37
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?
- A. Configure the application to send health data to an external system
- B. Create a health check endpoint that reuses the same port number and HTTP Listener configuration as the API itself
- C. Monitor the Payment API directly sending real customer payment data
- D. Create a health check endpoint that listens on a separate port and uses a separate HTTP Listener configuration from the API
Answer: D
Explanation:
Explanation
To test that the payment API is working in production, the developer should create a health check endpoint that listens on a separate port and uses a separate HTTP Listener configuration from the API. This way, the developer can isolate the health check endpoint from the API traffic and avoid affecting the performance or availability of the API. The health check endpoint should return a simple response that indicates the status of the API, such as OK or ERROR. References:
https://docs.mulesoft.com/api-functional-monitoring/afm-create-monitor#create-a-monitor
NEW QUESTION # 38
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 default correlation ID, Anypoint MQ will sutomatically propagate it.
- B. Use the underlying HTTP request of Anypoint MQ to set the 'X-CORRELATION_ID' header to the order ID
- C. Set a custom Anypoint MQ user property to propagate the order ID and set the correlation ID in the receiving applications.
- D. Wrap all Anypoint MQ Publish operations within a With CorrelationID scope from the Tracing module, setting the correlation ID to the order ID
Answer: D
Explanation:
Explanation
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. References:
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
NEW QUESTION # 39
A Flight Management System publishes gate change notification events whenever a flight's arrival gate changes. Other systems, including Baggage Handler System. Inflight Catering System and Passenger Notifications System, must each asynchronously receive the same gate change notification to process the event according.
Which configuration is required in Anypoint MQ to achieve this publish/subscribe model?
- A. Publish each client subscribe directly to the exchange.
Have each client subscribe directly to the queue. - B. Publish the gate change notification to an Anypoint MQ exchanhe.
Create different Anypoint MQ queues meant for each of the other subscribing systems.
Bind the exchange with each of the queues. - C. Publish the gate change notification to an Anypoint MC queue
Have each client subscribe directly to the queue - D. Publish the gate change notification to an Anypoint MQ queue.
Create different anypoint MQ exchange meant for each of the other subscribing systems Bind the queue with each of the exchanges
Answer: B
Explanation:
Explanation
To achieve a publish/subscribe model using Anypoint MQ, where each system receives the same gate change notification event, the developer should publish the gate change notification to an Anypoint MQ exchange, create different Anypoint MQ queues meant for each of the other subscribing systems, and bind the exchange with each of the queues. An exchange is a message routing agent that can send messages to different queues based on predefined criteria. By binding an exchange with multiple queues, each queue receives a copy of every message sent to that exchange. Therefore, each system can subscribe to its own queue and receive every gate change notification event. References:
https://docs.mulesoft.com/anypoint-mq/3.x/anypoint-mq-exchanges
NEW QUESTION # 40
Which statement is true about using mutual TLS to secure an application?
- A. Mutual TLS requires a hardware security module to be used
- B. Mutual TLS increases the encryption strength versus server-side TLS alone
- C. Mutual TLS authenticates the identity of the server before the identity of the client
- D. Mutual TLS ensures only authorized end users are allowed to access an endpoint
Answer: C
Explanation:
Explanation
Mutual TLS (mTLS) is an extension of TLS that requires both parties (client and server) to present their certificates to each other during the handshake process. This way, both parties can verify each other's identity and establish a secure connection. The authentication of the server happens before the authentication of the client, as the server sends its certificate first and then requests the client's certificate. References:
https://docs.mulesoft.com/mule-runtime/4.3/tls-configuration#mutual-authentication
NEW QUESTION # 41
Which statement is true when using XML SDK for creating custom message processors?
- A. All operations are public
- B. An XML SDK provides both inbound and outbound operations
- C. Operations can be reused in recursive calls
- D. Properties are fields defined by an end user of the XML SDK component and serve as a global configuration for the entire Mule project in which they are used
Answer: A
Explanation:
Explanation
When using XML SDK for creating custom message processors, all operations are public by default and can be used by any Mule application that imports them. There is no way to make an operation private or protected in XML SDK. References: https://docs.mulesoft.com/mule-sdk/1.1/xml-sdk#operations
NEW QUESTION # 42
......
Download the Latest MCD-Level-2 Dump - 2023 MCD-Level-2 Exam Question Bank: https://www.pass4suresvce.com/MCD-Level-2-pass4sure-vce-dumps.html