Mule 3 inbound message properties are set from the message source and have which access level?

Mule 3 inbound message properties are set from the message source and have which access level?

• A. Write-only access
• B. Read-only access
• C. Read/Write access
• D. Not accessible

Answer: (B)

Inbound message properties are metadata provided by the transport when a message arrives. They describe the original input (such as endpoint, HTTP method, headers, or JMS properties) and are meant to reflect the incoming event as it was received. Because this information comes from the transport, Mule treats these properties as read-only within the flow. You can read them to guide routing or logging, but you shouldn’t attempt to modify them. If you need to alter how processing proceeds, use the payload or flow variables (and outbound properties for the response) instead.

Inbound message properties are metadata provided by the transport when a message arrives. They describe the original input (such as endpoint, HTTP method, headers, or JMS properties) and are meant to reflect the incoming event as it was received. Because this information comes from the transport, Mule treats these properties as read-only within the flow. You can read them to guide routing or logging, but you shouldn’t attempt to modify them. If you need to alter how processing proceeds, use the payload or flow variables (and outbound properties for the response) instead.