AWS Certified Solutions Architect Professional SAP-C02 Practice Question
A global media company operates a real-time video-streaming service with backend infrastructure deployed on EC2 instances behind Network Load Balancers (NLBs) in the us-east-1, eu-central-1, and ap-southeast-2 Regions. The service uses a custom TCP-based protocol for streaming. Users connect to the geographically closest regional endpoint by means of DNS-based routing.
The company is experiencing two major issues:
Some corporate clients have strict firewall egress rules and struggle to whitelist the multiple static public IP addresses that each regional NLB exposes (one per Availability Zone and Region).
During a recent service impairment in one Region, users were not automatically routed to a healthy Region, resulting in a significant outage for a large user segment.
The company wants to implement a solution that provides static entry points for the application and improves availability with fast, automatic cross-Region failover. Which solution best meets these requirements?
Use Amazon Route 53 with a combination of latency-based routing and failover routing policies. Configure health checks for each regional NLB.
Deploy an AWS Global Accelerator and configure each regional NLB as an endpoint in its respective endpoint group.
Establish AWS Direct Connect connections to each AWS Region and use a Direct Connect gateway for inter-Region failover.
Configure an Amazon CloudFront distribution with the regional NLBs as custom origins and use a CloudFront Function to manage failover between origins.
Deploying AWS Global Accelerator is the best solution. Global Accelerator allocates two static anycast IP addresses that serve as fixed entry points, simplifying firewall whitelisting for corporate clients. It supports both TCP and UDP, so it works with the company's custom TCP-based streaming protocol. Because Global Accelerator operates at the network layer and continuously health-checks all registered regional endpoints, traffic is automatically and almost immediately redirected to the nearest healthy Region-without waiting for DNS TTLs to expire.
Incorrect answers:
Amazon CloudFront is optimized for HTTP/HTTPS and WebSocket traffic and cannot proxy an arbitrary TCP-based streaming protocol.
Amazon Route 53 can perform DNS-based latency or failover routing, but failover depends on DNS TTLs and client caches, and it still exposes many NLB IP addresses that clients must whitelist.
AWS Direct Connect is a private network service for on-premises connectivity and does not provide global static IPs or cross-Region failover for public internet users.
Ask Bash
Bash is our AI bot, trained to help you pass your exam. AI Generated Content may display inaccurate information, always double-check anything important.
What is AWS Global Accelerator and why is it suited to this scenario?
Open an interactive chat with Bash
How does AWS Global Accelerator ensure faster failover compared to Route 53?
Open an interactive chat with Bash
Why is Amazon CloudFront not a good fit for the custom TCP-based streaming protocol in this scenario?
Open an interactive chat with Bash
AWS Certified Solutions Architect Professional SAP-C02
Continuous Improvement for Existing Solutions
Your Score:
Report Issue
Bash, the Crucial Exams Chat Bot
AI Bot
Loading...
Loading...
Loading...
IT & Cybersecurity Package Join Premium for Full Access