How to Mock Third-Party API Integrations in AWS API Gateway?

DVA-C02 By islever Editorial Last updated

Short answer

D Set up an Amazon API Gateway REST API for each third-party API. Specify an integration request type of Mock. Configure integration responses by using sample responses captured from the real third-party API.

Question

A developer is working on an ecommerce platform that communicates with several third-party payment processing APIs. The third-party payment services do not provide a test environment. The developer needs to validate the ecommerce platform's integration with the third-party payment processing APIs. The developer must test the API integration code without invoking the third-party payment processing APIs. Which solution will meet these requirements?
  1. Set up an Amazon API Gateway REST API with a gateway response configured for status code 200. Add response templates that contain sample responses captured from the real third-party API.
  2. Set up an AWS AppSync GraphQL API with a data source configured for each third-party API. Specify an integration type of Mock. Configure integration responses by using sample responses captured from the real third-party API.
  3. Create an AWS Lambda function for each third-party API. Embed responses captured from the real third-party API. Configure Amazon Route 53 Resolver with an inbound endpoint for each Lambda function's Amazon Resource Name (ARN).
  4. Set up an Amazon API Gateway REST API for each third-party API. Specify an integration request type of Mock. Configure integration responses by using sample responses captured from the real third-party API. Correct Answer

Key Takeaways

The question tests knowledge of API Gateway's Mock integration type, distinguishing it from gateway responses, which serve a different purpose in error handling.

This question tests the ability to mock third-party API responses using Amazon API Gateway REST API Mock integrations. The community overwhelmingly agrees that configuring a Mock integration type with integration responses containing sample payloads is the correct approach.

Common mistake: Many candidates choose Option A, confusing gateway responses (used for customizing error responses like 4xx/5xx) with Mock integrations (used to simulate backend responses without a real backend).

Expert Analysis

Understanding Mock Integrations in Amazon API Gateway

When a developer needs to test API integration code without calling real third-party services, Mock integration in Amazon API Gateway is the standard AWS solution. A Mock integration allows API Gateway to return a predefined response without forwarding the request to any backend, making it ideal for testing and development scenarios.

Why Option D is Correct

Option D correctly describes setting up an Amazon API Gateway REST API for each third-party API and specifying the integration request type as Mock. The developer then configures integration responses with sample JSON payloads captured from the real third-party APIs. This approach accurately simulates the behavior of each third-party service, allowing the ecommerce platform's integration logic to be thoroughly tested.

Why Option A is Incorrect

Option A suggests using gateway responses configured for status code 200 with response templates. Gateway responses in API Gateway are designed to customize error responses (such as 4xx and 5xx errors) and are not intended to simulate backend payloads. Community comments correctly point out that gateway responses do not provide the detailed response structures needed to test integration logic effectively.

Why Options B and C are Incorrect

Option B proposes using AWS AppSync with a Mock integration type. While AppSync does support Mock data sources, it is primarily a managed GraphQL service and is not the appropriate tool for simulating RESTful third-party payment APIs. Option C suggests using AWS Lambda functions with Amazon Route 53 Resolver, which is unnecessarily complex, costly, and Route 53 Resolver is not designed for API mocking.

Community Consensus

The community strongly supports Option D, with 92% of votes. Commenters highlight the official AWS documentation on Mock integrations as the authoritative reference, confirming that Mock integration with integration responses is the intended solution for this scenario.

Official Reference

https://docs.aws.amazon.com/apigateway/latest/developerguide/how-to-mock-integration.html

This link opens the official vendor documentation in a new tab.

Exam Strategy

When you see 'mock' or 'simulate backend without invoking real services' in an API Gateway question, immediately look for the 'Mock integration type' keyword. Do not confuse Mock integrations with gateway responses, which are meant for error handling.

Community Votes

D
100%

100% of anonymous learners picked answer D. Votes are pick records left by other test-takers — they are not the verified answer.

Discussion 7 contributions

Compiled from public community threads and reader submissions, lightly edited for clarity. Handles and vote tallies are shown as recorded, and comments reflect the views of individual contributors.

From public community threads 7

  1. Abdullah22 👍 2 Answered D
    A. Response Templates for Status Code 200: While API Gateway supports response templates, simply configuring a 200 status code doesn't simulate the specific responses expected from the third-party APIs. The developer needs to define more detailed response structures to effectively test the integration logic.
  2. KarBiswa 👍 2 Answered D
    https://docs.aws.amazon.com/apigateway/latest/developerguide/how-to-mock-integration.html
  3. ANDRES715 👍 1 Answered A
    A. Configure una API REST de Amazon API Gateway con una respuesta de puerta de enlace configurada para el código de estado 200. Agregue plantillas de respuesta que contengan respuestas de muestra capturadas de la API real de terceros. Al configurar una API REST de Amazon API Gateway con una respuesta de puerta de enlace configurada para el código de estado 200, el desarrollador puede simular las respuestas de las API de procesamiento de pagos de terceros sin invocar realmente las API reales. Al agregar plantillas de respuesta que contengan respuestas de muestra capturadas de la API real de terceros, el desarrollador puede validar la integración de la plataforma de comercio electrónico con las API de procesamiento de pagos de terceros sin tener que interactuar directamente con las API reales.
  4. MasoudK 👍 1
    I will go with A. You can manage all mock responses within a single API Gateway, simplifying the setup and reducing costs.
  5. Abdullah22 👍 1
    anyone know way the questions end by this question which is 328 and there is no rest of the 337 questions?
Show 2 more comments
  1. CrescentShared 👍 6 Answered D
    D is right
  2. 65703c1 👍 2 Answered D
    D is the correct answer.

Reader comments & corrections

No reader corrections yet — spotted an error or have a note? Share it below.

Log in to comment, report an error, or add a note about this question.

How to Log Every Lambda Invocation to an SQS Queue?

S-grade

Identifying and Removing Clients in AWS API Gateway WebSocket APIs

S-grade

How to Test Updated Lambda Functions with a Subset of Users Using API Gateway?

S-grade

How to automate S3 object tagging after delayed third-party content audit?

S-grade

Practice All DVA-C02 Questions

Access 100 questions with complete answers and detailed explanations.

View Full DVA-C02 Practice Test →

← Back to DVA-C02 Study Guide