What is the default HTTP status code returned for a successful message, and how can it be changed?

• A. 200 by default; can be changed by setting outbound property message.outboundproperties.'httpstatus'
• B. 201 by default; can be changed by setting inbound property message.inboundproperties.'httpstatus'
• C. 500 by default; can be changed by exception strategy
• D. 404 by default; can be changed by setting header in response

Answer: (A)

The main idea is that a successful HTTP response starts with status 200. In a Mule flow, if you don’t specify a status, the HTTP connector uses 200 automatically for a successful message. To change this, you override the outgoing HTTP status by setting the message’s outbound property named httpstatus. When you assign a value to that property (for example, message.outboundProperties.'httpstatus' = 201), Mule uses that code for the response instead of 200. This is how you signal different outcomes like “Created” (201) or “No Content” (204) from your flow. The other options describe different outcomes or errors and aren’t the default behavior for a successful response.