What should a solutions architect do to meet these requirements?
Configure three Network Load Balancers (NLBs) in the three AWS Regions to address the on-premises endpoints. Create an accelerator by using AWS Global Accelerator, and register the NLBs as its endpoints. Provide access to the application by using a CNAME that points to the accelerator DNS.
Configure three Application Load Balancers (ALBs) in the three AWS Regions to address the on-premises endpoints. Create an accelerator by using AWS Global Accelerator, and register the ALBs as its endpoints. Provide access to the application by using a CNAME that points to the accelerator DNS.
Configure three Network Load Balancers (NLBs) in the three AWS Regions to address the on-premises endpoints. In Route 53, create a latency-based record that points to the three NLBs, and use it as an origin for an Amazon CloudFront distribution. Provide access to the application by using a CNAME that points to the CloudFront DNS.
Configure three Application Load Balancers (ALBs) in the three AWS Regions to address the on-premises endpoints. In Route 53, create a latency-based record that points to the three ALBs, and use it as an origin for an Amazon CloudFront distribution. Provide access to the application by using a CNAME that points to the CloudFront DNS.
Explanations:
This option uses Network Load Balancers (NLBs) to address on-premises endpoints, which is suitable for UDP-based applications. AWS Global Accelerator improves performance and availability by directing traffic to the nearest NLB based on latency, while the CNAME pointing to the accelerator DNS ensures a single entry point for users.
This option uses Application Load Balancers (ALBs), which are not designed for UDP traffic. ALBs are primarily for HTTP/HTTPS applications and do not support UDP, making them unsuitable for this scenario.
While this option correctly uses Network Load Balancers for UDP traffic, using Amazon CloudFront as an origin is not suitable since CloudFront primarily supports HTTP/HTTPS traffic. Thus, it does not align with the needs of a UDP-based application.
Similar to option B, this option utilizes Application Load Balancers (ALBs) which do not support UDP traffic. Furthermore, using CloudFront as an origin for ALBs is not effective for a UDP application, making it an unsuitable solution.
I weigh that the answer is:
Configure three Network Load Balancers (NLBs) in the three AWS Regions to address the on-premises endpoints. Create an accelerator by using AWS Global Accelerator, and register the NLBs as its endpoints. Provide access to the application by using a CNAME that points to the accelerator DNS.