A Developer is migrating an on-premises web application to the AWS Cloud. The application currently runs on a 32-processor server and stores session state in memory. On Friday afternoons the server runs at 75% CPU utilization, but only about 5% CPU utilization at other times.
How should the Developer change to code to better take advantage of running in the cloud?
 

Answer options:

A.Compress the session state data in memory.
B.Store session state on EC2 instance Store.
C.Encrypt the session state data in memory.
D.Store session state in an ElastiCache cluster.

Answer – D
ElastiCache is the perfect solution for managing session state. This is also given in the AWS Documentation.
In order to address scalability and to provide a shared data storage for sessions that can be accessed from any individual web server, you can abstract the HTTP sessions from the web servers themselves. A common solution to this is to leverage an In-Memory Key/Value store such as Redis and Memcached.
Option A is incorrect since compression is not the ideal solution.
Option B is incorrect since EC2 Instance Store is too volatile.
Option C is incorrect since this is ok from a security standpoint but will just make the performance worse for the application.
For more information on Session Management, please refer to the below Link-
https://aws.amazon.com/caching/session-management/