What is a valid reason to configure the Custom mode for the TCP Proxy Profile?

The TCP Proxy Profile governs layer 4 connection handling. The "Custom" mode is used when the default TCP settings are not optimal for a specific application. A valid reason to use it is to tune performance parameters, such as changing the TCP idle timeout for applications that maintain long-lived but infrequent connections, preventing premature session termination by the load balancer. Other tunable parameters include buffer sizes and keepalive intervals.

B. Enabling SSL/TLS termination is configured in the Virtual Service settings via an SSL/TLS Profile, not the TCP Profile.

C. Switching between L4 and L7 is determined by the Application Profile (e.g., System-TCP-Proxy vs. System-HTTP), not the TCP Profile mode.

D. TCP Fast Path is a completely different, non-proxy L4 profile type, chosen instead of TCP Proxy, not as a customization of it.

1. VMware NSX Advanced Load Balancer Documentation, "Profiles". The TCP/UDP Profile section explains that these profiles "dictate the timeout, and other TCP-protocol-specific settings for a virtual service." Creating a custom profile is the method to alter these settings from the default.