NSE7 Enterprise Firewall and VDOMs Practice Question
An administrator has a FortiGate 600E running multiple VDOMs. The administrator wants to ensure that when a VDOM is deleted, all associated firewall policies, addresses, and routes are also removed to avoid orphaned objects. Which action should the administrator take?
⚠ Common exam trap
The trap here is assuming that a global setting or manual cleanup is needed, when FortiOS automatically handles object deletion upon VDOM removal.
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
✓
Ensure the VDOM is not in use by any inter-VDOM links or management services, then delete it; associated objects are removed automatically.
Deleting a VDOM in FortiOS automatically removes all associated configuration objects, but you must first eliminate dependencies like inter-VDOM links. This ensures no orphaned objects remain. The other options either invent non-existent settings, suggest unnecessary manual steps, or propose inefficient workarounds that do not align with FortiGate's native behavior.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✓
Ensure the VDOM is not in use by any inter-VDOM links or management services, then delete it; associated objects are removed automatically.
Why this is correct
When you delete a VDOM on a FortiGate, FortiOS automatically deletes all configuration objects that belong to that VDOM, including firewall policies, addresses, and routes. However, you must first remove any dependencies such as inter-VDOM links or management services that reference the VDOM. This ensures a clean deletion without orphaned objects.
- ✗
Enable the 'vdom-delete-cascade' setting under system global.
Why it's wrong here
The 'vdom-delete-cascade' setting does not exist in FortiOS. VDOM deletion behavior is not controlled by a global setting. The FortiGate automatically handles object cleanup when a VDOM is deleted, so no additional configuration is required. This option is a distractor because it invents a non-existent command.
- ✗
Export the VDOM configuration, delete the VDOM, then re-import the configuration without the unwanted objects.
Why it's wrong here
Exporting and re-importing is not required because FortiOS automatically cleans up VDOM-specific objects upon deletion. This approach adds unnecessary complexity and risk of misconfiguration. It does not address the core behavior of automatic object removal and is not a recommended practice for VDOM deletion.
- ✗
Manually delete all firewall policies, addresses, and routes in the VDOM before deleting the VDOM.
Why it's wrong here
Manual deletion is unnecessary because FortiOS automatically removes all configuration objects associated with a VDOM when the VDOM is deleted. Requiring manual cleanup would be error-prone and is not how FortiGate operates. This option describes a redundant and impractical process that does not reflect actual FortiGate behavior.
Go deeper
Related to this question
About these practice questions
This NSE7 question is part of Courseiva's 718-question bank — original exam-style content with full explanations and wrong-answer analysis, never real exam questions or exam dumps. Learn why practice questions differ from exam dumps →
JA
Written and reviewed by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
Last reviewed September 2026 · checked against the official Fortinet exam blueprint
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.