Salesforce SALESFORCE-MULESOFT-DEVELOPER-II Online Practice Questions and Exam Preparation

Salesforce SALESFORCE-MULESOFT-DEVELOPER-II Online Questions & Answers

• Question 1:

  A company with MuleSoft Titanium develops a Salesforce System API using MuleSoft out-of-the-box Salesforce Connector and deploys the API to CloudHub. Which steps provide the average number of requests and average response time of the Salesforce Connector?

  A. Access Anypoint Monitoring's built-in dashboard. Select a resource. Locate the information under the Connectors tab.
  B. Access Anypoint Monitoring's built-in dashboard Seclect a resource. Create a custom dashboard to retrieve the information.
  C. Access Anypoint Monitoring built-in dashboard. Select a resource. Locate the information under Log Manager < Raw Data.
  D. Change the API Implementation to capture the information in the log. Retrieve the information from the log file.
  A. Access Anypoint Monitoring's built-in dashboard. Select a resource. Locate the information under the Connectors tab.

  ---

  Explanation/Reference:

  To get the average number of requests and average response time of the Salesforce Connector, the developer should access Anypoint Monitoring's built-in dashboard, select a resource (such as an application or an API), and locate the information under the Connectors tab. The Connectors tab shows metrics for each connector used by the resource, such as average requests per minute, average response time, and failures. https:// docs.mulesoft.com/monitoring/built-indashboard-reference

• Question 2:

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

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

  ---

  Explanation/Reference:

  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. https:// docs.mulesoft.com/mule-runtime.3/tls-configuration#mutualauthentication

• Question 3:

  Refer to the exhibit.

  

  What action must be performed to log all the errors raised by the VM Connector?

  A. Add
  B. Add
  C. Configure
  D. Nothing, as error-level events are automatically logged
  B. Add

  ---

  Explanation/Reference:

  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.3/logging-in-mule#configuringcustom-logging-settings

• Question 4:

  Multiple individual Mute application need to use the Mule Maven plugin to deploy to CloudHub. The plugin configuration should .. reused where necessary and anything project, specific should be property-based. Where should the Mule Maven details be configured?

  A. A parent pom.xml
  B. Settings, xml
  C. Pom, xml
  D. A Bill of Materials (BOM) parent pm
  A. A parent pom.xml

  ---

  Explanation/Reference:

  To reuse Mule Maven plugin configuration across multiple individual Mule applications, the developer should use a parent pom.xml file. A parent pom.xml file defines common configuration for one or more child projects that inherit from it. The developer can specify common properties and dependencies for all child projects in the parent pom.xml file, such as Mule Maven plugin configuration, and then reference them in each child project's pom.xml file using placeholders. https://docs.mulesoft.com/mule-runtime.3/mmp-concept#parent-pom https://maven.apache.org/guides/introduction/introduction-to-the-pom.html#Project_Inheritance

• Question 5:

  Bioinfo System API is implemented and published to Anypoint Exchange. A developer wants to invoke this API using its REST Connector. What should be added to the POM?

  

  A. Option A
  B. Option B
  C. Option C
  D. Option D
  E. Option E
  E. Option E

  ---

  Explanation/Reference:

  To invoke Bioinfo System API using its REST Connector, option E should be added to the pom.xml file.

  This option adds a dependency for Bioinfo System API REST Connector with its group ID, artifact ID, version, classifier, and type. The classifier specifies that it is a REST Connector (raml-client), and the type specifies that it is a Mule plugin

  (mule-plugin).

  Reference:

  https://docs.mulesoft.com/apikit.x/apikit-4-generate-from-rest-api-task#add-the-api-dependencyto-the-pom-file

• Question 6:

  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?

  A. For nay type of queue, the message will be processed after the system comes online
  B. For persistent queues, the message will be processed after the system comes online
  C. For transient queues, the message will be processed after the system comes online
  D. For any type of queue, the message will be lost
  B. For persistent queues, the message will be processed after the system comes online

  ---

  Explanation/Reference:

  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. https://docs.mulesoft.com/mule-runtime.3/vmconnector#persistent-queues

• Question 7:

  Refer to the exhibit.

  

  Based on the code snippet, schema,json file, and payload below, what is the outcome of the given

  code snippet when a request is sent with the payload?

  A. The Mule flow will execute successfully with status code 200, and the response will be the JSON sent in request
  B. The Mule flow will execute successfully with status code 204
  C. The Mule flow will throw the exception "JSON:SCHEMA_NOT_HONOURED
  D. The Mule flow will execute successfully with status code 200m and a response will display the message " Age in years which must equal to or greater than zero.''
  C. The Mule flow will throw the exception "JSON:SCHEMA_NOT_HONOURED

  ---

  Explanation/Reference:

  Based on the code snippet, schema.json file, and payload below, the outcome of the given code snippet when a request is sent with the payload is that the Mule flow will throw the exception "JSON:SCHEMA_NOT_HONOURED'. This is because the payload does not conform to the schema.json file, which specifies that age must be a number greater than or equal to zero. The payload has age as a string with a negative value, which violates the schema. Therefore, the validate-schema operation throws an error with type "JSON:SCHEMA_NOT_HONOURED'. Reference: https://docs.mulesoft.com/json-module.1/json-validate-schema

• Question 8:

  The HTTP Request operation raises an HTTP CONNECTIVITY error.

  Which HTTP status code and body are returned to the web client?

  A. HTTP Status Code:200. Body "Error in processing your request
  B. HTTP Status Code:500. Body "The HTTP CONNECTIVITY Error description
  C. HTTP Status Code:500. Body "Error in processing your request
  D. HTTP Status Code:500. Body "Error in processing your request
  C. HTTP Status Code:500. Body "Error in processing your request

  ---

  Explanation/Reference:

  When the HTTP Request operation raises an HTTP CONNECTIVITY error, it triggers an on-errorcontinue 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.3/error-handling#on-error-continue

• Question 9:

  A Mule API receives a JSON payload and updates the target system with the payload. The developer uses JSON schemas to ensure the data is valid. How can the data be validation before posting to the target system?

  A. Use a DataWeave 2.09 transform operation, and at the log of the DataWeave script, add: %dw 2.0 Import.json-moduls
  B. Using the DataWeave if Else condition test the values of the payload against the examples included in the schema
  C. Apply the JSON Schema policy in API Manager and reference the correct schema in the policy configuration
  D. Add the JSON module dependency and add the validate-schema operation in the flow, configured to reference the schema
  D. Add the JSON module dependency and add the validate-schema operation in the flow, configured to reference the schema

  ---

  Explanation/Reference:

  To validate the data before posting to the target system, the developer should add the JSON module dependency and add the validate-schema operation in the flow, configured to reference the schema. The JSON module provides a validate-schema operation that validates a JSON payload against a JSON schema and throws an error if the payload is invalid. https://docs.mulesoft.com/jsonmodule/1.1/json-validate-schema

• Question 10:

  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?

  A. In case of a cache hit, both the OAuth and HTTP Caching policies are evaluated; then the cached response is returned to the caller
  B. In case of a cache it, only the HTTP Caching policy is evaluating; then the cached response is returned to the caller
  C. In case of a cache miss, only the HTTP Caching policy is evaluated; then the API retrieves the data from the API implementation, and the policy stores the data to be cached in Object Store
  D. In case of a cache miss, both the OAuth and HTTP Caching policies are evaluated; then the API retrieves the data from the API implementation, and the policy does not store the data in Object Store
  B. In case of a cache it, only the HTTP Caching policy is evaluating; then the cached response is returned to the caller

  ---

  Explanation/Reference:

  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. Reference: https://docs.mulesoft.com/api-manager.x/http-caching-policy#policy-ordering