Which solution will meet these requirements?
Set the integration type to AWS_PROXY. Provision Lambda functions to return hardcoded JSON data.
Set the integration type to MOCK. Configure the method’s integration request and integration response to associate a JSON responses with specific HTTP status codes.
Set the integration type to HTTP_PROXY. Configure API Gateway to pass all requests to an external placeholder API. which the team will build.
Set the integration type to MOCK. Use a method request to define HTTP status codes. Use an integration request to define JSON responses.
Explanations:
Setting the integration type to AWS_PROXY requires a Lambda function to process requests and generate responses dynamically. This would not provide the predefined HTTP status codes and JSON responses directly, as it would involve additional coding to handle these responses in the Lambda function.
Setting the integration type to MOCK allows the developer to configure the API Gateway to return predefined HTTP status codes and JSON responses without needing a backend service. This meets the requirement of providing immediate access to the API endpoints for the frontend team.
Using HTTP_PROXY passes requests to an external API, which is not aligned with the requirement of providing predefined responses. The frontend team needs predefined endpoints, and relying on an external API would not allow for immediate access to these predefined responses.
Although using a MOCK integration allows defining JSON responses, the explanation of using a method request to define HTTP status codes is incorrect. The correct setup would be configuring the integration response for status codes. Thus, while it partially meets the requirement, it does not accurately describe how to implement it correctly.
I deduce that the answer is:
Set the integration type to MOCK. Configure the method’s integration request and integration response to associate a JSON responses with specific HTTP status codes.