Learn how to maintain an Amazon API Gateway REST API that uses Amazon Cognito authentication and a frontend UI. Discover how to deploy a new version of the API with backward-incompatible changes and provide beta access to other developers without affecting customers.
Table of Contents
Question
A developer maintains an Amazon API Gateway REST API. Customers use the API through a frontend UI and Amazon Cognito authentication.
The developer has a new version of the API that contains new endpoints and backward-incompatible interface changes. The developer needs to provide beta access to other developers on the team without affecting customers.
Which solution will meet these requirements with the LEAST operational overhead?
A. Define a development stage on the API Gateway API. Instruct the other developers to point the endpoints to the development stage.
B. Define a new API Gateway API that points to the new API application code. Instruct the other developers to point the endpoints to the new API.
C. Implement a query parameter in the API application code that determines which code version to call.
D. Specify new API Gateway endpoints for the API endpoints that the developer wants to add.
Answer
B. Define a new API Gateway API that points to the new API application code. Instruct the other developers to point the endpoints to the new API.
Explanation
The correct answer is B. Define a new API Gateway API that points to the new API application code. Instruct the other developers to point the endpoints to the new API.
This solution will meet the requirements with the least operational overhead because it will allow the developer to deploy and test the new version of the API without affecting the existing customers or the frontend UI. The other developers can access the new API by changing the base URL of their endpoints to point to the new API Gateway API. This solution also provides isolation and security for the new API, as it can use a separate Amazon Cognito user pool or authorizer.
The other options are not optimal for the following reasons:
A. Define a development stage on the API Gateway API. Instruct the other developers to point the endpoints to the development stage.
This solution will not work because stages are not meant for versioning or testing purposes. Stages are meant for deploying different configurations of the same API to different environments, such as dev, test, or prod. Stages share the same backend integration and resources, so any changes made to one stage will affect all other stages. This means that the developer cannot deploy backward-incompatible interface changes to a development stage without breaking the existing customers or the frontend UI.
C. Implement a query parameter in the API application code that determines which code version to call.
This solution will introduce unnecessary complexity and overhead to the API application code. The developer will have to implement logic in the code to check for the query parameter and route the request to the appropriate code version. This will also increase the maintenance and testing effort, as the developer will have to ensure that both versions of the code are working correctly and handle any errors or conflicts that may arise.
D. Specify new API Gateway endpoints for the API endpoints that the developer wants to add.
This solution will not work because it does not address the backward-incompatible interface changes that the developer wants to make. The developer will still have to modify or delete some of the existing endpoints, which will affect the existing customers or the frontend UI. This solution will also create confusion and inconsistency in the API design, as some endpoints will have different versions or formats than others.
The latest AWS Certified Developer – Associate DVA-C02 certification actual real practice exam question and answer (Q&A) dumps are available free, which are helpful for you to pass the AWS Certified Developer – Associate DVA-C02 exam and earn AWS Certified Developer – Associate DVA-C02 certification.
