Exam AWS Certified SysOps Administrator - Associate topic 1 question 403 discussion

"For IPv4, Global Accelerator provides two global static IPv4 addresses". https://docs.aws.amazon.com/global-accelerator/latest/dg/about-accelerators.eip-accelerator.html

When you create an Application Load Balancer or Network Load Balancer in the AWS Management Console, you can optionally add an accelerator at the same time. Elastic Load Balancing and Global Accelerator work together to transparently add the accelerator for you. The accelerator is created in your account, with the load balancer as an endpoint. Using an accelerator provides static IP addresses and improves the availability and performance of your applications.

I choose A, although at first was hesitating between A and D Why not D - Cannot assign Elastic IP address (static IP address) to ALB To assign static IP to ALB, there are 2 options: 1. Register ALB as a target of NLB to forward traffic from NLB to ALB, as Network Load Balancer can be assigned one Elastic IP address for each Availability Zone it uses. WHY NOT B - NLB has to be in front of ALB, not behind it 2. Use AWS Global Accelerator to get static IP addresses that act as a fixed entry point to your application endpoints - this is option A https://aws.amazon.com/blogs/networking-and-content-delivery/using-aws-lambda-to-enable-static-ip-addresses-for-application-load-balancers/ https://aws.amazon.com/blogs/networking-and-content-delivery/improving-availability-and-performance-for-application-load-balancers-using-one-click-integration-with-aws-global-accelerator/

B is correct. You can't assign a static IP address to an Application Load Balancer. If your Application Load Balancer requires a static IP address, then it's a best practice to register it behind a Network Load Balancer. The static IP address that's assigned to a Network Load Balancer doesn't change and provides a fixed entry point for your Application Load Balancer. https://repost.aws/knowledge-center/alb-static-ip

I think it is either A or D