County integration tests must stay on an approved Lambda build while developers keep iterating on unpublished code. How should aliases be used?
Select an answer to reveal the explanation.
Short Explanation
Tape a sticker on the bottle that passed taste-test—leave the open flask for kitchen experiments. A test alias freezes the approved version while $LATEST stays messy. QA on $LATEST is tasting unfinished soup.
Full Explanation
Lambda aliases provide stable pointers to published versions for integration testing while development continues on $LATEST. Pinning a test alias to an approved version freezes the candidate under test. Targeting $LATEST or binding production to $LATEST removes that freeze and couples QA or live traffic to unfinished code.