Before wiring live back ends, a developer wants /health on a new municipal API deployment to always return a fixed 200 body from the gateway itself. Which back-end type should they use?
Select an answer to reveal the explanation.
Short Explanation
Stock response is the gateway answering from its own desk drawer—fixed status, body, and headers, no trip to a function or URL. Handy for health checks and placeholders, not for hosting big content.
Full Explanation
A stock-response back end makes the API Gateway itself return a fixed status, body, and headers without calling a function or HTTP URL. Use it to verify a deployment is reachable, reserve a path with a constant response, or as the placeholder OpenAPI import may create (for example 501 when no response is described). Documented body and header sizes are small; it is not a content-hosting service.