How do you handle binary data in DataWeave?

• A. Use appropriate input/output types and encoding, and map binary payloads directly or encode/decode using read/write with application/octet-stream.
• B. Binary data cannot be handled in DataWeave.
• C. Always convert binary data to string.
• D. Binary data is processed only in the JVM code outside DataWeave.

Answer: (A)

Binary data in DataWeave is treated as a raw stream of bytes, so you can work with it without forcing it into text form. The best approach is to use the right input/output type and encoding, then either pass the binary payload through directly or convert it when needed by using read and write with a binary-oriented mime type such as application/octet-stream.

This is why the correct approach is effective: you can keep the data in its binary form when you want a faithful pass-through, ensuring no corruption that can happen with string conversions. If you need a textual representation or a different encoding, you can decode or re-encode the binary using read or write with the appropriate mime type, such as application/octet-stream, or switch to a base64 variant when a textual format is required.

Binary data cannot be dismissed as unsupported, and forcing a string conversion is not always appropriate or safe for non-text files. Also, binary processing is not limited to JVM code outside DataWeave—DataWeave provides the tools to handle it directly within the transformation.