What should the developer do next to meet these requirements?
Configure the integration request mapping template with Content-Type of text/html and statusCode of 200. Configure the integration response mapping template with Content-Type of application/json. In the integration response mapping template, include the LandingPage HTML code that references the APIs.
Configure the integration request mapping template with Content-Type of application/json. In the integration request mapping template, include the LandingPage HMTL code that references the APIs. Configure the integration response mapping template with Content-Type of text/html and statusCode of 200.
Configure the integration request mapping template with Content-Type of application/json and statusCode of 200. Configure the integration response mapping template with Content-Type of text/html. In the integration response mapping template, include the LandingPage HTML code that references the APIs.
Configure the integration request mapping template with Content-Type of text/html. In the integration request mapping template, include the LandingPage HTML code that references the APIs. Configure the integration response mapping template with Content-Type of application/json and statusCode of 200.
Explanations:
The integration request mapping template should not have a Content-Type oftext/html, as the API Gateway expects a JSON payload for integration requests. Also, including HTML in the integration response mapping template would not be appropriate since it’s not a valid format for that context.
The integration request mapping template should not include HTML code; it should focus on JSON format instead. Additionally, the response mapping template should not haveContent-Typeset toapplication/jsonif the intent is to return HTML content for the landing page.
This option correctly sets the integration request mapping template toapplication/json, which is appropriate for API Gateway. The response mapping template withContent-Typeoftext/htmlallows for returning HTML content for the landing page, which is the required functionality.
This option incorrectly configures the integration request mapping template withtext/html, which is not suitable for API Gateway as it expects a JSON request format. The response mapping template is correct in returning HTML content, but the request mapping is misconfigured.
I would say the answer is:
Configure the integration request mapping template with Content-Type of application/json and statusCode of 200. Configure the integration response mapping template with Content-Type of text/html. In the integration response mapping template, include the LandingPage HTML code that references the APIs.