101 · Question #530
In which scenario is a packet forwarding architecture required?
The correct answer is C. when the server responds directly to the client. A packet forwarding (Direct Server Return) architecture is required when the server must respond directly to the client without returning traffic through the load balancer.
Question
In which scenario is a packet forwarding architecture required?
Options
- Awhen HTTP header must be modified
- Bwhen cookie persistency is demanded
- Cwhen the server responds directly to the client
- Dwhen the number of TCP connections on the server should be reduced
How the community answered
(38 responses)- A5% (2)
- B3% (1)
- C84% (32)
- D8% (3)
Why each option
A packet forwarding (Direct Server Return) architecture is required when the server must respond directly to the client without returning traffic through the load balancer.
Modifying HTTP headers requires full proxy mode where the load balancer can inspect and rewrite Layer 7 content, not a packet forwarding approach.
Cookie persistence requires the load balancer to inspect and insert HTTP cookies, which is only possible in a full proxy or HTTP profile mode, not packet forwarding.
In a packet forwarding or Direct Server Return (DSR) architecture, the load balancer only intercepts inbound client requests and forwards packets without NATing the destination IP, allowing backend servers to reply directly to clients using the virtual IP as the source. This bypasses the load balancer on the return path, which is the defining characteristic and primary use case for this architecture.
Reducing TCP connections on the server (connection multiplexing or OneConnect) is a full proxy feature that requires the load balancer to terminate and manage TCP sessions, the opposite of packet forwarding.
Concept tested: Direct Server Return packet forwarding architecture use case
Source: https://my.f5.com/manage/s/article/K7820
Topics
Community Discussion
No community discussion yet for this question.