SAA-C03 · Question #517
A large financial services company uses Amazon ElastiCache (Redis OSS) for its new application that has a global user base. A solutions architect must develop a caching solution that will be…
The correct answer is B. Create a global data store in ElastiCache (Redis OSS). Then create replica clusters in two other. The optimal solution for low-latency global caching with disaster recovery and cross-Region replication is to use Amazon ElastiCache Global Datastore for Redis OSS. A Global Datastore enables fully managed cross-Region replication and supports automatic failover by promoting…
Question
A large financial services company uses Amazon ElastiCache (Redis OSS) for its new application that has a global user base. A solutions architect must develop a caching solution that will be available across AWS Regions and include low-latency replication and failover capabilities for disaster recovery (DR). The company's security team requires the encryption of cross-Region data transfers. Which solution meets these requirements with the LEAST amount of operational effort?
Options
- AEnable cluster mode in ElastiCache (Redis OSS). Then create multiple clusters across Regions
- BCreate a global data store in ElastiCache (Redis OSS). Then create replica clusters in two other
- CDisable cluster mode in ElastiCache (Redis OSS). Then create multiple replication groups across
- DCreate a snapshot of ElastiCache (Redis OSS) in the primary Region and copy it to the failover
How the community answered
(30 responses)- A17% (5)
- B73% (22)
- C3% (1)
- D7% (2)
Explanation
The optimal solution for low-latency global caching with disaster recovery and cross-Region replication is to use Amazon ElastiCache Global Datastore for Redis OSS. A Global Datastore enables fully managed cross-Region replication and supports automatic failover by promoting read replica clusters in another Region. ElastiCache ensures encryption in-transit and at-rest, meeting compliance and security requirements. It's a fully managed AWS-native feature, reducing operational effort compared to setting up DMS-based or snapshot-based replication manually. Other options (A, C, D): Require manual setup and management (e.g., custom DMS pipelines, snapshots). Do not offer real-time replication or failover without manual intervention.
Community Discussion
No community discussion yet for this question.