Exam AWS Certified Solutions Architect - Professional SAP-C02 topic 1 question 384 discussion

Answer is B not D. CloudFront does not work with NLB nor does it accept a fixed IP address A Standard accelerators automatically route traffic to a healthy endpoint that is nearest to your user. Since they're designed to load balance traffic, you can't deterministically route multiple users to a specific EC2 destination behind your accelerator. Custom routing accelerators allows you to do just that. Another difference is that standard routing accelerators support Network Load Balancers, Application Load Balancers, EC2 instances, and Elastic IPs as endpoints. Custom routing accelerators support only VPC subnet endpoints, each containing one or more EC2 instances that are running your application. https://aws.amazon.com/global-accelerator/faqs/#:~:text=A%3A%20Standard%20accelerators%20automatically%20route,you%20to%20do%20just%20that.

Option B Creating a Standard Accelerator with multiple endpoints, one for each additional region, allows you to provide static IP addresses that can be used by customers to allow lists. The Global Accelerator IP address is essentially a global IP address that points to an accelerator endpoint. This means that regardless of the customer's location, traffic will be routed to the nearest edge location (determined by AWS's latency algorithms), which is typically located in the closest region. By providing customers with the Global Accelerator IP address, you can ensure that they can access your application from anywhere in the world.

B is correct

D - With a custom routing accelerator, Global Accelerator does not route traffic based on the geoproximity or health of the endpoint. A and C - Though it may work but the IP address list keeps on changing and we can use this only in internal AWS implementations where we have access to the prefix list of Cloudfront IPs B is the correct answer

Option B is most appropriate here because requirement is to route the customer to closest region and not to specific EC2 instance. Option D provides custom routing that is not required in this case.

https://aws.amazon.com/blogs/networking-and-content-delivery/introducing-aws-global-accelerator-custom-routing-accelerators/

Answer B. For standard accelerators, the endpoints are Network Load Balancers, Application Load Balancers, Amazon EC2 instances, or Elastic IP addresses. For custom routing accelerators, the endpoints are virtual private cloud (VPC) subnets with one or more EC2 instances.

standard

B for sure

Answer: B