Salesforce Salesforce-MuleSoft-Developer-II Test Dumps

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 DescriptionExplanation:

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-idscope

https://docs.mulesoft.com/tracing-module/1.0/tracing-module-concepts

A.   Store the contents of the file on separate storage, and store the key and location of the file Object using Object Store v2

Answer DescriptionExplanation:

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.

References:

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

C.   The HTTP Listener generates correlation IDS unless a correlation ID is received in the HTTP request

Answer DescriptionExplanation:

When working with correlation IDs, the HTTP Listener generates correlation IDs unless a correlation ID is received in the HTTP request. In that case, it propagates the received correlation ID throughout the flow execution. Correlation IDs are used to track events across different flows or applications.

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

B.    ${secure::tiskeystore,keyPassowrd}

Answer DescriptionExplanation:

secure::tiskeystore,keyPassowrdShortExplanationofCorrectAnswerOnly:Toreferenceasecur epropertyvaluewithintheapplication,thedeveloperneedstousethesyntax{secure::}. In this case, the property name is tiskeystore,keyPassword, so the correct syntax is ${secure::tiskeystore,keyPassowrd}.

References: https://docs.mulesoft.com/muleruntime/4.3/secure-configuration-properties#referencing-secure-properties

C.   In Design Center, open the RAML and modify baseUn to include a variable that indicates the version number

Answer DescriptionExplanation:

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-ramlspecs#baseuri https://docs.mulesoft.com/api-manager/2.x/api-versioning

B.   Pass in the runtime parameter ‘’-Danpow.platform.gatekeeper=disabled’’

Answer DescriptionExplanation:

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.

References: https://docs.mulesoft.com/api-manager/2.x/api-auto-discovery-newconcept#configuring-api-autodiscovery

https://docs.mulesoft.com/mule runtime/4.3/configuring-properties

A.   Object Store v2 REST API

Answer DescriptionExplanation:

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

B.   Mutual TLS authenticates the identity of the server before the identity of the client

Answer DescriptionExplanation:

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

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

Answer DescriptionExplanation:

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-listenerref#callback

A.   If the two APIs use the same domain, the VM Connector can be leveraged

Answer DescriptionExplanation:

To communicate asynchronously between two APIs deployed to a two-node on-prem cluster, the developer can use the VM Connector if the two APIs use the same domain. The VM Connector allows passing messages between different Mule applications within a single Mule runtime instance or across different instances using shared memory or persistent storage. If two APIs are deployed under the same domain, they can share resources such as VM queues and communicate asynchronously using VM Connector operations.

References: https://docs.mulesoft.com/mule-runtime/4.3/vm-connector

https://docs.mulesoft.com/mule-runtime/4.3/shared-resources