A busy county resident portal caches session and lookup data in ElastiCache. Leadership wants the cache tier to survive node failure without dropping the whole site’s sessions. What design improves cache resilience?
Select an answer to reveal the explanation.
Short Explanation
Sessions hate surprise evictions. Multi-AZ ElastiCache with failover keeps a warm spare ready so one sick node doesn’t boot every resident out of the portal.
Full Explanation
ElastiCache Multi-AZ with automatic failover maintains replicas and promotes a healthy node when the primary fails, improving session and cache resilience. A single-node, single-AZ design is a cache SPOF. Flushing on every deploy or co-locating the only node with one web AZ concentrates failure risk. For a busy municipal portal, Multi-AZ cache design is the reliability pattern.