NSE7 Enterprise Firewall and VDOMs Practice Question
An enterprise deploys a FortiGate in transparent mode to bridge two broadcast domains. The administrator needs to apply a web filter to HTTP traffic between these domains. Which configuration is required?
⚠ Common exam trap
Many candidates think web filter profiles can be applied directly to interfaces (like in NAT/route mode) or that global settings enable filtering, but in transparent mode, all Layer 7 inspection must be configured via security policies with the bridge interface as both source and destination.
Answer choices
Why each option matters
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Configure a security policy with source and destination interfaces as the bridge, action ACCEPT, and a web filter profile
In transparent mode, FortiGate bridges traffic at Layer 2, so security policies must use the bridge interface as both source and destination. Option B correctly configures a security policy with source and destination interfaces set to the bridge, action ACCEPT, and a web filter profile applied. This allows the FortiGate to inspect HTTP traffic between the two broadcast domains and apply the web filter.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Apply the web filter profile directly to the bridge interface
Why it's wrong here
In transparent mode, web filtering is applied through a firewall policy, not attached to the bridge interface; interfaces carry no security profiles. It is tempting because the bridge interface is the visible data path between the broadcast domains, but profile attachment belongs to policies that permit the traffic.
- ✓
Configure a security policy with source and destination interfaces as the bridge, action ACCEPT, and a web filter profile
Why this is correct
In transparent mode the FortiGate forwards frames between bridged interfaces, so the policy must reference the bridge interface pair. Attaching the web filter profile to that ACCEPT policy enforces filtering on HTTP crossing the two broadcast domains.
- ✗
Enable web filtering globally under Config -> Features
Why it's wrong here
Global feature toggles only expose web-filter menus; they do not create the firewall policy that inspects HTTP crossing a transparent bridge. The filter must be attached to a policy permitting the bridged traffic. Enabling features globally suits profiles applied by existing policies, not a scenario lacking any policy to bind them to.
- ✗
Create a policy with action SET_PERMIT and enable web filtering
Why it's wrong here
SET_PERMIT is an IPsec phase 1 action, not a firewall policy action; policies use ACCEPT or DENY, and web filtering attaches to an ACCEPT policy. It is tempting because SET_PERMIT sounds like an allow action, but it belongs to VPN tunnel negotiation, not traffic inspection.
Visual reference
Go deeper
Related to this question
About these practice questions
Courseiva writes every NSE7 question from scratch — 718 in total, each with an explanation and a wrong-answer breakdown. None are copied from real exams or dumps. Learn why practice questions differ from exam dumps →
JA
Written by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
This NSE7 practice question is part of Courseiva's free Fortinet certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the NSE7 exam.