An operator is configuring a TCP/UDP Profile of type "TCP Proxy" for an application. What are two valid reasons to configure the Custom mode for the TCP Proxy Settings? (Choose two.)

Question

Options

• AExpose client destination TCP port to the application
• BStatically configure the Receive Window
• CDisable Source Network Address Translation (SNAT)
• DChange the Idle Duration timeout
• EEnable Port Address Translation (PAT)

• A
  16% (7)
• B
  71% (32)
• C
  9% (4)
• D
  4% (2)

Explanation

Switching a TCP Proxy profile to Custom mode unlocks TCP parameters that are either locked or auto-managed in the default mode. Option B is correct because Custom mode lets you statically set the TCP Receive Window size - overriding the auto-tuning behavior - which matters for applications with specific throughput or latency requirements. Option E is correct because Custom mode exposes the ability to enable Port Address Translation (PAT), which remaps source ports and is not configurable in the standard mode.

The distractors are wrong for these reasons: A (exposing client destination port) is controlled at the virtual server or application policy level, not within the TCP profile's custom settings; C (disabling SNAT) is configured at the NAT/virtual server level, entirely separate from the TCP profile; D (Idle Duration timeout) is a basic setting available in the default mode - you do not need Custom mode to change it.

Memory tip: Think "Buffer size and Port rewriting" - the two things Custom mode uniquely gives you are fine-grained buffer/window control (B) and port translation control (E/PAT). Anything involving SNAT, idle timers, or port exposure belongs to a different layer of configuration.

No community discussion yet for this question.