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

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

• Question 21:

  An organization is beginning to follow Mulesoft's recommended API led connectivity approach to use modern API to support the development and lifecycle of the integration solutions and to close the IT delivery gap. What distinguishes between how modern API's are organized in a MuleSoft recommended API-led connectivity approach as compared to other common enterprise integration solutions?

  A. The API interfaces are specified as macroservices with one API representing all the business logic of an existing and proven end to end solution
  B. The API interfaces are specified at a granularity intended for developers to consume specific aspect of integration processes
  C. The API implementation are built with standards using common lifecycle and centralized configuration management tools
  D. The APIO implementations are monitored with common tools, centralized monitoring and security systems
  B. The API interfaces are specified at a granularity intended for developers to consume specific aspect of integration processes

  ---

  Explanation

• Question 22:

  Refer to the exhibits.

  

  A web client submits a request to http://localhQst:8081. What is the structure of the payload at the end of the flow?

  

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

  ---

  Explanation

  The Scatter-Gather component is a routing event processor that processes a Mule event through different parallel processing routes that contain different event processors. Each route receives a reference to the Mule event and executes a sequence of one or more event processors. Each of these routes uses a separate thread to execute the event processors, and the resulting Mule event can be either the same Mule event without modifications or a new Mule event with its own payload, attributes, and variables. The Scatter-Gather component then combines the Mule events returned by each processing route into a new Mule event that is passed to the next event processor only after every route completes successfully. The Scatter-Gather component executes each route in parallel, not sequentially. Parallel execution of routes can greatly increase the efficiency of your Mule application and may provide more information than sequential processing. Mule Ref Doc : https://docs.mulesoft.com/mule-runtime/4.3/scatter-gather-concept

• Question 23:

  An HTTP Request operation sends an HTTP request with a non-empty JSON object payload to an external HTTP endpoint. The response from the external HTTP endpoint returns an XML body. The result is stored in a target named the Result.

  What is the payload at the event processor after the HTTP Request?

  A. The XML response body
  B. null
  C. The original JSON request body
  D. A non-empty Java object
  C. The original JSON request body

  ---

  Explanation

• Question 24:

  Refer to the exhibit.

  

  The main flow contains a Flow Reference for the child flow.

  What values are accessible in the child flow after a web client submits a request to http://localhost:8Q81/order? color=red?

  A. payload
  B. payload quantity var
  C. payload color query param
  D. payload quantity var color query param
  D. payload quantity var color query param

  ---

  Explanation

  Flow Reference Component Flow Reference routes the Mule event to another flow or subflow, executes all processors in the referenced flow, and then routes the event back within the same Mule application. The following diagram shows the order of processing when one flow references another:

  

  When the main flow is triggered, the Mule event travels through and executes the flow until the event reaches the Flow Reference. The event then travels through and executes the referenced flow from beginning to end, and then returns to the main flow. This process enables you to treat the entire referenced flow like a single component in your current flow. Mule Ref Doc : https://docs.mulesoft.com/mule-runtime/4.3/flowref-about Correct answer is payload quantity var color query param

• Question 25:

  A function named newProdCode needs to be defined that accepts two input parameters, an integer value for itemID and a string value for productCategory, and returns a new product code.

  What is the correct DataWeave code to define the newProdCode function?

  A. fun newProdCode{itemID: Number, productCategory: String) --> "PC-" ++ productCategory ++ (itemID as String)
  B. fun newProdCode(itemID: Number, productCategory: String) = "PC-" ++ productCategory ++ (itemID as String)
  C. function newProdCode(itemID: Number, productCategory: String) = "PC-" ++ productCategory ++ (itemID as String)
  D. var newProdCode(itemID: Number, productCategory: String) -> "PC-" ++ productCategory ++ (itemID as String)
  B. fun newProdCode(itemID: Number, productCategory: String) = "PC-" ++ productCategory ++ (itemID as String)

  ---

  Explanation

• Question 26:

  Refer to the exhibits.

  As a mulesoft developer, what you would change in Database connector configuration to resolve this error?

  

  

  A. Configure the correct host URL
  B. Configure the correct database name
  C. Configure the correct table name
  D. Configure the correct JDBC driver
  D. Configure the correct JDBC driver

  ---

  Explanation

  Correct answer is Configure the correct JDBC driver as error message suggests the same Caused by: java.sql.SQLException: Error trying to load driver:

  com.mysql.jdbc.Driver : Cannot load class 'com.mysql.jdbc.Driver': [ Class 'com.mysql.jdbc.Driver' has no package mapping for region 'domain/default/app/mule_app'., Cannot load class 'com.mysql.jdbc.Driver': [

• Question 27:

  Refer to the exhibits. What payload is logged at the end of the main flow?

  

  A. [order1, order2, order3, order4]
  B. [1, 2, 3, 4]
  C. order4
  D. order1order2order3order4
  B. [1, 2, 3, 4]

  ---

  Explanation

  The For Each scope splits a payload into elements and processes them one by one through the components that you place in the scope. It is similar to a for-each/for loop code block in most programming languages and can process any

  collection, including lists and arrays. The collection can be any supported content type, such as application/json, application/java, or application/xml.

  General considerations about the For Each scope:

  By default, For Each tries to split the payload. If the payload is a simple Java collection, the For Each scope can split it without any configuration. The payload inside the For Each scope is each of the split elements. Attributes within the

  original message are ignored because they are related to the entire message.

  For Each does not modify the current payload. The output payload is the same as the input.

  Mule Doc Reference : https://docs.mulesoft.com/mule-runtime/4.3/for-each-scope-concept

• Question 28:

  What MuleSoft API-led connectivity layer is intended to expose part of a backend database without business logic?

  A. Data layer
  B. Process layer
  C. Experience layer
  D. System layer
  D. System layer

  ---

  Explanation

  System APIs provide a means for insulating the data consumers from the complexity or changes to the underlying backend systems. MuleSoft recommends three-layered approach to API-led connectivity, highlighting the three layers:

  *

  System APIs

  *

  Process APIs

  *

  Experience APIs System APIs are the core systems of record underlying core systems of record (e.g. ERPs, key customer and billing systems, databases, etc.). Process APIs allow you to define a common process which the organization can share, and these APIs perform specific functions, provide access to non-central data, and may be built by either Central IT or Line of Business IT. And finally, the Experience APIs are the means by which data can be reconfigured so that it is most easily consumed by its intended audience, all from a common data source.

  The three-layered structure allows for a seamless flow of data from systems of record to new experiences, and allows for reusability of assets rather than point to point connections. This approach provides a distributed and tailored approach to architecture, greater flexibility through loose coupling, and deeper operational visibility into what is being built.

  

• Question 29:

  Refer to the exhibits.

  

  The Batch Job scope processes the array of strings

  After the Batch Job scope completes processing the input payload what information is logged by the Logger component?

  

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

  ---

  Explanation

• Question 30:

  Does a root element required when creating a XML response using Dataweave?

  A. Depends on requirement
  B. Not required
  C. Always required
  D. None of these
  C. Always required

  ---

  Explanation

  Root element is always required while creating XML response in DataWeave transformation