How to enable frontend development while backend API is not ready using API Gateway?
A company is building an application on AWS. The application's backend includes an Amazon API Gateway REST API. The company's frontend application developers cannot continue work until the backend API is ready for integration. The company needs a solution that will allow the frontend application developers to continue their work. Which solution will meet these requirements in the MOST operationally efficient way?
Community Votes
100% of anonymous learners picked answer A. Votes are pick records left by other test-takers — they are not the verified answer.
Community Insight
This question tests the ability to decouple frontend and backend development using API Gateway's native mock integration feature, avoiding unnecessary infrastructure like Lambda functions or extra endpoints.
When backend APIs are not yet ready, Amazon API Gateway mock integrations allow frontend developers to continue building by returning predefined static responses. This is the most operationally efficient solution as it requires no additional backend resources.
Candidates often choose option B (Lambda function returning a mocked response) because it seems practical, but it is less operationally efficient as it requires deploying and managing additional Lambda resources when API Gateway can natively return mock responses.
Community Discussion (5 comments)
Comments & Corrections
No comments yet — spotted an error or have a note? Share it below.
Expert Analysis
The correct answer is A. Configure mock integrations for API Gateway API methods.
Amazon API Gateway supports mock integrations, which allow you to define a method that returns a static response without forwarding the request to any backend service. This is specifically designed for scenarios where frontend developers need to proceed with integration testing or UI development while the backend is still under construction.
Why Option A is correct: Mock integrations are built directly into API Gateway. You simply configure the integration type as MOCK and define the response templates. This requires zero additional AWS resources, making it the most operationally efficient solution. Frontend developers can immediately start consuming the API with predictable response structures.
Why Option B is incorrect: While integrating a Lambda function that returns a mocked response would technically work, it introduces unnecessary operational overhead. You would need to write, deploy, and maintain a Lambda function solely for returning static data. This violates the principle of operational efficiency since API Gateway can accomplish the same task natively.
Why Option C is incorrect: Adding new API endpoints to the API Gateway stage does not address the core requirement. The question is about enabling frontend development while the backend is not ready, not about creating additional endpoints. This option also lacks clarity on how the mocked response would be generated.
Why Option D is incorrect: A proxy resource in API Gateway forwards all requests directly to a backend integration (like Lambda or HTTP). It does not provide mock responses and would still require a functioning backend, defeating the purpose of allowing frontend developers to work independently.
Community consensus strongly supports Option A, with 100% of voters selecting it. As noted by community members, mock integrations are the standard AWS approach for enabling parallel development between frontend and backend teams.
Official Reference
Exam Strategy
When the question emphasizes 'MOST operationally efficient,' always look for the solution that uses native AWS features without requiring additional resources. Mock integrations in API Gateway are a perfect example of a built-in feature that solves a common development workflow problem without extra infrastructure.
Related Analysis
Practice All DVA-C02 Questions
Access 100 questions with complete answers and detailed explanations.
View Full DVA-C02 Practice Test →