A municipal API Gateway API has distinct stages for development, test, and production. Each stage must invoke a different Lambda alias. How should that wiring be managed?
Select an answer to reveal the explanation.
Short Explanation
Stage variables are name tags on the pipes—dev pipe to dev alias, test to test. One API definition, environment-specific pointers. Hard-coding prod into every stage floods the wrong tank.
Full Explanation
API Gateway stages differentiate environments within one API. Stage variables commonly parameterize integrations so each stage targets the correct Lambda alias or backend without rewriting the entire API for every environment. Hard-coding a single production ARN across stages or eliminating stages removes that environment management pattern.