Deployment1 / 5
A company is migrating a three-tier web application to the cloud. The application tier consists of stateful session servers that store user shopping carts in memory. To enable horizontal scaling in the cloud, which modification should be made FIRST?
CorrectNot quite
Alex
One of the biggest challenges in cloud migration is handling stateful application tiers. When session data lives in server memory, users must always reach the same server (session affinity), which limits scaling and creates single points of failure. The cloud-native solution is to externalize state to a shared, distributed store like Redis or Memcached. Once sessions live in an external cache, application servers become stateless — any server can handle any request, and servers can be added or removed freely. Sticky sessions (session affinity) on the load balancer are a temporary workaround that pins users to specific servers, but this creates uneven load distribution, complicates deployments, and means a server failure loses all pinned users' sessions. Increasing memory is vertical scaling, not a path to horizontal scalability. WebSocket conversion addresses connection type, not state management. Exam tip: 'stateful to stateless' migration almost always means externalizing state to a distributed cache.
Sourcedocs.aws.amazon.com
Create a free account to keep asking Alex — no credit card required.
Question 1 of 5
Get started free