You have written an application that uses the Elastic Load Balancing service to spread
traffic to several web servers Your users complain that they are sometimes forced to login
again in the middle of using your application, after they have already togged in. This is not
behavior you have designed. What is a possible solution to prevent this happening?
A.
Use instance memory to save session state.
B.
Use instance storage to save session state.
C.
Use EBS to save session state
D.
Use ElastiCache to save session state.
E.
Use Glacier to save session slate.
D
0
0
D
0
0
I couldnt for the life of me figure out why D, till I found this
https://blogs.aws.amazon.com/net/post/TxMREMF0459SXT/ElastiCache-as-an-ASP-NET-Session-Store
0
0
Answer: D. Use ElastiCache to save session state.
Great link. Relevant text: “By moving the session state to a central location, all the web servers can share a single copy of session state. This allows the ELB to send requests to any web server, better distributing load across all the web servers. In addition, Auto Scaling can terminate individual web servers without losing session state information.”
2
0
This is a tricky question as non of the answers seems correct, but if we go through elimination:
A – instance memory are just memory resources, nothing to do with web sessions.
B – web sessions has nothing to do with instance storage or storage for the matter
C – EBS is storage, nothing to do with web sessions
D – Only this is possible
E – glacier is used for long time storage, not web sessions
But as Khozi pointed out, its D.
0
0
D
0
0
thanks Khozi, D
0
0
D
0
0
D
0
0