Which combination of actions should a solutions architect take to improve availability and performance?
(Choose two.)
Create an accelerator using AWS Global Accelerator. Add the load balancers as endpoints.
Create an Amazon CloudFront distribution with an origin that uses Amazon Route 53 latency-based routing to route requests to the load balancers.
Configure two Application Load Balancers in each Region. The first will route to the EC2 endpoints and the second will route to the on-premises endpoints.
Configure a Network Load Balancer in each Region to address the EC2 endpoints. Configure a Network Load Balancer in each Region that routes to the on- premises endpoints.
Configure a Network Load Balancer in each Region to address the EC2 endpoints. Configure an Application Load Balancer in each Region that routes to the on-premises endpoints
Explanations:
AWS Global Accelerator improves the availability and performance of TCP-based workloads by routing traffic to the optimal endpoint based on health, geography, and routing policies. Adding load balancers as endpoints allows for efficient management of incoming traffic across multiple AWS Regions.
While Amazon CloudFront can improve performance by caching content, it is not ideal for stateful TCP-based workloads. The use of Route 53 for latency-based routing can enhance performance but does not address the stateful nature of the application effectively.
Configuring two Application Load Balancers (ALBs) in each region is not optimal for a stateful TCP-based workload, as ALBs are better suited for HTTP/S traffic. This setup may not handle TCP connections efficiently, especially with a stateful workload.
Network Load Balancers (NLBs) are suitable for TCP-based workloads due to their ability to handle millions of requests per second while maintaining ultra-low latencies. Configuring NLBs for both EC2 and on-premises endpoints ensures efficient routing for stateful traffic.
While NLBs are appropriate for the EC2 endpoints, using an Application Load Balancer for on-premises endpoints is not ideal for a stateful TCP-based workload. ALBs are designed for HTTP/S and do not manage TCP connections efficiently.