Pass the Salesforce Salesforce MuleSoft Salesforce-MuleSoft-Developer-II Questions and answers with CertsForce

To develop an API that retrieves data from a hospital system using reusable Java libraries, thedeveloper should install libraries in a local repository and refer to it in the pom.xml file. This way, the developer can use Maven to manage dependencies and invoke Java code from Mule applications using Java Module operations. References: https://docs.m ulesoft.com/mule-runtime/4.3/java-module-reference#add-the-java-module-to-your-projecthttps://docs.mulesoft.com/mule-runtime/4.3/java-module-reference#invok e-java-code

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 keyand 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-in-object-store-v2

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 parameterin 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. References:https://docs.mulesoft.com/apikit/4.x/apikit-4-headers

To configurea common-global-handler flow that can be reused across all of the organization’s deployed applications, the developer should create a Mule Plugin project, create a common-global-error-handler flow inside the plugin project, and use this plugin as a dependency in all Mule applications. This way, the developer can import the common-global-error-handler flow in any application that needs it and avoid duplicating the error handling logic. References:https://docs.mulesoft.com/mule-runtime/4.3/error-handling#global-error-handler

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 alsosupports custom invalidation strategies using MEL or DataWeave expressions. References:https://docs.mulesoft.com/mule-runtime/4.3/cache-scope#cache_invalidation

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. References: https://docs.mulesoft.com/mule-runtime/4.3/about-mule-message#mess age-attributes

secure::tiskeystore,keyPassowrd∗∗ShortExplanationofCorrectAnswerOnly:Toreferenceasecurepropertyvaluewithintheapplication,thedeveloperneedstousethesyntax{secure::}. In this case, the property name is tiskeystore,keyPassword, so the correct syntax is ${secure::tiskeystore,keyPassowrd}.References: https://docs .mulesoft.com/mule-runtime/4.3/secure-configuration-properties#referencing-secure-properties

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

To configure API Functional Monitoring to monitor the health of 10 public APIs periodically while minimizing operational overhead and cost, the developer should use one public locationwith all 10 APIs in a single schedule. A public location is a worker that runs in a CloudHub shared environment, which is cheaper and easier to maintain than a private location. A single schedule allows running all 10 APIs tests at the same time and frequency, which reduces complexity and resource consumption. References:https://docs.mulesoft.com/functional-monitoring/fm-create-monitor#create-a-monitor

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 implementationwith 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-new-concept#configuring-api-autodiscovery https://docs.mulesoft.com/mule-runtime/4.3/configuring-properties