You are part of the IT team of a streaming application. Your application is hosted in two separate regions, us-east-1(N Virginia) and ap-south-1 (Mumbai). Your application recently became very popular, and now you have users from all around the world. However, these new users have been experiencing high latency in the application. How can you solve this problem, keeping in mind that possible failovers in the app need to be solved very quickly?
 

Answer options:

A.Enable a DNS-based traffic management solution with Geolocation route policies in Route53.
B.Enable AWS WAF to securely serve your application content to the nearest Edge Locations to the users.
C.Enable Global Accelerator endpoint for your two regions.
D.Enable Direct Connect.

Answer: C
Option A is incorrect because if there is a failover, you will need to modify the source application`s IP address or configure Route53 records. That will take time to solve the failover. More details please check https://docs.aws.amazon.com/Route53/latest/DeveloperGuide/routing-policy.html#routing-policy-geo.
Option B is incorrect because AWS WAF is a service to protect applications from attacks. It does not help to improve the performance or reduce latency.
Option C is CORRECT because AWS Global Accelerator is a service that redirects users requests to the nearest edge location and then routes the data to the Amazon global network, increasing the speed and security of data transfer, therefore, increasing the performance of our applications. It also reroutes requests to healthy IPs if it fails and changes propagations. It is automatic and lasts some seconds. More details please check https://aws.amazon.com/global-accelerator/faqs/.
Option D is incorrect because Direct Connect is a service used to increase data transfer between On-Premise data centers and AWS services. More details: https://aws.amazon.com/directconnect/.
Here is the additional explanation on AWS website on Global accelerator FAQ. Why DNS/Route 53 is an inferior option as compared to Global accelerator.
Q: How is AWS Global Accelerator different from a DNS-based traffic management solution?
A: First, some client devices and internet resolvers cache DNS answers for long periods of time. So when you make a configuration update, or there’s an application failure or change in your routing preference, you don’t know how long it will take before all of your users receive updated IP addresses. With AWS Global Accelerator, you don’t have to rely on the IP address caching settings of client devices. Change propagation takes a matter of seconds, which reduces your application downtime. Second, with Global Accelerator, you get static IP addresses that provide a fixed entry point to your applications. This lets you easily move your endpoints between Availability Zones or between AWS Regions, without having to update the DNS configuration or client-facing applications.