What should a solutions architect do to provide path-based routing to send the traffic to the correct group of servers?
Route all traffic to an internet gateway. Configure pattern matching rules at the internet gateway to route traffic to the group of servers supporting that path.
Route all traffic to a Network Load Balancer (NLB) with target groups for each group of servers. Use pattern matching rules at the NLB to route traffic to the correct target group.
Route all traffic to an Application Load Balancer (ALB). Configure path-based routing at the ALB to route traffic to the correct target group for the servers supporting that path.
Use Amazon Route 53 as the DNS server. Configure Route 53 path-based alias records to route traffic to the correct Elastic Load Balancer for the group of servers supporting that path.
Explanations:
An internet gateway does not support path-based routing. It is designed for routing traffic to instances in a VPC, but it cannot apply rules based on URL paths. Therefore, this option does not meet the requirement for path-based routing.
A Network Load Balancer (NLB) can route traffic to target groups based on TCP/UDP connections but does not support path-based routing based on URL paths. This means that it cannot direct traffic to different server groups based on the request path, which is necessary for this scenario.
An Application Load Balancer (ALB) is specifically designed to handle HTTP/HTTPS traffic and supports advanced routing features, including path-based routing. It can route traffic to different target groups based on the URL path, making it the ideal solution for the described requirement.
Amazon Route 53 does not support path-based routing. It can direct traffic to different endpoints based on domain names or subdomains, but not based on URL paths. Therefore, this option cannot fulfill the requirement for path-based routing to different server groups.