To transform XML to JSON in DataWeave 2.0, which script setup is correct?

• A. Use a DataWeave script with input 'application/xml' and output 'application/json', e.g., %dw 2.0; output application/json; --- payload.
• B. Use a DataWeave script with input 'application/json' and output 'application/xml'; %dw 2.0; output application/xml; --- payload.
• C. Use a DataWeave script with input 'application/xml' and output 'application/json'; %dw 1.0; output application/json; --- payload.
• D. Use a DataWeave script with input 'text/plain' and output 'application/json'.

Answer: (A)

Transforming data formats in DataWeave hinges on declaring what you’re reading and what you’re producing. For Mule 4, using DataWeave 2.0, converting XML to JSON means the script should read XML input and emit JSON output. Specifying the DataWeave version as 2.0 and setting the output to application/json signals DataWeave to parse the incoming XML (application/xml) and produce JSON. The payload expression then yields the transformed JSON representation of the XML input. This setup matches the requested direction—XML to JSON—and uses the correct DataWeave version for Mule 4. The other options either reverse the transformation, rely on the older DataWeave 1.0, or specify an unsuitable input type like text/plain.