Council wants the citizen auth gateway to scale horizontally without sticky sessions pinned to a particular EC2 host. Which session approach supports that goal?
Select an answer to reveal the explanation.
Short Explanation
Think hotel keycards that any front desk can swipe—not a room key locked in one clerk's drawer. Bearer tokens or an external session store let any auth instance validate the citizen. Sticky in-memory sessions, pinned private IPs, and a single giant box fight horizontal scale.
Full Explanation
Stateless bearer tokens or sessions stored outside instance memory allow any healthy host behind a load balancer to authenticate requests, enabling horizontal scale without sticky affinity. In-memory sticky sessions couple users to specific hosts. Pinning to private IPs or collapsing to one instance defeats the scale-out goal.