Which AWS Service Improves Performance for Apps Behind ALBs?

Why the Answer Is Correct

AWS Global Accelerator gives an application two static anycast IP addresses that onboard traffic at the nearest AWS edge location and then carry it over the AWS global network, avoiding much of the public internet's latency and jitter. It natively supports Application Load Balancers as endpoints, so the existing ALB-fronted public applications gain a measurable performance improvement without re-architecting the application. It also adds fast regional failover, which further supports availability and performance for public-facing workloads. Because the requirement is squarely about improving the performance of applications sitting behind ALBs, Global Accelerator is the direct architectural fit.

Why the Other Options Are Wrong

Amazon Connect is a cloud contact-center service and has no role in accelerating web application traffic. Amazon ElastiCache improves performance only at the data tier by caching frequently read data, which requires application code changes and does not shorten the network path for users hitting an ALB. Amazon CloudWatch provides monitoring, metrics, and alarms; it can tell you that performance is poor, but it cannot make the traffic faster. None of these three address the network-level latency of public applications the way Global Accelerator does.

Community Comment Notes

Every learner comment converges on Global Accelerator: Nikmah restates the AWS description almost verbatim, noting it can "Improve global application availability and performance using the AWS global network," while babycute999 and ShaiTay reduce the reasoning to the keyword "Improve performance" pointing at option A. The shared logic is that a network acceleration service, not a cache or a monitoring tool, is what improves delivery of public apps sitting behind ALBs. That reasoning matches the service documentation, so the unanimous pick is sound rather than a case of following the vote.