A parks department API Gateway has stages for test and prod. Developers want each stage to invoke a different Lambda alias without cloning the entire API definition. Which feature provides that dynamic stage-to-backend binding?
Select an answer to reveal the explanation.
Short Explanation
Staging variables are the sticky notes on each stage door: test points at alias test, prod at alias prod—same API blueprint. Cloning the whole API or hard-coding prod ARNs everywhere is how parks APIs turn into a paperwork swamp.
Full Explanation
API Gateway staging variables let stages resolve configuration such as which Lambda alias to invoke without duplicating the full API definition per environment. That supports environment-specific backend bindings while keeping one API model. Hard-coding a single alias, per-method accounts, or abandoning stages discards this deployment pattern.