Free AWS DVA-C01 Actual Exam Questions - Question 14 Discussion

Question No. 14
An e-commerce web application that shares session state on-premises is being migrated to AWS. The
application must be fault tolerant, natively highly scalable, and any service interruption should not
affect the user experience.
What is the best option to store the session state?
Select one option, then reveal solution.
US
PL
Paul L.
2026-02-16

A/D? While stickiness (D) keeps things simple by tying users to one server, it’s risky if that server goes down, causing session loss. ElastiCache (A) offers distributed, in-memory storage that’s fast and scales well with zero downtime impact, which is vital for a smooth user experience. CloudFront (B) isn’t meant for session storage, and S3 (C) is too slow for real-time session needs. So between A and D, A fits better for fault tolerance and scalability without interrupting users.

0
FK
Farhan K.
2026-02-10

A/C? S3 is super durable but too slow for session data. ElastiCache is fast and supports fault tolerance, which fits the need for no user impact during interruptions better.

0
SS
Sarah S.
2026-01-25

It’s D since stickiness avoids syncing issues and keeps sessions consistent per user.

0
RG
Ravi G.
2026-01-23

A/D? I get why A is popular since ElastiCache is fast and handles failover well, but D’s session stickiness keeps the user tied to one instance, so no constant session sync needed. The problem is if that instance fails, the session breaks. So D isn’t fully fault tolerant. A still seems more robust because it shares session state across all instances, making it scalable and fault tolerant. Stickiness might be simpler but won’t handle server failures smoothly.

0
RG
Ravi G.
2026-01-19

It’s A because ElastiCache offers low-latency, in-memory storage that’s perfect for session state and supports automatic failover, unlike session stickiness which can cause issues if a server goes down.

0
RG
Ravi G.
2026-01-18

It’s D because session stickiness lets users keep the same backend server during their session, so no need to constantly sync session data across instances. This avoids state-sharing complexity and helps with fault tolerance since the load balancer handles routing. ElastiCache is good but adds extra overhead and possible latency, while stickiness is simpler and often enough for many web apps.

0
RG
Ravi G.
2026-01-17

It’s A, ElastiCache fits best for session state caching.

0