NSE7 Enterprise Firewall and VDOMs Practice Question
An administrator configures inter-VDOM routing between VDOM-A and VDOM-B using a VDOM link. After configuration, traffic from VDOM-A cannot reach VDOM-B. Which configuration step is MOST likely missing?
⚠ Common exam trap
It's easy for candidates to assume static routes or a global inter-VDOM routing toggle are required, overlooking that VDOM links function like physical interfaces and need firewall policies to permit traffic.
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
✓
Create a firewall policy on VDOM-A and VDOM-B allowing traffic over the VDOM link interface
VDOM links are special inter-VDOM interfaces that require firewall policies on both VDOMs to permit traffic. Without a policy on VDOM-A and VDOM-B that allows traffic over the VDOM link interface, packets will be dropped by the implicit deny rule. This is the most common missing step when inter-VDOM routing fails.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✓
Create a firewall policy on VDOM-A and VDOM-B allowing traffic over the VDOM link interface
Why this is correct
A VDOM link provides the physical path, but FortiGate evaluates inter-VDOM traffic through firewall policies. Without policies on both VDOM-A and VDOM-B permitting traffic across the link interface, packets are dropped, which explains why connectivity fails despite the link existing.
- ✗
Enable 'inter-vdom-routing' under system settings
Why it's wrong here
FortiGate has no global 'inter-vdom-routing' toggle; VDOM links are created and interfaces assigned, with routing configured per VDOM. It is tempting because feature-enable commands are common elsewhere, but the actual missing step is normally an interface or route, and such a toggle would be correct only if FortiOS exposed one.
- ✗
Configure a static route on VDOM-A pointing to VDOM-B's subnet via the VDOM link
Why it's wrong here
A static route via the VDOM link is typically required, but the stem says the link is configured and traffic still fails, so the more fundamental omission is usually the interface IP or link membership. It is tempting because routing is genuinely needed, and this would be correct if the link interfaces already had addresses and were assigned.
- ✗
Assign both VDOM link interfaces to the same VDOM
Why it's wrong here
Each end of a VDOM link must belong to a different VDOM; placing both interfaces in one VDOM defeats the link entirely. It is tempting because interface-to-VDOM assignment is a real step, but the correct configuration puts one interface in VDOM-A and the other in VDOM-B, which is what enables forwarding between them.
Visual reference
Go deeper
Related to this question
About these practice questions
One of 718 original NSE7 practice questions on Courseiva, each with a full explanation and wrong-answer analysis — not exam dumps or protected exam content. 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.