MuleSoft Developer Exam 2024 Questions and Answers | 100% Correct !!

MuleSoft Developer Exam 2024 Questions and Answers | 100% Correct !! When do variables persist? -Answer-Variables persist through all flows unless the event crosses a transport boundary (e.g. making a http request to another flow) T/F: Subflows can have their own error handling strategy -Answer-False Syntax to fetch a variable -Answer-#[] What persists when calling from a parent flow to another flow via http request? -Answer- Not variables API Interface definition file (API Specification) -Answer-defines what you call, what you send it, and what you get back A Web Service -Answer-The Actual API implementation you can make calls to or interface of that API implementation An API Proxy -Answer-An application that controls access to the web service, restricting access, and usage through an API gateway What persists when calling from a parent flow to another flow via flow reference? - Answer-Variables JMS connector -Answer-connector capable of sending and receiving messages to and from topics and queues JMS Publish -Answer-Operation that allows the user to send a message to a JMS Destination JMS Publish - Consume -Answer-Operation that allows the user to send a message to a JMS Destination and waits for response either to the provided replyTo destination or to a dynamically created Language for Choice Decisions -Answer-dataweave #[ != 0] Execution order of functions -Answer-the last function in the chain is executed first Calling flows from a DW Expression -Answer-use the lookup function {a: lookup("myFlow",{b:"Hello"})} How to import a function in a module -Answer-import dasherize from dw::core::Strings How to import a module -Answer-import dw::core::Strings You can call subflows from a dataweave expressions -Answer-false map -Answer-Iterates over items in an array and outputs the results into a new array. Scatter gather output -Answer-returns a collection of all results, collection is an object of objects each object contains attributes and payload validation module -Answer-can use to check whether something has or not been met and you can halt the flow if that condition has not been met Mule defualt error handler -Answer-used if no error handler defined implicitly and globally handles all messaging errors thrown in Mule applications stops execution of the flow and logs information about the error cannot be configured Error object properties -Aiption = string Type = an object Error types -Answer-identified by a namespace and an identifier example: http:unauthorized ns ident Most general error type parent -Answer-ANY Default success response from HTTP Listener -Answer-the payload a status code of 200 Default error repsonse from HTTP Listeners -Answer-error description a status code of 500 On Error Propogate -Answer-at the end of the scope the rest of the flow is not executed the error is rethrown to the next level and handled there HTTP Listener returns an error response On Error Continue -Answer-at the end of the scope the rest of the flow is not executed the event is passed up to the next level as if the flow execution had completed successfully HTTP Listener returns asuccessful response Error scope execution order -Answer-the error is handled by the first error scope whose condition evaluates to true Handling errors at a processor level -Answer-Try Scope to encapsulate the processors you want to have a try catch On Error Propogate behavior in try catch -Answer-rest of try scope is not executed transaction is rolled back error is rethrown On Error Continue behavior in try catch -Answer-Rest of the try scope is not executed transaction is committed event is passed up to the parent flow which continues APIKIT Routing flow -Answer-BaD request 400 not found 404 method not allowed 405 not acceptable 406 unsupported media type 415 not implemented 501 To map to a custom error type -Answer-go to the http request, look at error mapping and map the corresponding error to the custom error type, which then can be referenced by the type field in the type field of error scope handling Messaging error -Answer-thrown when a mule event is involved. These errors can be handled using the standard error handlers and scopes System Error -Answer-thrown when a mule event IS NOT involved. These type of errors occur during start up or when a connection to an external system fails. These errors are handled by the system error handling strategy and cannot be configured. For all types of system errors, logs the error. For connection type errors, logs and also executes the reconnection strategy for the specific connector (set in advanced settings) Data model can consist of what types if data -Answer-Objects, arrays, simple literals XML details -Answer-Can only have one top level value and that value