MuleSoft Developer Exam |137
Accurate Q’s and A’s
When do variables persist? - -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 - -False
- Syntax to fetch a variable - -#[vars.foo]
- What persists when calling from a parent flow to another flow via http
request? - -Not variables
- API Interface definition file (API Specification) - -defines what you call,
what you send it, and what you get back
- A Web Service - -The Actual API implementation you can make calls to or
interface of that API implementation
- An API Proxy - -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? - -Variables
- JMS connector - -connector capable of sending and receiving messages to
and from topics and queues
- JMS Publish - -Operation that allows the user to send a message to a JMS
Destination
- JMS Publish - Consume - -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 - -dataweave
#[payload.size != 0]
- Execution order of functions - -the last function in the chain is executed
first
- Calling flows from a DW Expression - -use the lookup function
, {a: lookup("myFlow",{b:"Hello"})}
- How to import a function in a module - -import dasherize from
dw::core::Strings
- How to import a module - -import dw::core::Strings
- You can call subflows from a dataweave expressions - -false
- map - -Iterates over items in an array and outputs the results into a new
array.
- Scatter gather output - -returns a collection of all results, collection is an
object of objects
each object contains attributes and payload
- validation module - -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 - -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 - -error.description = string
error.errorType = an object
- Error types - -identified by a namespace and an identifier
example:
http:unauthorized
ns ident
- Most general error type parent - -ANY
- Default success response from HTTP Listener - -the payload
a status code of 200
- Default error repsonse from HTTP Listeners - -error description
a status code of 500
Accurate Q’s and A’s
When do variables persist? - -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 - -False
- Syntax to fetch a variable - -#[vars.foo]
- What persists when calling from a parent flow to another flow via http
request? - -Not variables
- API Interface definition file (API Specification) - -defines what you call,
what you send it, and what you get back
- A Web Service - -The Actual API implementation you can make calls to or
interface of that API implementation
- An API Proxy - -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? - -Variables
- JMS connector - -connector capable of sending and receiving messages to
and from topics and queues
- JMS Publish - -Operation that allows the user to send a message to a JMS
Destination
- JMS Publish - Consume - -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 - -dataweave
#[payload.size != 0]
- Execution order of functions - -the last function in the chain is executed
first
- Calling flows from a DW Expression - -use the lookup function
, {a: lookup("myFlow",{b:"Hello"})}
- How to import a function in a module - -import dasherize from
dw::core::Strings
- How to import a module - -import dw::core::Strings
- You can call subflows from a dataweave expressions - -false
- map - -Iterates over items in an array and outputs the results into a new
array.
- Scatter gather output - -returns a collection of all results, collection is an
object of objects
each object contains attributes and payload
- validation module - -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 - -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 - -error.description = string
error.errorType = an object
- Error types - -identified by a namespace and an identifier
example:
http:unauthorized
ns ident
- Most general error type parent - -ANY
- Default success response from HTTP Listener - -the payload
a status code of 200
- Default error repsonse from HTTP Listeners - -error description
a status code of 500
