Your company runs a popular map service as a SaaS platform. Your dynamic multi-page application users are spread across the world, but not all of them heavily use the system. So the load is high in some of the regions but not all. The application uses the NoSQL database and runs it on a cluster of EC2 machines and using the custom tools to replicate the data across different regions. The current database size is around 10PB. As the popularity of the application grows, the database is also growing rapidly. Now the application is serving millions of requests from your SaaS platform. The management has decided to develop a plan to re-design the architecture dynamically, both from the application availability and infrastructure cost perspective. Please suggest the necessary changes. Select 3 Options.

Answer options:

A.Route53 with Latency-based routing policy to redirect to the lowest latency region and deploy the application into regions from where the heavy load is generating.
B.Migrate the application on S3 and use CloudFront edge locations to serve the requests.
C.Use DynamoDB global tables to replicate the data into multiple regions.
D.Deploy the ElastiCache to cache the requests to the DynamoDB table.
E.Use RDS with the Read Replicas into multiple regions, application servers will use the read replicas to serve the traffic.

Correct Answer: A, C, D
Option A is CORRECT because the AWS Route53 Latency-based routing will redirect the lowest latency region`s request to help serve the application faster.
Option B is INCORRECT because the AWS S3 can only be used for Static Website Hosting or Single Page Applications. However, in the current case, the application is a SaaS platform and the question mentions that the multi-page application is dynamic. CloudFront is suitable to serve requests from different regions. But as S3 is incorrect, this option is wrong.
Option C is CORRECT because the DynamoDB global tables provide replication capabilities. With global tables, you can have a fully managed, multi-region, and multi-master database that provides fast, local, read and write performance for massively scaled, global applications.
Option D is CORRECT because, in the current case, the size of the database is into petabytes. We can use ElasticCache to provide secure and fast performance.
Option E is INCORRECT because AWS RDS is a relational database service, and the application in the context is using the NoSQL database. It would require a significant engineering effort to re-design the application to fit the relational database and scale for such a huge amount of data.