A company has public EC2 application servers, each with an Elastic IP, and must perform firewall inspection on all internet traffic before it reaches the instances. A Gateway Load Balancer (GLB) and firewall fleet are deployed in a separate VPC. How should the network engineer modify the environment so internet traffic traverses the firewall fleet?

The correct solution involves using a Gateway Load Balancer Endpoint (GLB Endpoint) to direct internet-bound traffic through the firewall fleet. By provisioning a GLB Endpoint in the application VPC, traffic can be redirected. Associating a gateway route table with the Internet Gateway (IGW) and adding a route that sends traffic destined for the application subnet CIDR to the GLB Endpoint ensures all incoming internet traffic first goes through the GLB. The application subnet's default route must also point to the GLB Endpoint for return traffic and outbound initiated connections to be inspected. Incorrect options: Deploying a Transit Gateway is not necessary for this specific traffic flow and adds complexity. GLB Endpoints are designed for this direct integration. Adding a route for the application VPC's CIDR block in the firewall VPC does not correctly redirect incoming internet traffic from the IGW. Moving the GLB into the application VPC is not the standard or most scalable approach; the GLB Endpoint handles cross-VPC communication for inspection.