How should the database specialist deploy ElastiCache to meet this requirement?
Launch an ElastiCache for Redis cluster using the AWS CLI with the -cluster-enabled switch.
Launch an ElastiCache for Redis cluster and select read replicas in different Availability Zones.
Launch two ElastiCache for Redis clusters in two different Availability Zones. Configure Redis streams to replicate the cache from the primary cluster to another.
Launch an ElastiCache cluster in the primary Availability Zone and restore the cluster’s snapshot to a different Availability Zone during disaster recovery.
Explanations:
The-cluster-enabledswitch is used for Redis Cluster mode, which does not ensure high availability. It is not sufficient for making the deployment highly available across multiple Availability Zones.
Launching an ElastiCache for Redis cluster with read replicas in different Availability Zones ensures high availability, as it allows automatic failover if the primary node becomes unavailable.
Launching two ElastiCache clusters in different Availability Zones and using Redis streams for replication is not a recommended approach for high availability in ElastiCache, as it introduces unnecessary complexity and does not leverage built-in high availability features.
Launching an ElastiCache cluster in the primary Availability Zone and relying on snapshot restoration for disaster recovery does not ensure high availability, as it lacks real-time failover and replication capabilities.
I guess:
Launch an ElastiCache for Redis cluster and select read replicas in different Availability Zones.