What is the correct command to configure a Content Switching virtual server for implementing Secure Web Gateway in transparent proxy mode?

• A. add cs vserver swgVS PROXY 192.168.10.1 80 -Authn401 on -authnVsName explicit-auth-vs
• B. add cs vserver swgVS PROXY ** -Authn401 on -authnVsName explicit-auth-vs
• C. add cs vserver swgVS PROXY 192.168.10.1 -Authn401 on -authnVsName transparent-auth-vs
• D. add cs vserver swgVS PROXY * 21 -Authn401 on -authnVsName transparent-auth-vs

Answer: (B)

In this scenario, the key idea is that a Content Switching vserver for Secure Web Gateway in transparent proxy mode must be able to receive traffic from any interface, so it uses a wildcard IP binding rather than a specific address. The command creates a CS vserver of type PROXY that listens on all interfaces (wildcard) and enables authentication on 401 by pointing to an explicit authentication virtual server. Using an explicit authentication flow fits the SWG use case, where users are prompted to log in through a designated authentication VS before access is allowed.

Binding to a concrete internal IP or port would constrain the vserver to a single path, which defeats the purpose of transparent proxy, and choosing a different authentication virtual server type would change how user credentials are collected. The wildcard binding with explicit-auth-vs aligns with the transparent proxy behavior and the expected login flow for SWG.