ANS-C01 · Question #238
An online retail company is running a web application in the us-wast-2 Region and serves consumers in the United States. The company plans to expand across several countries in Europe and wants to…
The correct answer is C. Configure an Application Load Balancer (ALB) for the application in each environment in the new. Explanation Option C is correct because AWS Global Accelerator with an Application Load Balancer (ALB) is the ideal combination here: Global Accelerator provides static anycast IP addresses (enabling IP identification and sub-minute failover for both GET and POST methods via…
Question
An online retail company is running a web application in the us-wast-2 Region and serves consumers in the United States. The company plans to expand across several countries in Europe and wants to provide low latency for all its users. The application needs to identify the users' IP addresses and provide localized content based on the users' geographic location. The application uses HTTP GET and POST methods for its functionality. The company also needs to develop a failover mechanism that works for GET and POST methods and is based on health checks. The failover must occur in less than 1 minute for all clients. Which solution will meet these requirements?
Options
- AConfigure a Network Load Balancer (NLB) for the application in each environment in the new
- BConfigure an Application Load Balancer (ALB) for the application in each environment in the new
- CConfigure an Application Load Balancer (ALB) for the application in each environment in the new
- DConfigure a Network Load Balancer (NLB) for the application in each environment in the new
How the community answered
(58 responses)- A16% (9)
- B34% (20)
- C43% (25)
- D7% (4)
Explanation
Explanation
Option C is correct because AWS Global Accelerator with an Application Load Balancer (ALB) is the ideal combination here: Global Accelerator provides static anycast IP addresses (enabling IP identification and sub-minute failover for both GET and POST methods via health checks), while ALB supports HTTP-layer routing needed for geographic content localization and handles both GET and POST methods at the application layer.
Why the distractors are wrong:
- Option A & D (NLB): Network Load Balancers operate at Layer 4 (TCP/UDP) and cannot inspect HTTP headers or perform the application-layer routing needed for geographic content customization based on user location. NLB is optimized for raw TCP traffic, not HTTP-aware routing.
- Option B (ALB without Global Accelerator): An ALB alone lacks the global anycast network required to achieve low latency across multiple continents and cannot guarantee failover in under 1 minute for geographically dispersed users without Global Accelerator's health-check-driven traffic steering.
Memory Tip: Think "GAP" - Global Accelerator + ALB = Performance. Whenever you see requirements for global low latency + IP identification + fast failover + HTTP methods, Global Accelerator paired with ALB is your go-to combination. NLB is for speed at Layer 4, not for HTTP-aware, geo-based routing.
Topics
Community Discussion
No community discussion yet for this question.