A developer is preparing an Amazon API Gateway API (with a Lambda backend) so frontend teams can start building the UI before the backend is implemented. The frontend team needs endpoints that return predefined HTTP status codes and JSON bodies. The developer created a method for an API resource. Which approach fulfills these requirements?

The MOCK integration type in API Gateway is specifically designed for scenarios where you need to simulate API responses without a backend. It allows you to define static responses directly within API Gateway. You configure the integration request and integration response to map desired HTTP status codes and JSON bodies, fulfilling the requirement for predefined responses. AWSPROXY integration requires a Lambda function to process requests and return responses, which is not ideal for pre-implementation UI development. HTTPPROXY integration forwards requests to another HTTP endpoint, also requiring an external service. While MOCK is correct, the last option incorrectly separates the definition of HTTP status codes and JSON responses; both are handled within the integration request and response mapping in a MOCK integration.