Which three Web filtering deployment actions are supported by Junos? (Choose three.)

Junos OS supports three primary methods for deploying Web filtering on SRX Series devices. These are:

1. Local Web Filtering: This method uses user-defined lists (blocklists and allowlists) configured directly on the device to control access to specific websites.

2. Websense Redirect: This is an integrated third-party solution where the Junos device redirects HTTP requests to a dedicated external Websense server, which then performs the filtering and enforces policy.

3. Juniper Enhanced Web Filtering: This is a subscription-based, cloud-hosted solution. The Junos device queries a large, dynamically updated Juniper database in the cloud to categorize and filter web traffic.

These three options represent the distinct deployment actions available for this feature.

A. Use IPS: Intrusion Prevention System (IPS) is a separate Unified Threat Management (UTM) feature that inspects traffic for malicious signatures and anomalies, not a method for deploying URL-based Web filtering.

C. Use remote lists: This term is too generic. While both Websense and Juniper Enhanced Web Filtering use remote resources, they are specific, distinct implementations. The official documentation categorizes them separately, not under a general "remote lists" heading.

1. Juniper Networks TechLibrary

UTM Web Filtering Feature Guide for Security Devices: This official guide explicitly details the three supported types of Web filtering.

URL: https://www.juniper.net/documentation/us/en/software/junos/utm/topics/concept/utm-web-filtering-understanding.html

Details: The "Types of Web Filtering" section states

"Junos OS supports the following types of Web filtering: Local Web filtering

Juniper enhanced Web filtering

and Websense redirect Web filtering." This directly validates options B

D

and E.