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 be configured with Content-Type of text/html for a mock integration, as mock integrations do not involve real requests. Additionally, the response mapping template cannot contain HTML code for a mock integration.
Configuring the integration request mapping template with Content-Type of application/json is not suitable for a mock integration, as mock integrations do not process incoming requests. The response mapping template should not include HTML code directly but instead map to a predefined response.
This option correctly sets the integration request mapping template with Content-Type of application/json and statusCode of 200, while the integration response mapping template is configured with Content-Type of text/html, allowing for the correct response format. Including the HTML code in the response mapping template is appropriate for providing the landing page content.
The integration request mapping template should not include HTML code, and using Content-Type of text/html is inappropriate for a mock integration. The integration response mapping template is correctly set up for text/html, but the request configuration is invalid.