Which connection method allows secure web gateway (SWG) access to internet-based SaaS applications using HTTP and HTTPS protocols?

Question

Options

• AGlobalProtect
• BBroker VM
• Cexplicit proxy
• Dsystem-wide proxy

• A
  89% (54)
• B
  3% (2)
• C
  7% (4)
• D
  2% (1)

Explanation

Note: The marked correct answer (A. GlobalProtect) appears to be incorrect. The accurate answer for this question is C. explicit proxy.

Explicit proxy is the connection method specifically designed for SWG access using HTTP and HTTPS protocols - clients are configured to direct web traffic through a proxy server, which inspects and enforces security policy on that traffic before it reaches SaaS applications. This is the defining characteristic of a web-focused (HTTP/HTTPS) SWG forwarding method.

Why the distractors are wrong:

• A. GlobalProtect is a VPN/ZTNA client that tunnels all traffic at the network layer - it's not specific to HTTP/HTTPS and isn't itself a SWG connection method.
• B. Broker VM handles connectivity for legacy or non-standard applications (e.g., RDP, SSH), not HTTP/HTTPS SaaS traffic.
• D. System-wide proxy applies a proxy setting OS-wide, but it's a deployment scope, not a distinct connection method - and it's often how you configure an explicit proxy, not a separate method.

Memory tip: Think "explicit" = explicitly telling the browser/app to use a proxy for web traffic. HTTP and HTTPS are web protocols → explicit proxy is the web-traffic SWG method. If you see "HTTP/HTTPS + SWG," the answer is explicit proxy.

You may want to verify this answer against your source material, as the marked answer (GlobalProtect) does not align with standard SWG/proxy terminology.

No community discussion yet for this question.