NSE4_FGT-7.0 · Question #173
Which downstream FortiGate VDOM is used to join the Security Fabric when split-task VDOM is enabled on all FortiGate devices?
The correct answer is A. Root VDOM. When split-task VDOM is enabled on FortiGate devices, the Root VDOM is responsible for joining the Security Fabric and managing global device settings. This VDOM handles management tasks, while other VDOMs are dedicated to traffic.
Question
Which downstream FortiGate VDOM is used to join the Security Fabric when split-task VDOM is enabled on all FortiGate devices?
Options
- ARoot VDOM
- BFG-traffic VDOM
- CCustomer VDOM
- DGlobal VDOM
How the community answered
(45 responses)- A93% (42)
- B4% (2)
- D2% (1)
Why each option
When split-task VDOM is enabled on FortiGate devices, the Root VDOM is responsible for joining the Security Fabric and managing global device settings. This VDOM handles management tasks, while other VDOMs are dedicated to traffic.
In a FortiGate configured with split-task VDOMs, the Root VDOM is designated as the management VDOM. It handles all control plane functions, including Security Fabric communication and device-level configurations. Therefore, the Root VDOM is the one that establishes and maintains the Security Fabric connection.
FG-traffic VDOM is typically used for user traffic processing when split-task VDOM is enabled and is not intended for Security Fabric management.
Customer VDOM is a generic term for VDOMs created by an administrator to segment customer traffic, not a specific VDOM designated for Security Fabric management.
Global VDOM is a conceptual global configuration space, but the actual VDOM responsible for fabric communication when split-task is enabled is the Root VDOM.
Concept tested: FortiGate Security Fabric integration with split-task VDOMs
Source: https://docs.fortinet.com/document/fortigate/7.4.0/administration-guide/183182/split-task-vdom
Topics
Community Discussion
No community discussion yet for this question.