Developers need unfinished API routes isolated from citizens while QA still exercises a stable candidate. How should API Gateway stages be used?
Select an answer to reveal the explanation.
Short Explanation
Stages are lanes on the same bridge—dev traffic here, QA there, citizens elsewhere. Keep unfinished routes on /dev and let QA use /test so production stays calm. Hourly stage-variable roulette is not isolation.
Full Explanation
Amazon API Gateway stages provide environment separation for the same API definition, aligning with testing in development environments. Mapping developer work to a /dev stage and QA to /test keeps incomplete routes away from citizens. Collapsing everything onto production, time-sharing one stage, or bypassing stages with public function URLs weakens that separation.