An application runs on EC2 instances behind an Application Load Balancer distributed across three Availability Zones. Customers require that the application be accessible via no more than two static IP addresses. What solution should the SysOps administrator implement?

AWS Global Accelerator provides static IP addresses that act as a fixed entry point to your application endpoints, including Application Load Balancers. By placing Global Accelerator in front of the ALB, you satisfy the requirement for no more than two static IP addresses, as Global Accelerator provides two static Anycast IP addresses by default. These IPs improve performance by directing user traffic to the optimal endpoint over the AWS global network. Deploying an internal Network Load Balancer behind the Application Load Balancer would not provide static public IP addresses for external access. Reducing the Application Load Balancer to operate in only two Availability Zones would decrease fault tolerance and still not provide static public IP addresses. Attaching Elastic IP addresses directly to an Application Load Balancer is not supported; ALBs automatically scale and use dynamic IP addresses.