Which two things will happen to application traffic based on the GWLB deployment?

A customer has implemented GWLB between the partner and application VPCs. FortiGate appliances are deployed in the partner VPC with multiple AZs to inspect traffic transparently.

Which two things will happen to application traffic based on the GWLB deployment? (Choose two.)
A . Inbound and outbound traffic will go to multiple devices, which will perform load balancing.
B . Inbound and outbound traffic will go to the same device, which will perform stateful processing.
C . The content of the original traffic exchanged between the GWLB and FortiGate will be preserved.
D . The original traffic exchanged between the GWLB and FortiGate will be hashed for data integrity.

Answer: A, B

Explanation:

Understanding Gateway Load Balancer (GWLB):

GWLB is designed to distribute traffic across multiple appliances for both inbound and outbound traffic, providing scalability and high availability.

Traffic Load Balancing:

GWLB can send traffic to multiple FortiGate appliances for load balancing purposes, ensuring efficient use of resources (Option A).

Stateful Processing:

For stateful processing, GWLB ensures that traffic flows (both inbound and outbound) for a given connection are directed to the same FortiGate appliance. This maintains session integrity (Option B). Preservation and Hashing of Traffic:

Options C and D are incorrect as they suggest incorrect behavior regarding traffic content preservation and hashing for data integrity, which are not primary functions of GWLB.

Reference: AWS Gateway Load Balancer Documentation: AWS Gateway Load Balancer

FortiGate Integration with GWLB: Fortinet Documentation