
Ultimate access to all questions.
Deep dive into the quiz with AI chat providers.
We prepare a focused prompt with your quiz and certificate details so each AI can offer a more tailored, in-depth explanation.
A gaming company is building an application with Voice over IP capabilities. The application will serve traffic to users across the world. The application needs to be highly available with an automated failover across AWS Regions. The company wants to minimize the latency of users without relying on IP address caching on user devices.
What should a solutions architect do to meet these requirements?
A
Use AWS Global Accelerator with health checks.
B
Use Amazon Route 53 with a geolocation routing policy.
C
Create an Amazon CloudFront distribution that includes multiple origins.
D
Create an Application Load Balancer that uses path-based routing.
Explanation:
Why AWS Global Accelerator is the correct choice:
Global low latency routing: AWS Global Accelerator uses the AWS global network infrastructure to route user traffic to the optimal AWS endpoint based on health, geography, and routing policies. This minimizes latency for users worldwide.
Automated failover across AWS Regions: Global Accelerator provides automatic failover to healthy endpoints in different AWS Regions when health checks detect issues. This ensures high availability across regions.
Static IP addresses: Global Accelerator provides static IP addresses that act as a fixed entry point for applications. This eliminates the need for IP address caching on user devices, as users always connect to the same static IP addresses.
Health checks: Global Accelerator continuously monitors the health of application endpoints and automatically routes traffic only to healthy endpoints.
Why other options are incorrect:
B. Amazon Route 53 with geolocation routing: While Route 53 can route based on user location, it doesn't provide the same level of automated cross-region failover and doesn't use AWS's global network infrastructure to optimize routing. It also relies on DNS caching which can delay failover.
C. Amazon CloudFront with multiple origins: CloudFront is a content delivery network (CDN) optimized for caching static content. While it can route to multiple origins, it's not designed for real-time applications like VoIP and doesn't provide automated cross-region failover with health checks.
D. Application Load Balancer with path-based routing: ALB operates at the regional level and doesn't provide global routing capabilities. It cannot route traffic across different AWS Regions or minimize latency for global users.
Key requirements met by AWS Global Accelerator:
This solution is ideal for real-time applications like VoIP that require low latency and high availability across multiple regions.