ElastiCache Redis Automatic Failover
A caching layer uses Amazon ElastiCache for Redis in front of a stateless web service. The service must continue to read cached responses during maintenance events and should automatically fail over to another node if one AZ becomes impaired. Which design change best satisfies this requirement?
Quick Answer
The requirement here has two parts, continued reads during maintenance and automatic recovery if an AZ becomes impaired, and a Redis replication group configured for automatic failover across multiple Availability Zones is built to satisfy both at once. Because the replication group maintains a primary node plus read replicas in different AZs, the service isn't dependent on any single node or single AZ staying healthy; if the primary becomes unavailable, whether from a maintenance event or an AZ-level impairment, one of the replicas in another AZ is automatically promoted to take over as primary with minimal disruption. This is different from a single-node cache or a replication group confined to one AZ, where any interruption to that one node, planned or not, would mean the stateless web service in front of it temporarily has nowhere to read cached responses from. Spreading the nodes across AZs and enabling automatic failover is what converts a single point of failure into a resilient setup that can absorb both routine maintenance and unplanned AZ issues without manual intervention. Whenever a caching or data layer needs to keep serving reads through both planned maintenance and unplanned infrastructure failures, that combination of requirements is the cue to look for a multi-AZ replication group with automatic failover rather than a single-node or single-AZ configuration.
⚠ Common exam trap
Watch out — candidates often confuse Memcached's simplicity with Redis's replication capabilities, assuming that client-side connection pooling alone can handle failover, when in fact Memcached lacks any built-in replication or automatic failover mechanism.
Answer choices
Why each option matters
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Configure an ElastiCache Redis replication group with automatic failover across multiple Availability Zones.
An ElastiCache Redis replication group with automatic failover across multiple Availability Zones ensures that if the primary node or its AZ becomes impaired, a read-replica in another AZ is automatically promoted to primary. This allows the stateless web service to continue reading cached responses without interruption, satisfying both the maintenance and AZ impairment requirements.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Deploy a single-node Redis cluster and rely on application-level retries when cache misses occur.
Why it's wrong here
A single-node setup has no automatic failover, so AZ impairment can fully break cache availability.
When this WOULD be correct
This option would be correct in a scenario where the application can tolerate cache unavailability (e.g., reads from a slower database are acceptable) and the primary goal is cost minimization, with no requirement for high availability or automatic failover.
- ✓
Configure an ElastiCache Redis replication group with automatic failover across multiple Availability Zones.
Why this is correct
Multi-AZ replication groups provide redundant nodes and automatic failover, improving cache resilience during AZ events.
- ✗
Move the cache into the VPC but keep it in one Availability Zone to reduce network latency.
Why it's wrong here
Network placement does not address AZ-level redundancy; keeping one AZ still creates a single point of failure.
When this WOULD be correct
If the requirement was to minimize latency for a single-AZ application with no high availability needs, and the question explicitly stated that AZ impairment is not a concern, then deploying in one AZ would be appropriate.
- ✗
Use a Memcached cluster and configure only client-side connection pooling without failover support.
Why it's wrong here
Memcached differs operationally and connection pooling does not implement node-level failover in another AZ.
When this WOULD be correct
If the requirement was for a simple, low-latency cache that can tolerate data loss and does not need automatic failover (e.g., caching non-critical, recomputable data in a single AZ), Memcached with client-side pooling would be appropriate.
Option-by-option analysis
Why each answer is right or wrong
Understanding why wrong answers are wrong — and when they would be correct — is what separates a 750 score from a 900. The SAA-C03 exam frequently reuses these exact scenarios with slightly different constraints.
✓Configure an ElastiCache Redis replication group with automatic failover across multiple Availability Zones.Correct answer▾
Why this is correct
Multi-AZ replication groups provide redundant nodes and automatic failover, improving cache resilience during AZ events.
✗Deploy a single-node Redis cluster and rely on application-level retries when cache misses occur.Wrong answer — click to see why▾
Why this is wrong here
A single-node Redis cluster lacks automatic failover; if the node or its AZ becomes impaired, the service cannot read cached responses until the node is restored, violating the requirement for continued reads during maintenance and AZ impairment.
★ When this WOULD be the correct answer
This option would be correct in a scenario where the application can tolerate cache unavailability (e.g., reads from a slower database are acceptable) and the primary goal is cost minimization, with no requirement for high availability or automatic failover.
Why candidates choose this
Candidates may think a single-node cluster is simpler and cheaper, and assume application-level retries are sufficient to handle failures, underestimating the need for automatic failover to maintain cache availability during AZ impairments.
✗Move the cache into the VPC but keep it in one Availability Zone to reduce network latency.Wrong answer — click to see why▾
Why this is wrong here
Keeping the cache in one Availability Zone does not provide automatic failover to another node if that AZ becomes impaired, failing the requirement for high availability during maintenance events.
★ When this WOULD be the correct answer
If the requirement was to minimize latency for a single-AZ application with no high availability needs, and the question explicitly stated that AZ impairment is not a concern, then deploying in one AZ would be appropriate.
Why candidates choose this
Candidates may think that reducing network latency by keeping the cache in one AZ is more important than high availability, or they may overlook the failover requirement and focus solely on performance.
✗Use a Memcached cluster and configure only client-side connection pooling without failover support.Wrong answer — click to see why▾
Why this is wrong here
Memcached does not support automatic failover or multi-AZ replication; if an AZ becomes impaired, the cache becomes unavailable, violating the requirement for continued reads during maintenance.
★ When this WOULD be the correct answer
If the requirement was for a simple, low-latency cache that can tolerate data loss and does not need automatic failover (e.g., caching non-critical, recomputable data in a single AZ), Memcached with client-side pooling would be appropriate.
Why candidates choose this
Candidates may confuse Memcached's simplicity and speed with high availability, or assume that client-side connection pooling alone provides failover, not realizing Memcached lacks built-in replication and automatic failover.
Analysis generated from the official SAA-C03blueprint and verified against question context. The “when correct” sections are what AI assistants cite when candidates ask “what’s the difference between these options?”
Go deeper
Related to this question
About these practice questions
One of 302 original SAA-C03 practice questions on Courseiva, each with a full explanation and wrong-answer analysis — not exam dumps or protected exam content. Learn why practice questions differ from exam dumps →
Same concept, more angles
1 more way this is tested on SAA-C03
These questions test the same concept from different angles. Work through them to make sure you can recognise it however the exam phrases it.
Variation 1. A caching layer uses Amazon ElastiCache for Redis in front of a stateless web service. The service must continue to read cached responses during maintenance events and should automatically fail over to another node if one AZ becomes impaired. Which design change best satisfies this requirement?
medium- A.Deploy a single-node Redis cluster and rely on application-level retries when cache misses occur.
- ✓ B.Configure an ElastiCache Redis replication group with automatic failover across multiple Availability Zones.
- C.Move the cache into the VPC but keep it in one Availability Zone to reduce network latency.
- D.Use a Memcached cluster and configure only client-side connection pooling without failover support.
Why B: An ElastiCache Redis replication group with automatic failover across multiple Availability Zones ensures that if the primary node or its AZ becomes impaired, a read-replica in another AZ is automatically promoted to primary. This allows the stateless web service to continue reading cached responses during maintenance events without interruption, as the failover is transparent to the application.
JA
Written by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
This SAA-C03 practice question is part of Courseiva's free Amazon Web Services certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the SAA-C03 exam.