A dogwood-bend legacy origin still returns XML, but municipal mobile clients want JSON. Without rewriting the origin, what should the APIM developer apply?
Select an answer to reveal the explanation.
Short Explanation
Leave the crusty origin alone and fix the wire format at the gateway. xml-to-json on outbound (or a set-body cousin) hands mobiles JSON without a rewrite of the backend.
Full Explanation
APIM outbound policies can transform response bodies—xml-to-json is the documented policy for converting XML origins to JSON for clients; complementary policies such as json-to-xml or set-body support other shapes. Rewriting every client, substituting Redis, or moving the problem into Logic Apps alone is not the outbound transformation pattern.