What is the primary use case of a Secure Web Gateway (SWG) in BIG-IP APM deployments?

Question

Options

• ATo enforce access policies for specific user groups
• BTo protect resources from DDoS attacks
• CTo provide web filtering and content security services
• DTo enable Multi-Factor Authentication (MFA) for user logins

• A
  3% (1)
• B
  7% (2)
• C
  90% (26)

Explanation

A Secure Web Gateway (SWG) is specifically designed to inspect and filter outbound web traffic, enforcing acceptable use policies, blocking malicious URLs, and providing content categorization - making C correct. It sits between users and the internet to control what web content can be accessed, a classic proxy/content-security role.

Why the distractors are wrong:

• A (access policies for user groups) describes general APM policy enforcement - that's the broader APM engine, not the SWG component specifically.
• B (DDoS protection) belongs to BIG-IP AFM (Advanced Firewall Manager) or BIG-IP AWAF, not SWG.
• D (MFA) is an authentication feature handled by APM's authentication profiles and MFA integrations, not the gateway's filtering role.

Memory tip: Think of SWG as a security guard for web browsing - it watches what employees fetch from the internet and blocks bad content. The name itself is the clue: "Web Gateway" = traffic going to the web; "Secure" = filtered and safe.

No community discussion yet for this question.