Correct answer is Not needed as dw::core module is included by default. We don ' t need to include it explicitly

Allowed methods is an optional configuration. If nothing is specified then all HTTP methods are supported.

Rest all are mandatory.

This kind of questions are best solved with filtering technique. Key thing to note here is XML attributes are always access by @ notation. So in this example orderId can be accessed as @OrderId which makes option 3 and option 4 false. Now difference in optin and option 2 is in mapping of lineItemPrice. Correct syntax to format a String in Numbse is value.price as Number. Hence option 2 is correct

Mule event is correct answer. Mule event has two parts which are as follows

1) Message (which contains payload and attributes like headers and query/uri parameters

2) Variables

Diagram Description automatically generated

The HTTP 415 Unsupported Media Type client error response code indicates that the server refuses to accept the request because the payload format is in an unsupported format. The format problem might be due to the request ' s indicated Content-Type or Content-Encoding , or as a result of inspecting the data directly. As per RAML input is expected in application/xml.

Hence correct answer is Set a request header with the name Content-Type to a

In this case as outbound call is made using HTTP: POST /child , all attributes will be replaced by this invocation. Hence query parameter will not be accessible at logger. Hence correct answer is option 2

Correct answer is ${training.host}

Setting Breakpoints

To set breakpoints, right-click a building block, then select Toggle Breakpoint.

Studio applies a red dot to the building block’s icon on the canvas.

When you run your application in Debug mode, Studio stops the flow execution at the breakpoint you have set, allowing you to check the Mule Event content in the Mule Debugger View.

Mule Ref Doc :  Setting Breakpoints | MuleSoft Documentation