A developer is using Amazon API Gateway as an HTTP proxy to a backend endpoint. There are three separate environments: Development, Testing, Production, and three corresponding stages in the API gateway.
How should traffic be directed to different backend endpoints for each of these stages without creating a separate API for each?
 

Answer options:

A.Add a model to the API and add a schema to differentiate different backend endpoints.
B.Use stage variables and configure the stage variables in the HTTP integration Request of the API.
C.Use API Custom Authorizers to create an authorizer for each of the different stages.
D.Update the Integration Response of the API to add different backend endpoints.

Answer – B
The AWS Documentation mentions the following to support this.
Stage variables are name-value pairs that you can define as configuration attributes associated with a deployment stage of an API. They act like environment variables and can be used in your API setup and mapping templates.
Option A is incorrect since this would only allow for additions of schema’s.
Option C is incorrect since this is only used for Authorization and would not help differentiate the environments.
Option D is incorrect since this would help in integrating the responses to the API gateway.
For more information on Stage variables in the API gateway, please refer to the below Link-
https://docs.aws.amazon.com/apigateway/latest/developerguide/stage-variables.html