Refer to exhibits.In the execution of the Scatter-Gather , the flow route completes after 10 seconds and the flow2 route completes in 40 seconds. How many seconds does it take for the Scatter-Gather to complete?
Answer(s): C
Scatter-Gather sends the event to each routes concurrently. Hence both route in this example will start in parallel. So total time to complete processing is 40 seconds 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.
https://docs.mulesoft.com/mule-runtime/4.3/scatter-gather-concept
A Utlility.dwl is located in a Mule project at src/main/resources/modules. The Utility.dwl file defines a function named encryptString that encrypts a String What is the correct DataWeave to call the encryptString function in a Transform Message component?
Answer(s): B
Correct answer is%dw 2.0output application/json import modules::Utility---Utility::encryptString( "John Smith" )DataWeave 2.0 functions are packaged in modules. Before you begin, note that DataWeave 2.0 is for Mule 4 apps. For Mule 3 apps, refer to DataWeave Operators in the Mule 3.9 documentation. For other Mule versions, you can use the version selector for the Mule Runtime table of contents. Functions in the Core (dw::Core) module are imported automatically into your DataWeave scripts. To use other modules, you need to import the module or functions you want to use by adding the import directive to the head of your DataWeave script, for example:import dw::core::Strings import camelize, capitalize from dw::core::Strings import * from dw::core::StringsThe way you import a module impacts the way you need to call its functions from a DataWeave script. If the directive does not list specific functions to import or use * from to import all functions from a function module, you need to specify the module when you call the function from your script. For example, this import directive does not identify any functions to import from the String module, so it calls the pluralize function like this: Strings::pluralize("box").Transform%dw 2.0import dw::core::Strings output application/json---{ 'plural': Strings::pluralize("box") }
A mule project contains MySQL database dependency . The project is exported from Anypoint Studio so that it can be deployed to Cloudhub. What export options needs to be selected to create the smallest deployable archive that will successfully deploy to Cloudhub?
You can choose Attach Project Sources to include metadata that Studio requires to reimport the deployable file as an open Mule project into your workspace. You must keep the Attach Project Sources option selected to be able to import the packaged JAR file back into a Studio workspace. But requirement here is to create smallest deployable archive that will successfully deploy to Cloudhub.Hence we can ignore this option.We need to select Include project module and dependencies As actual modules and external dependencies required to run the Mule application in a Mule runtime engineHence correct answer isSelect only below option 2) Include project module and dependencies Reference:https://docs.mulesoft.com/studio/7.5/import-export-packages#exporting-a- studio-project-to-a-deployable-mule-application
What should this endpoint return? http://dev.acme.com/api/patients?name=John&surname=Bell
Answer(s): D
Query parameters are a defined set of parameters attached to the end of a url. They are extensions of the URL that are used to help define specific content or actions based on the data being passed. To append query params to the end of a URL, a `?' Is added followed immediately by a query parameter. To add multiple parameters, an `&' is added in between each. Hence coming back to question, endpoint would return Patients with name as John and (and is very important here) surname as Bell
There are three routes configured for Scatter-Gather and incoming event has a payload is an Array of three objects. How routing will take place in this scenario?
Entire event would be sent to each route in parallel.Scatter-Gather works as follows :- The Scatter-Gather component receives a Mule event and sends a reference of this Mule event to each processing route.- Each of the processing routes starts executing in parallel. After all processors inside a route finish processing, the route returns a Mule event, which can be either the same Mule event without modifications or a new Mule event created by the processors in the route as a result of the modifications applied.- After all processing routes have finished execution, the Scatter-Gather component creates a new Mule event that combines all resulting Mule events from each route, and then passes the new Mule event to the next component in the flow.
Post your Comments and Discuss Salesforce Salesforce-MuleSoft-Developer-I 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-I content, but please register or login to continue.