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? (Choose one answer)

A. The FortiGate-HQ must be managed under the FortiManager ADOM—root to allow moving its VDOMs to different ADOMs.
B. The administrator must have full access in the device layer of FortiGate-HQ VDOM-root before they can VDOMs to different ADOMs.
C. FortiManager must be in ADOM normal mode, which does not allow VDOMs to be managed separately.
D. The administrator must delete the FortiGate-HQ device from FortiManager and add it again using the Add Device wizard before moving the VDOM.

Correct Answer: C

Brave-Dump Clients Votes

C 75%

D 25%

Comments

Saeed Abd El Halim Hamada 2025-07-16 22:24:22

Selected Answers: C

Correct Answer: C
Correct Answer: C
Correct Answer C
Explanation:
FortiManager has two ADOM modes:

Normal mode – Devices are managed as a single unit, including all of their VDOMs. In this mode, you cannot manage or move individual VDOMs to different ADOMs.

Advanced mode (Split-ADOM mode) – Allows you to manage individual VDOMs separately, so you can assign each VDOM to a different ADOM if needed.

Mahboab Ali Ghaleb 2025-07-21 01:25:13
C: It is the cause of the problem (Normal mode), not the solution to the problem. Fortimanager must be in advaced mode to allow manage VDOMs on different ADOMs.
Mahboab Ali Ghaleb 2025-07-22 09:09:28
The phrase "must be" = "is required to be". In Option C, it's used incorrectly because being in normal mode causes the problem, it does not solve it. if a sentence like: FortiManager is in ADOM normal mode, which does not allow VDOMs to be managed separately. It's correct,Why? It describes the current mode FortiManager is in (normal mode) and it accurately explains that normal mode does not support managing VDOMs separately and explains the reason why the administrator cannot move the VDOM to another ADOM which is true.

Mahboab Ali Ghaleb 2025-07-22 09:00:27

Selected Answers: D

You cannot move individual VDOMs to other ADOMs unless the device was initially added with split VDOMs enabled.
You cannot change an already-added device from normal to split mode after it's added.
The Proper Way (if the device is already added in normal mode):
- Delete the device from FortiManager.
- Switch FortiManager to Advanced ADOM mode (if not already).
- Re-add the device using the Add Device wizard, and enable Split VDOMs into separate devices.
- FortiManager will now treat each VDOM as an independent device.
- FortiManager will now treat each VDOM as an independent device.

Option C: Meaning of "must be" in this context:
The phrase "must be" implies a requirement or condition. It means:
FortiManager is required to be in normal mode in order for something to work.
This option is stating that FortiManager needs to be in "normal mode" — but that’s incorrect.

Omar Ahmed ([email protected]) 2025-10-08 20:21:48

Selected Answers: C

In FortiManager, ADOM mode determines how devices and their VDOMs are managed:

Normal mode (default):

The entire FortiGate device, along with all its VDOMs, must be managed within a single ADOM.

You cannot move individual VDOMs to different ADOMs in this mode.

Advanced mode:

Allows individual VDOMs on a FortiGate to be managed under separate ADOMs.

Required when you want to split VDOMs like root, HR, and Facilities across different ADOMs.

Brave-Dumps Admin 2025-11-08 13:12:22

Selected Answers: C

Study Guide page 38

In Normal mode, you cannot assign different FortiGate virtual domains (VDOMs) to different FortiManager ADOMs.
In Advanced mode, you can assign different VDOMs from the same FortiGate device to different ADOMs.