A water-utility billing API exposes a public JSON field named accountId, but the stable HTTP back end still expects customerNumber. The team wants the public contract to evolve without forking the Function. Which gateway capability should they use?
Select an answer to reveal the explanation.
Short Explanation
The gateway can act like a translator at the city desk—rename the form field on the way in and restore the public name on the way out so the clerk’s system never changes. Request and response transformation policies rewrite headers, query, or body so back ends stay stable while the public contract evolves. Transformations reshape the message; they are not a substitute for a real back end.
Full Explanation
OCI API Gateway supports request policies that transform inbound headers, query parameters, or body content and response policies that transform the outbound message. That lets the public API contract evolve while HTTP or Functions back ends keep stable field names. Prefer transformation before forking a Function only to rename a field. Transformations reshape messages; they do not replace a real back-end implementation.