AWS Certified Developer - Associate
Get started today
Ultimate access to all questions.
Ultimate access to all questions.
A company is planning to offer beta access to a select group of developers on its development team for a new version of their Amazon API Gateway REST API. The aim is to ensure that this beta testing does not interfere with the current customers who are accessing the API through a frontend UI along with Amazon Cognito authentication. Notably, the new API version includes additional endpoints and backward-incompatible interface changes, and the responsibility for its maintenance lies with the company’s development team.
Which of the following options will meet these requirements in the MOST operationally efficient way?
Explanation:
A stage is a logical reference to a lifecycle state of your API (for example, 'dev', 'prod', 'beta', 'v2'). API stages are identified by API ID and stage name. You use a stage to manage and optimize a particular deployment. For example, you can configure stage settings to enable caching, customize request throttling, configure logging, define stage variables, or attach a canary release for testing. After the initial deployment, you can add more stages and associate them with existing deployments. You can use the API Gateway console to create a new stage, or you can choose an existing stage while deploying an API. In general, you can add a new stage to an API deployment before redeploying the API.
For the given use case, you can configure a development stage for your API Gateway API and then integrate it with the new version of the backend functionality that has new endpoints and backward-incompatible interface changes. The customers can continue to use the existing API.