Free MCD-Level-2 Exam Braindumps (page: 2)

Page 2 of 16

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?

  1. Enable the auto-generate CorrelationID option when scaffolding the flow
  2. Enable the CorrelationID checkbox in the HTTP Listener configuration
  3. Configure a custom correlation policy
  4. NO action is needed as the correlation ID is returned to the caller in the response header by default

Answer(s): D

Explanation:

When implementing a synchronous API where the event source is an HTTP Listener, Mule automatically propagates some message attributes between flows via outbound and inbound properties. One of these attributes is correlation ID, which is returned to the caller in the response header by default as MULE_CORRELATION_ID.


Reference:

https://docs.mulesoft.com/mule- runtime/4.3/about-mule-message#message-attributes



Which statement is true about using mutual TLS to secure an application?

  1. Mutual TLS requires a hardware security module to be used
  2. Mutual TLS authenticates the identity of the server before the identity of the client
  3. Mutual TLS ensures only authorized end users are allowed to access an endpoint
  4. Mutual TLS increases the encryption strength versus server-side TLS alone

Answer(s): B

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.


Reference:

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



Which statement is true when using XML SDK for creating custom message processors?

  1. 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
  2. An XML SDK provides both inbound and outbound operations
  3. Operations can be reused in recursive calls
  4. All operations are public

Answer(s): D

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.


Reference:

https://docs.mulesoft.com/mule-sdk/1.1/xml- sdk#operations



Which type of cache invalidation does the Cache scope support without having to write any additional code?

  1. Write-through invalidation
  2. White-behind invalidation
  3. Time to live
  4. Notification-based invalidation

Answer(s): C

Explanation:

The Cache scope supports time to live (TTL) as a cache invalidation strategy without having to write any additional code. TTL specifies how long the cached response is valid before it expires and needs to be refreshed. The Cache scope also supports custom invalidation strategies using MEL or DataWeave expressions.


Reference:

https://docs.mulesoft.com/mule-runtime/4.3/cache- scope#cache_invalidation



Page 2 of 16



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

Anonymous commented on November 10, 2024
Good ONE FOR mcd l2
INDIA
upvote

RM commented on October 30, 2024
Thank you for the dumps
Anonymous
upvote

Champ commented on September 26, 2024
Good to see that something is still free. I truly appreciate this service.
Mexico
upvote