FCP_FMG_AD-7.6 · Question #5
An administrator has a FortiGate-HQ device with VDOMs--root, HR and Facilities, currently managed under the FortiManager ADOM--Site1. They try to move VDOM HR to the FortiManager ADOM-- Site2, but…
The correct answer is C. FortiManager must be in ADOM normal mode, which does not allow VDOMs to be managed. An ADOM can work in device moces: Normal, which is the default mode, and Advanced. In Normal mode, you cannot assign diferent FortiGate virtual domains (VDOMs) to different Fortitvlanager ADOMs. In Advanced mode, you can assign different VDOMs from the sarne FortjGate device to…
Question
An administrator has a FortiGate-HQ device with VDOMs--root, HR and Facilities, currently managed under the FortiManager ADOM--Site1. They try to move VDOM HR to the FortiManager ADOM-- Site2, but it does not work. Why is the administrator not able to move FortiGate-HQ VDOM HR to FortiManager ADOM-- Site2?
Options
- AThe FortiGate-HQ must be managed under the FortiManager ADOM--root to allow moving its
- BThe administrator must have full access in the device layer of FortiGate-HQ VDOM-root before
- CFortiManager must be in ADOM normal mode, which does not allow VDOMs to be managed
- DThe administrator must delete the FortiGate-HQ device from FortiManager and add it again using
How the community answered
(28 responses)- A4% (1)
- B18% (5)
- C71% (20)
- D7% (2)
Explanation
An ADOM can work in device moces: Normal, which is the default mode, and Advanced. In Normal mode, you cannot assign diferent FortiGate virtual domains (VDOMs) to different Fortitvlanager ADOMs. In Advanced mode, you can assign different VDOMs from the sarne FortjGate device to diferent ADOMs. The system applies this setting globally to all ADOMs. This resutts in more complex management scenarios, and it is recommended for advanced users only.
Topics
Community Discussion
No community discussion yet for this question.