An admin is registering a new FortiGate 100F into an existing ADOM. The company standard requires that all new devices receive a baseline configuration including admin access settings, DNS servers, and NTP servers. The admin wants this applied automatically during the registration process. What should the admin configure in FortiManager?

Use a CLI script and run it against the device after it appears in the ADOM.

Create a provisioning template and assign it to the ADOM so it applies to all newly registered devices.

Manually configure the device after registration using the 'Device Config' tab.

Set the device as a 'Template Device' and copy its settings to new devices.

A company is deploying a FortiGate 4200F chassis with two FIM (FortiGate Interface Module) cards and four FPM (FortiGate Processing Module) cards. The admin needs to register this chassis in FortiManager so that all modules are managed as a single logical device. What is the correct registration procedure?

Register the chassis by its serial number; FortiManager automatically discovers and manages all modules as one unit.

Register each FPM and FIM card individually as separate devices in the ADOM.

Use the 'Add Chassis' wizard, which requires entering the serial numbers of all modules during registration.

Register only the primary FPM module and manually add the other modules as 'virtual' devices.

A FortiGate is failing to register with FortiManager. The admin has verified that the FortiManager IP is correct, the FGFM port (541) is open, and the device is in the correct ADOM. The admin also confirmed that the FortiGate's local-in policy allows traffic from FortiManager. What is the next most likely step to troubleshoot?

Reboot the FortiGate to reset the FGFM tunnel.

Check if the FortiManager's certificate is trusted by the FortiGate.

Check if the FortiGate's serial number is already registered in a different ADOM.

Verify that the FortiGate's hostname is not already in use in the ADOM.

A FortiGate has been successfully registered in FortiManager, but the admin notices that the device is showing as 'Unregistered' in the GUI. The admin has verified that the FGFM tunnel is up. What is the most likely cause?

The device is in a different ADOM than the one FortiManager assigned it to.

The device's firmware is not compatible with FortiManager.

The device's hostname is not unique in the ADOM.

The device's serial number is not recognized by FortiManager.

FortinetNSE 6 - FortiManager Administrator

Domain 2Objective 1

Register Devices in ADOMs NSE6-FORTIMANAGER-ADMINISTRATOR Practice Questions (Page 2)

Part of the Device Manager domain, which accounts for 20-30% of the NSE6-FORTIMANAGER-ADMINISTRATOR exam. Fortinet does not publish an official question count, but from its 70-minute exam (~30–45 total, ~6–14 in this domain), expect 2–5 from this objective — we provide 23 practice questions to prepare you well beyond it. (estimate)

23questions here

5free pages

5concepts

20-30%of the exam

Questions 6–10

6application · medium
An admin is registering a new FortiGate 100F into an existing ADOM. The company standard requires that all new devices receive a baseline configuration including admin access settings, DNS servers, and NTP servers. The admin wants this applied automatically during the registration process. What should the admin configure in FortiManager?
Select an answer first
7foundation · easy
An administrator wants to automatically apply a standard set of interface and administrative settings to every new FortiGate that registers to an ADOM. Which FortiManager feature should be used?
Select an answer first
8application · medium
A company is deploying a FortiGate 4200F chassis with two FIM (FortiGate Interface Module) cards and four FPM (FortiGate Processing Module) cards. The admin needs to register this chassis in FortiManager so that all modules are managed as a single logical device. What is the correct registration procedure?
Select an answer first
9expert · hard
A FortiGate is failing to register with FortiManager. The admin has verified that the FortiManager IP is correct, the FGFM port (541) is open, and the device is in the correct ADOM. The admin also confirmed that the FortiGate's local-in policy allows traffic from FortiManager. What is the next most likely step to troubleshoot?
Select an answer first
10application · medium
A FortiGate has been successfully registered in FortiManager, but the admin notices that the device is showing as 'Unregistered' in the GUI. The admin has verified that the FGFM tunnel is up. What is the most likely cause?
Select an answer first

Finished these 5 questions?

Review the revealed explanations, or continue through the curriculum.

Next 5 questions →Back to NSE6-FORTIMANAGER-ADMINISTRATOR

Free Basic Practice is a study aid with revealable answers — not a scored exam. Examers.io is independent and not affiliated with or endorsed by Fortinet. “NSE6-FORTIMANAGER-ADMINISTRATOR” is a trademark of its owner, used for identification only.

Register Devices in ADOMs NSE6-FORTIMANAGER-ADMINISTRATOR Practice Questions (Page 2)

Questions 6–10

An administrator wants to automatically apply a standard set of interface and administrative settings to every new FortiGate that registers to an ADOM. Which FortiManager feature should be used?

A FortiGate has been successfully registered in FortiManager, but the admin notices that the device is showing as 'Unregistered' in the GUI. The admin has verified that the FGFM tunnel is up. What is the most likely cause?

Keep studying — Device Manager