A team must rename fields, reshape the JSON body, and map a backend's HTTP status codes to API responses before the client sees them. Which API Gateway integration offers that control?
Show answer and explanation
Answer: A
A non-proxy (custom) integration lets API Gateway transform requests and responses with mapping templates written in Velocity Template Language. You can reshape bodies, rename fields, read headers, and map backend status codes to method responses. Proxy integrations pass data through with little transformation, and mock integrations return fixed content, so neither gives this level of control.
Why the other options are wrong
- B. Lambda proxy integration hands the full event to the function and returns its output directly. The function can reshape data itself, but API Gateway does not apply mapping templates in this mode.
- C. A mock integration answers from the gateway itself without calling a backend. It is useful for stubbing, but it cannot transform real backend responses or map their status codes.
- D. HTTP proxy integration forwards the request to a backend endpoint and returns its response with minimal change. That is the pass-through case, which does not provide the transformations the team needs.