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:
Configuring Network Load Balancers (NLBs) for the on-premises endpoints allows for efficient UDP traffic handling. Using AWS Global Accelerator enhances performance and availability by routing traffic to the optimal NLB based on latency. A CNAME pointing to the accelerator DNS simplifies access while adhering to compliance requirements since the application remains on-premises.
Application Load Balancers (ALBs) are designed for HTTP/HTTPS traffic and do not efficiently support UDP-based applications. Thus, using ALBs in this scenario is not suitable for the company’s requirements for a UDP-based application.
While configuring NLBs is appropriate for UDP traffic, creating a CloudFront distribution as an origin does not align with UDP protocols, as CloudFront primarily handles HTTP/S traffic. This would not effectively improve performance or meet the application’s compliance and operational needs.
Similar to option B, using Application Load Balancers (ALBs) is not suitable for a UDP-based application. Additionally, the use of CloudFront as an origin is not appropriate for UDP traffic, leading to a misalignment with the application requirements and performance goals.