101 · Question #625
in which scenario is a full proxy required?
The correct answer is A. When a separation between client and server connection .s needed. A full proxy is required when the client-side and server-side TCP connections must be completely isolated, allowing independent policy enforcement and optimization on each leg of the connection.
Question
in which scenario is a full proxy required?
Options
- AWhen a separation between client and server connection .s needed
- BWhen administration directly access the servers for administration
- Cwhen the server sends the response through Iho load balancer
- Dwhen all TCP client parameters must be seen by the server
How the community answered
(35 responses)- A89% (31)
- B6% (2)
- C3% (1)
- D3% (1)
Why each option
A full proxy is required when the client-side and server-side TCP connections must be completely isolated, allowing independent policy enforcement and optimization on each leg of the connection.
A full proxy terminates the inbound client TCP connection and establishes a separate, independent outbound TCP connection to the server. This separation enables applying different TCP profiles, security policies, and traffic optimizations to each side independently, which is the defining purpose of a full proxy architecture.
Direct administrative access to servers is a management topology concern that requires jump hosts or out-of-band access, not a full proxy architecture.
The server sending responses through the load balancer describes a basic routed or half-proxy return path, which does not require full connection termination and re-origination.
When the server must see all original TCP client parameters, a pass-through or transparent mode is needed - a full proxy deliberately hides client TCP parameters by re-originating the connection.
Concept tested: Full proxy architecture and connection separation requirement
Source: https://techdocs.f5.com/en-us/bigip-16-1-0/big-ip-local-traffic-management-basics/big-ip-local-traffic-management-basics.html
Topics
Community Discussion
No community discussion yet for this question.