Q: 4
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
Discussion
B , seen this in practice tests and AWS official docs cover global data store as the easiest managed way.
B seems right, is it. Had something like this in a mock before-global data store for ElastiCache Redis does auto encrypted cross-Region sync and has the failover built in with almost no management overhead. Other options are way more hands-on. Anyone disagree?
It’s D, not B. Snapshots make DR easy and seem like less effort, though I could be missing a catch with encryption.
B is the right pick here since ElastiCache global datastore gives you managed cross-Region replication with encryption baked in. No need for extra DMS setup or manual failover steps, which keeps operational effort low. I think that's what the question aims for, but happy to discuss if someone sees a gap.
B/C? Leaning B because global datastore seems more automated, but not 100% sure if there's a hidden catch.
Tricky part here is the encryption for cross-Region transfers, which rules out D since snapshot copies aren't encrypted in-transit by default. So B is the only one that actually meets all requirements without manual setup or extra tooling. If encryption wasn't called out, maybe D could work, but not for this specific scenario I think. Disagree?
B Just one step, global datastore covers cross-Region replication and encryption automatically. No need to set up DMS or handle snapshots. Pretty sure that's exactly what AWS wants you to use for this scenario.
I don’t think it’s D. B matches the least effort part, global datastore is built for this and traps you if you miss the encryption bit.
C/D? If cluster mode is off, DMS might not support all replication needs for Redis OSS, so depends.
I don't think A, C or D match the "least operational effort" part. B uses global data store which handles cross-Region encrypted replication automatically, so you avoid all the manual DMS or snapshot work. Saw a similar question in practice sets. Only thing to watch is that D might trick folks if you miss the encryption requirement!
Be respectful. No spam.
