A company deployed a web application on EC2 instances behind an Application Load Balancer (ALB) in an Auto Scaling group. Enterprise customers worldwide will use the app; their employees connect via HTTPS from office locations. Those corporate firewalls only allow outbound traffic to approved IP addresses. Employees must access the app with minimal latency. What infrastructure change should the network engineer make?

AWS Global Accelerator is the best solution because it uses the AWS global network to route user traffic to the nearest edge location, then through the AWS backbone to the ALB. This significantly reduces latency for a global user base and provides static IP addresses for the corporate firewalls to whitelist. Creating an NLB in front of an ALB is unnecessary and doesn't address global latency or static IP requirements. CloudFront is for caching static content and doesn't directly optimize dynamic application traffic globally in the same way Global Accelerator does, nor does it provide static IPs for whitelisting. Route 53 is a DNS service and while essential, it only resolves domain names to IP addresses; it doesn't optimize network paths or provide static IPs for firewall whitelisting.