What is the key difference between transparent and explicit proxy deployments in Secure Web Gateway (SWG)?

Question

Options

• ATransparent proxy does not require user configuration, while explicit proxy requires user settings.
• BTransparent proxy provides faster performance, while explicit proxy offers better security.
• CTransparent proxy requires client-side installation, while explicit proxy is fully server-side.
• DTransparent proxy is suitable for encrypted traffic, while explicit proxy is limited to HTTP traffic.

• A
  90% (35)
• B
  3% (1)
• C
  5% (2)
• D
  3% (1)

Explanation

Option A is correct because the defining characteristic of a transparent proxy is that it intercepts traffic without any configuration on the client - users and devices are unaware it exists. An explicit proxy, by contrast, requires the client to be configured (via browser settings, PAC files, or GPO) to point traffic at the proxy.

Why the distractors are wrong:

• B is false - performance and security trade-offs are not the defining distinction between these two deployment models; both can be equally secure.
• C reverses reality - transparent proxies require network-level infrastructure (e.g., routing or WCCP) to intercept traffic, not client-side installation; explicit proxies just need a config setting, not a server-side-only architecture.
• D is false - neither proxy type is inherently limited to HTTP; both can handle HTTPS (with SSL inspection configured), and transparent proxies actually face more difficulty with encrypted traffic due to certificate trust challenges.

Memory tip: Think of "transparent" as invisible to the user - like a one-way mirror. "Explicit" means you have to explicitly tell the client where to send traffic. If the user has to configure it, it's explicit; if they don't know it's there, it's transparent.

No community discussion yet for this question.