Refer to the exhibits. The Set Payload transformer in the addltem child flow uses DataWeave to create an order object. What is the correct DataWeave code for the Set Payload transformer in the createOrder flow to use the addltem child flow to add a router call with the price of 100 to the order?
A. lookup( "addltern", { price: "100", item: "router", itemType: "cable" } )
B. addltem( { payload: { price: "100", item: "router", itemType: "cable" > } )
C. lookup( "addltem", { payload: { price: "100", item: "router", itemType: "cable" } > )
D. addltem( { price: "100", item: "router", itemType: "cable" } )
Refer to the exhibit. 
What is a valid expression for the Choice router’s when expression to route events to the
documenticShipping flow?
A.
0#[ payload = 'US' ]
B.
#[ payload == 'US' J
C.
#[ if(payload = 'US') J
D.
#[ if(payload == "US") ]
#[ payload == 'US' J
Which file is used to define the interface contract to invoke a web service implemented as a SOAP service?
A. RAML
B. WSDL
C. JSON
D. OAS
WSDL is used to define the contract in case of SOAP . RAML/OAS is used to REST services.
Refer to the exhibits.
What DataWeave expression transforms the conductorIds array to the XML output?
A. 1. 1. trains:
2. 2. conductorIds map ((engId, index) ->
3. 3. train: {
4. 4. engineerId: engId
5. 5. }
6. 6. )
B. 1. 1. { trains:
2. 2.
3. 3. conductorIds map ((engId, index) ->
4. 4. train: {
5. 5. engineerId: engId
6. 6. }
7. 7. )
8. 8. }
C. 1. 1. trains:
2. 2. {(
3. 3. conductorIds map ((engId, index) ->
4. 4. train: {
5. 5. engineerId: engId
6. 6. }
7. 7. )
8. 8. )}
D. 1. 1. {( trains:
2. 2.
3. 3. conductorIds map ((engId, index) ->
4. 4. train: {
5. 5. engineerId: engId
6. 6. }
7. 7. )
8. 8. )}
Explanation:
Points to remember:
* XML must have a root element.
* XML only allows one root element
* To avoid multiple root issues, you must create a root element for the XML output,
whenever we transform output
* When mapping array elements (JSON or JAVA) to XML, wrap the map operations in {(..)}
-{ } are defining the object
( ) are transforming each element in the array as a key/value pair
* The transformation to XML would fail if the above mentioned considerations were not
taken into account.
* Thus the transformation script declares a root element as trains and wraps the data in “{(
)}“.
Whenever you see such type of question, always look out for root element followed by {( )}
wrapping map.
I call this a "Wrap The Map" scenario. Hope it would help you remember !
What is not true about application properties?
A. Application properties can be encrypted
B. Application properties can be overridden with system properties
C. Application properties can be defined in .yaml file only
D. Application properties provide easier way to manage configurable values
Application properties can be defined in .yaml or in .properties file.
Refer to the exhibits.
The Set Payload transformer's value is set to {'year': '2020'}.
What message value should be added to the Logger component to output the message
'The year is 2020', withouthardcoding 2020?
A.
#[The year is $(pay load .year)]*
B.
The year is #[payload.year]'
C.
'#[The year is " + paytoad.year]'
D.
#["The year is "++ payload.year].
#["The year is "++ payload.year].
According to MuleSoft, what is the Center for Enablement’s role in the new IT operating model?
A. Implements line of business projects to enforce common security requirements
B. Creates and manages discoverable assets to be consumed by line of business developers
C. Centrally manages partners and consultants to implement line of business projects
D. Implements line of business projects to enforce common security requirements
Correct answer is Creates and manages discoverable assets to be consumed by line of
business developers.
C4E does not get directly involved in projects.
A web client sends a request to http;//localhost:8081?dept=sales. What is the correct DataWeave expression to access the value of dept?
A.
attributes.queryParams.dept
B.
attributes.dept
C.
message.queryParams.dept
D.
vars.dept
attributes.queryParams.dept
| Page 1 out of 29 Pages |
Contact Us - Privacy Policy ... Copyright © - All Rights Reserved