Design for New Solutions II
Explore advanced AWS architectural designs addressing global latency-sensitive services, multi-account backup governance, warm-standby disaster recovery, robust edge security, and secure private subnet networking. Understand practical solutions for reducing failover time, enforcing long-term encrypted backups, automating disaster recovery tests, layering defenses against web attacks, and controlling outbound API traffic without public internet exposure.
We'll cover the following...
Question 26
A global gaming company is building a latency-sensitive TCP and WebSocket service in two AWS Regions. Mobile clients aggressively cache DNS responses, and the company needs Regional failover in less than 30 seconds without requiring clients to resolve a new DNS answer. Which traffic management design should the company use?
A. Use Amazon Route 53 failover routing with a 1-second TTL and rely on client retry logic to pick up the new DNS answer during a Regional outage.
B. Use Amazon CloudFront origin failover for all TCP and WebSocket traffic and configure the secondary Region as the failover origin.
C. Use a Multi-AZ Network Load Balancer in one Region and depend on the load balancer to route around any Regional failure.
D. Use AWS Global Accelerator with static anycast IP addresses, endpoint groups in both Regions, health checks against Application Load Balancer or Network Load Balancer endpoints, optional traffic dials, and a data layer replicated across Regions.
Question 27
A health care organization is creating a new multi-account platform with moderate ...