Refer to the exhibit.What action must be performed to log all the errors raised by the VM Connector?
Answer(s): B
To log all the errors raised by the VM Connector, the developer needs to add an async logger with the name `org.mule.extension.vm' and the level `ERROR' inside the appenders tag of the log4j2.xml file. This will enable logging all error-level events generated by the VM Connector to the console appender.
https://docs.mulesoft.com/mule-runtime/4.3/logging-in-mule#configuring- custom-logging-settings
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?
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.
https://docs.mulesoft.com/api-manager/2.x/http-caching-policy#policy-ordering
A system API that communicates to an underlying MySQL database is deploying to CloudHub. The DevOps team requires a readiness endpoint to monitor all system APIs. Which strategy should be used to implement this endpoint?
Answer(s): A
To implement a readiness endpoint to monitor all system APIs, the developer should create a dedicated endpoint that responds with the API status and reachability of the underlying systems. This way, the DevOps team can check if the system API is ready to receive requests and if it can communicate with its backend systems without errors.
https://docs.mulesoft.com/mule- runtime/4.3/deployment-strategies#readiness-probes
The HTTP Request operation raises an HTTP CONNECTIVITY error. Which HTTP status code and body are returned to the web client?
Answer(s): C
When the HTTP Request operation raises an HTTP CONNECTIVITY error, it triggers an on-error- continue handler that sets a payload with `Error in processing your request'. Since no status code is explicitly set in this handler, it defaults to 500 (INTERNAL SERVER ERROR). Therefore, the web client receives an HTTP response with status code 500 and body `Error in processing your request'.
https://docs.mulesoft.com/mule-runtime/4.3/error-handling#on-error-continue
A Mule application defines as SSL/TLS keystore properly `tis,keystore.keyPassword'' as secure. How can this property be referenced to access its value within the application?
secure::tiskeystore,keyPassowrd ShortExplanationofCorrectAnswerOnly:Toreferenceasecureproper tyvaluewithintheapplication,thedeveloperneedstousethesyntax{secure::}. In this case, the property name is tiskeystore,keyPassword, so the correct syntax is ${secure::tiskeystore,keyPassowrd}.
https://docs.mulesoft.com/mule-runtime/4.3/secure-configuration- properties#referencing-secure-properties
Post your Comments and Discuss Salesforce Salesforce-MuleSoft-Developer-II exam prep with other Community members:
Our website is free, but we have to fight against AI bots and content theft. We're sorry for the inconvenience caused by these security measures. You can access the rest of the Salesforce-MuleSoft-Developer-II content, but please register or login to continue.