Question #578
A developer manages an Amazon API Gateway HTTP API used by a mobile application with AWS IAM authorization. A new API version introduces breaking changes and additional endpoints. The developer needs to allow internal testers to access the new version without impacting the existing mobile users. Which solution meets these requirements with the LEAST operational overhead?
Create a new deployment stage in the existing API Gateway and direct testers to use the stage-specific URL.
Deploy a new API Gateway API linked to the updated backend, instructing testers to target the new API's invoke URL.
Modify the backend to check a custom header, routing requests to the appropriate version based on the header value.
Add new resources and methods to the existing API for the additional endpoints, keeping the original endpoints unchanged.
Explanation
Option A is correct because API Gateway stages enable isolated environments (e.g., dev, test) within the same API. By deploying the new version to a new stage, testers can use the stage-specific URL to access the updated API while existing users continue using the original stage. This approach avoids creating a new API (Option B), modifying backend logic (Option C), or cluttering the API with redundant endpoints (Option D). Stages are a built-in feature designed for versioning and environment management, ensuring minimal setup and maintenance. Other options introduce unnecessary complexity, such as reconfiguring a new API (B), altering backend routing (C), or risking conflicts with breaking changes (D). Key takeaway: Use API Gateway stages to manage versions/environments efficiently.
Answer
The correct answer is: A