Cisco
CompTIA
ISC
EC-Council
EXIN
Fortinet
ITIL
Juniper
Microsoft
VMware
Avaya
SAP
Google
NVIDIA
Salesforce
Amazon
Palo Alto Networks
ISC2
Splunk
ServiceNow
All Vendors
  2. Home
  3. Exams
  4. MuleSoft
  5. MCD-Level-2

MuleSoft MCD-Level-2 Exam
MuleSoft Certified Developer - Level 2 (Mule 4) (Page 4 )

Updated On: 1-Feb-2026
Page 2 of 13
PDF with 60 Questions

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?

  1. The HTTP Request operation will succeed if the CA'S certificate is present in the JRE's default keystore
  2. The HTTP Request operation will succeed if the CA's certificate is present in the JRE's default truststore.
  3. The HTTP Request operation will always succeed regardless of the CA
  4. The HTTP Request operation will always fail regardless of the CA

Answer(s): B

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.


Reference:

https://docs.mulesoft.com/mule-runtime/4.3/tls- configuration#tls-default



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?

  1. For nay type of queue, the message will be processed after the system comes online
  2. For persistent queues, the message will be processed after the system comes online
  3. For transient queues, the message will be processed after the system comes online
  4. For any type of queue, the message will be lost

Answer(s): B

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.


Reference:

https://docs.mulesoft.com/mule-runtime/4.3/vm- connector#persistent-queues



Refer to the exhibit.



A developer generates the base scaffolding for an API in Anypoint Studio.
Which HTTP status code is returned while testing using the API Kit console if no values are entered in client-secret?

  1. HTTP status code:200
  2. HTTP status code:403
  3. HTTP status code:400
  4. HTTP status code:500

Answer(s): B

Explanation:

Based on the code snippet and schema.json file below, when testing using the API Kit console if no values are entered in client-secret, HTTP status code 403 (FORBIDDEN) is returned. This is because client-secret is defined as a required header parameter in schema.json file, which means that it must be present in every request. If no values are entered in client-secret, then it is equivalent to omitting this header parameter, which violates the schema and causes APIKit Router to return HTTP status code 403.


Reference:

https://docs.mulesoft.com/apikit/4.x/apikit-4-headers



A company has been using CI/CD. Its developers use Maven to handle build and deployment activities.
What is the correct sequence of activities that takes place during the Maven build and deployment?

  1. Initialize, validate, compute, test, package, verify, install, deploy
  2. Validate, initialize, compile, package, test, install, verify, verify, deploy
  3. Validate, initialize, compile, test package, verify, install, deploy
  4. Validation, initialize, compile, test, package, install verify, deploy

Answer(s): C

Explanation:

The correct sequence of activities that takes place during the Maven build and deployment is validate, initialize, compile, test package, verify, install, deploy. These are Maven lifecycle phases that define a sequence of goals to execute during a build process. Each phase represents a stage in the build lifecycle and can have zero or more goals bound to it.


Reference:

https://maven.apache.org/guides/introduction/introduction-to-the-lifecycle.html



A Mule application deployed to multiple Cloudhub 2.0 replicas needs to temporarily persist large files over 10MB between flow executions, and routinely needs to query whether the file data exists on separate executions.
How can this be achieved?

  1. Store the contents of the file on separate storage, and store the key and location of the file Object using Object Store v2
  2. Use an in-memory Object Store
  3. Store the key and full contents of the file in an Object Store
  4. Store the key and full contents of the file, caching the filename and location between requests

Answer(s): A

Explanation:

To temporarily persist large files over 10MB between flow executions, and routinely query whether the file data exists on separate executions, the developer should store the contents of the file on separate storage, and store the key and location of the file object using Object Store v2. This way, the developer can avoid storing large files in memory or exceeding the size limit of Object Store v2 (10MB per object). The developer can also use Object Store v2 operations to query, retrieve, or delete the file object by its key.


Reference:

https://docs.mulesoft.com/object-store/osv2-faq#can-i- store-files-in-object-store-v2



Viewing page 4 of 13
Viewing questions 16 - 20 out of 60 questions



Post your Comments and Discuss MuleSoft MCD-Level-2 exam prep with other Community members:

Join the MCD-Level-2 Discussion