What is the result if a non-text-based payload is uploaded to Anypoint MQ?

• A. It is converted to a string before sending.
• B. It is rejected with an error.
• C. It remains in its original binary form.
• D. It triggers a security alert.

Answer: (A)

Payload handling in Anypoint MQ aims for consistent text-based serialization. When a payload that isn’t text is uploaded, the system converts it into a string before sending. This normalization ensures the message body can be transmitted and consumed reliably by a wide range of clients and processors that expect text data. The conversion uses the platform’s standard encoding (typically UTF-8), so the data is transformed into a textual form rather than remaining in its original binary state. If exact binary fidelity is required, you would typically encode the data (for example, base64) before sending or use a binary-aware workflow. This behavior avoids rejection or automatic security alerts, which wouldn’t align with providing a consistent, text-based transport.