Free FCP_FMG_AD-7.4 Practice Test Questions and Answers (2026)

The configuration shown in the exhibit leads to two primary results. First, with Concurrent ADOM Access set to One Admin, only a single administrator can have read-write privileges within an ADOM at any given time. Any other administrators attempting to access that same ADOM will be granted read-only access. This effectively disables simultaneous read-write access by multiple administrators.

Second, the setting Allow admin to lock multiple ADOMs is explicitly Enabled. Although the master ADOM Locking feature is disabled (which makes this setting currently ineffective), the statement accurately describes a configured state. The configuration is set to permit an administrator to lock more than one ADOM, should the primary locking feature be activated.

A. The setting Allow remote authentication for admin login is explicitly set to Disabled, which prevents the use of external authentication servers.

C. The Concurrent ADOM Access setting is configured to One Admin, which directly prevents two or more administrators from making configuration changes simultaneously.

1. FortiManager Administration Guide 7.4.1

Page 101

"Admin Settings".

Concurrent ADOM Access: "Select how many administrators can access an ADOM at the same time: One Admin or Multiple Admins." This directly supports the correctness of option D and the incorrectness of option C.

Allow admin to lock multiple ADOMs: "When ADOM locking is enabled

you can enable this option to allow administrators to lock more than one ADOM at a time." This supports that the configuration is set as described in option B.

2. FortiManager Administration Guide 7.4.1

Page 102

"Admin Settings".

Allow remote authentication for admin login: "Enable to allow remote authentication for administrator login." The exhibit shows this is disabled

which invalidates option A.

In FortiManager with workspace mode enabled, any attempt to modify the configuration, including deleting an object, requires the administrator to first lock the Administrative Domain (ADOM). This prevents concurrent changes and ensures administrative control. Therefore, the system will not permit the deletion until the ADOM is locked.

Once the ADOM is locked and the administrator deletes an address object that is referenced in a firewall policy, FortiManager automatically replaces the deleted object within that policy with the none address object. This action maintains the structural integrity of the firewall policy while removing the specific reference, preventing validation or installation errors.

A. FortiManager will temporarily change the status of the referenced firewall policy to disabled.

This is incorrect. FortiManager modifies the policy's content by replacing the object, but it does not change the enabled/disabled status of the policy itself.

B. FortiManager will disable the status of the address object until the changes are installed.

This is incorrect. Address objects in FortiManager do not have an enabled or disabled status; they are either present in the database or they are not.

1. FortiManager Administration Guide 7.4.1

Page 218

"Workspace mode": "When workspace mode is enabled

you must lock an ADOM before you can make changes to it." (Supports answer C)

2. FortiManager Administration Guide 7.4.1

Page 381

"Deleting objects": "If you delete an object that is used by other objects

such as a firewall policy

the deleted object is replaced by the none object." (Supports answer D)

When an administrator initiates the action to move a device between Administrative Domains (ADOMs) in the FortiManager GUI, a confirmation dialog box is immediately displayed. This prompt, as shown in Option A, serves as a crucial checkpoint. It informs the administrator of the consequences—that the device will be removed from its current ADOM and its configuration will be retrieved after being added to the new one. The user must click "OK" to proceed with the move. This dialog is the direct and initial output of the move action itself, preceding the actual execution and subsequent status changes.

B: The "Re-install policy" prompt appears after the device has been successfully moved and FortiManager determines its configuration is out of sync with the policy packages in the new ADOM.

C: This shows a log entry. While a log is generated to record the event, it is not a primary dialog box or interactive output displayed to the administrator during the move process.

D: The "Modified" configuration status is a result that is displayed in the Device Manager pane after the move is complete and the device's configuration has been retrieved and compared against the new ADOM's database.

1. Fortinet FortiManager Administration Guide 7.4.1

Page 238

Section: "Moving devices to another ADOM".

The guide states

"When you move a device to another ADOM

a confirmation dialog box is displayed. After you confirm the move

the device is moved to the other ADOM." This directly confirms that the dialog box (Option A) is the immediate output when the action is initiated.

The same section later explains the consequences: "When a device is moved to a new ADOM

the device's configuration is retrieved. The configuration is compared against the new ADOM's database

and the device's configuration status becomes modified." This supports why options B and D are subsequent results

not the initial output.

Global policy packages and their assignments to Administrative Domains (ADOMs) are managed centrally from the Global ADOM (also called the Global Database). To remove a global policy assignment from a customer ADOM, a service provider administrator (with superadmin privileges) must perform the action from within the Global ADOM context. They would navigate to the ADOM management settings, edit the specific customer ADOM (MyADOM), and unassign the global policy package. This action removes the global header policy from all policy packages within MyADOM. A customer administrator confined to their own ADOM does not have the necessary permissions or access to the Global ADOM to perform this function.

A. This describes the result but is less precise than option D. The action of unassigning the policy from MyADOM must be initiated within the Global ADOM, which is the crucial administrative context.

B. A customer administrator is restricted to their assigned ADOM and lacks the permissions to manage global objects or their assignments, which are controlled at a higher administrative level.

C. Locking an ADOM is a feature to prevent conflicting changes by multiple administrators within that ADOM; it does not elevate a customer administrator's permissions to the global level.

1. FortiManager Administration Guide 7.4.0

"Global policy packages"

Page 538: "Global policy packages are created in the global database and assigned to ADOMs. The policies are then used as a header and/or footer policy to the policy packages in the assigned ADOMs." This establishes that management is a global-level task.

2. FortiManager Administration Guide 7.4.0

"Assigning a global policy package to an ADOM"

Page 138: The procedure requires the administrator to "Go to System Settings > All ADOMs". This view is only available to administrators with access to the Global ADOM (such as a superadmin)

confirming that the assignment/unassignment is managed from the global context. The administrator then selects the target ADOM to edit its properties

including the assigned global package.

3. FortiManager Administration Guide 7.4.0

"Administrators"

Page 108: This section details administrator profiles and permissions

clarifying the distinction between a superadmin with global access and a standard administrator who may be restricted to a specific ADOM. A customer administrator would typically have a restricted profile.

After a successful authentication request to the FortiManager JSON API, the system returns a unique session ID. This session ID acts as a temporary authentication token. For all subsequent API calls within the same session, this ID must be included in the JSON RPC request payload. This allows FortiManager to verify that the request is coming from an authenticated and authorized user, eliminating the need to send login credentials with every single request. The session remains valid until it is explicitly terminated or times out.

A. The session ID is an authentication credential, not a mechanism for identifying or managing client-side metadata related to the FortiManager.

B. The session ID is a token for session management and authentication; it is not a cryptographic hash used for verifying the integrity of JSON responses.

C. The HTTP request method (e.g., POST) is part of the HTTP protocol itself and is independent of the session ID, which is part of the JSON payload for authentication.

1. Fortinet FortiManager Administration Guide 7.4.0

Page 598

Section: "JSON API". The guide states

"After you log in

you receive a session ID that you must use for all subsequent requests." This confirms its role as a token for subsequent requests.

2. Fortinet FortiManager API Reference 7.4.0

Page 10

Section: "Authentication". The documentation details the login process and shows that the response contains a "session" key. It further explains

"The session key is required for all subsequent requests to the FortiManager unit." An example request on page 11 demonstrates including the "session": "..." key-value pair in a subsequent API call.

The integrity of the FortiManager databases is critical for stable operation, successful upgrades, and reliable backups.

Statement (C) is correct because FortiManager database schemas can change significantly between major versions. The upgrade process includes scripts to migrate the database to the new schema. Skipping versions in the upgrade path means these migration scripts may not run or may fail, leading to data corruption and database inconsistencies.

Statement (B) is also correct. As a built-in safeguard, the FortiManager system automatically performs a database integrity check before executing a backup task. If this check fails, the backup process is aborted to prevent creating a backup of a corrupted or inconsistent database, which would be unreliable for a future restore.

A. The diagnose dvm check-integrity command is a diagnostic tool that reports inconsistencies within the Device Manager (DVM) database, not the underlying file system. It does not perform any corrective actions.

D. While it is a mandatory prerequisite to fix integrity issues before a backup can succeed (as the backup will fail otherwise), statement B describes the actual system process that enforces this, making it a more direct and accurate statement about the system's behavior.

E. The diagnose cdb check adom-integrity command is used to identify and report integrity problems within a specific ADOM's database. It does not have the functionality to correct issues, such as unlocking devices.

1. FortiManager Administration Guide 7.4.1

Page 101

"Backing up the FortiManager system": "Before backing up the configuration

FortiManager runs a database integrity check. If the check fails

the backup is not created." This directly supports answer B.

2. FortiManager Upgrade Guide 7.4.1

Page 5

"Upgrade path": "You must follow the supported upgrade path. If you do not follow the supported upgrade path

you will have issues with the upgrade." This section emphasizes the requirement to follow a specific path to prevent issues

which includes database inconsistencies

supporting answer C.

3. FortiManager CLI Reference 7.4.1

Page 130

"diagnose dvm check-integrity": The description for this command is "Check device manager database integrity." It details the syntax for checking but includes no parameters or descriptions for fixing or repairing

which supports the reasoning for A being incorrect.

4. FortiManager CLI Reference 7.4.1

Page 108

"diagnose cdb check adom-integrity": The description is "Check ADOM integrity." Similar to other diagnostic commands

its purpose is to report status

not to perform corrective actions

which supports the reasoning for E being incorrect.

The diagnose test deploymanager reloadconf command is a diagnostic tool used to force a resynchronization of a managed device's configuration with the FortiManager database. It instructs FortiManager to connect to the specified FortiGate (identified by ), retrieve its current running configuration, and then use that configuration to "reload" or overwrite the corresponding device-level database on FortiManager. This is typically used in troubleshooting scenarios where the configuration on FortiManager is out of sync or suspected to be corrupt, ensuring FortiManager has an accurate representation of the device's state.

A. This describes a configuration difference check (diff), which is a comparison function, not the primary purpose of the reloadconf command which is to retrieve and update.

C. This describes a policy package installation, which involves pushing configuration from FortiManager to a FortiGate. The reloadconf command performs the opposite action (pulling).

D. This describes a device-level configuration installation. The reloadconf command retrieves the configuration from the FortiGate, it does not install a configuration onto it.

1. Fortinet FortiManager Administration Guide 7.4.1

Page 371

"Synchronizing configuration". The guide discusses retrieving configuration and states

"You can retrieve the configuration of a device or VDOM... This is useful if the device configuration was changed locally on the device and you want to import the changes into the FortiManager system." The reloadconf command is a CLI method to force this retrieval and reload process.

2. Fortinet FortiManager CLI Reference 7.4.1

Page 218. Under the diagnose test deploymanager command tree

the reloadconf command is explicitly defined with the description: "Reload device configuration from the device." This confirms the action is a pull from the FortiGate to update the FortiManager database.

In a FortiManager High Availability (HA) cluster, the primary unit's configuration defines the cluster membership. When a secondary (peer) device fails and cannot be recovered, the HA cluster is in a degraded state. To return the cluster to a stable, working condition with the remaining active members, an administrator must manually intervene. The correct procedure is to access the primary FortiManager's HA settings and remove the configuration entry, including the IP address, for the failed secondary device. This action updates the cluster's topology and resolves the inconsistency caused by the unreachable member.

A: This is incorrect. Manual mode HA requires administrator intervention to manage cluster membership, especially in a failure scenario. The process is not transparent.

B: Rebooting the failed device will not change the HA configuration on the primary unit. If the device is permanently offline, this action has no effect on the cluster's state.

C: Promoting a secondary device is the procedure for a primary device failure, not a secondary one. The primary unit is still operational in this scenario.

1. FortiManager Administration Guide 7.4.1

Chapter: "High Availability"

Section: "Managing the cluster"

Subsection: "Removing a failed cluster member"

Page 71.

The documentation explicitly states: "If a cluster member fails

you must remove it from the cluster. You must edit the HA configuration on the primary FortiManager to remove the failed device." It then provides the GUI steps: "Go to System Settings > HA... In the Peer Information table

select the failed device and click Delete." This directly supports the action of reconfiguring the primary device.

The configuration Concurrent ADOM Access: Allow explicitly permits a single administrator account to access and therefore lock multiple ADOMs simultaneously. This makes option D correct.

ADOM locking is tied to an administrator's session. If the session terminates ungracefully (e.g., browser crash, network loss), the lock is not released. The ADOM remains locked to prevent data inconsistency until the administrator's idle session times out or another administrator with override permissions manually unlocks it. This makes option B correct.

A. Unlocking an ADOM will submit configuration changes automatically to the approval administrator.

This describes a feature of Workspace Mode, which is explicitly Disabled in the exhibit. In Normal mode, there is no submission or approval workflow.

C. Unlocking an ADOM will install configuration changes automatically on managed devices.

Unlocking an ADOM and installing a configuration are two distinct and separate administrative actions. Unlocking only makes the ADOM available for other administrators to edit.

1. FortiManager Administration Guide 7.4.1

Page 101

"System Settings pane":

Under the ADOM section

the guide describes the Concurrent ADOM Access setting: "Select to allow administrators to access multiple ADOMs at the same time." This directly validates option D.

The guide also describes Workspace Mode

confirming its features are not active when disabled

which invalidates option A.

2. FortiManager Administration Guide 7.4.1

Page 98

"ADOMs":

This section explains the ADOM locking mechanism: "When an administrator is making configuration changes in an ADOM

the ADOM is locked to prevent other administrators from making changes at the same time." It further explains that locks are tied to sessions. If a session ends abnormally

the lock persists until the session idle timeout

validating the behavior described in option B.

3. FortiManager Administration Guide 7.4.1

Page 323

"Install policies and objects":

This section details the installation process as a separate

deliberate step initiated by an administrator using the Install Wizard. This confirms that unlocking an ADOM (a configuration management action) does not trigger an installation

invalidating option C.

FortiManager provides flexibility in how and where system backups are performed. Administrators can configure scheduled backups through both the graphical user interface (GUI) under System Settings > Advanced > Scheduled Backup and the command-line interface (CLI) using the config system backup all-settings command. For storing these backups remotely, FortiManager supports multiple secure and standard file transfer protocols, specifically FTP (File Transfer Protocol), SCP (Secure Copy Protocol), and SFTP (SSH File Transfer Protocol). This allows integration with various external backup servers for data redundancy and disaster recovery purposes.

A. The backup includes FortiManager data and device configurations, but not the entire FortiGuard database, which contains dynamic threat intelligence data like antivirus and IPS signatures.

C. Scheduled backups are designed to run as a background process and do not require putting the FortiManager into offline mode, which is a separate maintenance state.

1. FortiManager Administration Guide 7.4.1

Page 101

Section: "Scheduled backups". This section explicitly details the GUI configuration for scheduled backups and lists the supported upload options: "Select the type of server to upload the backup file to: FTP

SCP

or SFTP." This supports answers B (GUI part) and D.

2. FortiManager CLI Reference 7.4.1

Page 1116

Command: config system backup all-settings. This document shows the set schedule command within this context

which allows for enabling and configuring the backup schedule via the CLI

confirming that both GUI and CLI methods are available. This supports answer B.

3. FortiManager Administration Guide 7.4.1

Page 100

Section: "Backing up all settings". This section describes the contents of a full backup

which includes "all FortiManager data and configurations

including all device configurations

scripts

and global ADOM database." It makes no mention of the FortiGuard database

confirming option A is incorrect.

4. FortiManager Administration Guide 7.4.1

Page 106

Section: "Offline mode". This section describes offline mode as a distinct feature for performing maintenance

such as rebuilding the database

separate from the standard backup process. This confirms option C is incorrect.

The Never Installed status indicates that a policy package has been assigned to a managed device within FortiManager, but the configuration has never been pushed (installed) from FortiManager to the device. This is a common initial state after a new device is registered and associated with a policy package, but before the first deployment is executed. It signifies that no policy synchronization from FortiManager to the device has ever occurred for that specific package.

A. This state is typically represented by an Unknown status, which occurs when FortiManager cannot connect to the device to retrieve its status.

B. This describes a Modified status, indicating that the configuration was changed locally on the managed device and is now different from FortiManager's database.

D. This describes a configuration that is Modified (on FortiManager) or Out-of-Sync, meaning changes have been made in FortiManager that are pending installation on the device.

1. Fortinet FortiManager Administration Guide 7.4.1

Page 310

Table "Installation status".

Never Installed: "The policy package has never been installed to the device."

Modified: "The device has been changed. You can import the changes."

Unknown: "The installation status is unknown."

This official documentation directly defines "Never Installed" as a state where the package has not been pushed to the device

aligning with the scenario in option C where initial synchronization has not happened. It also explicitly defines the statuses described in options A

B

and D as distinct from "Never Installed".

An ADOM revision in FortiManager creates a versioned snapshot of the central management components within a specific Administrative Domain (ADOM). Its primary purpose is to save the current state of all policy packages and their associated objects. This allows administrators to create a restore point before making significant changes. If a new configuration causes issues, the administrator can revert the ADOM's policy and object database to this previously saved, known-good state.

A. This is incorrect because an ADOM revision specifically saves the policy and object database, not the entire state of the ADOM, which would include device inventory and other settings.

C. This describes an action (reverting) that can be performed using a revision, not the purpose of creating one. Also, device-level settings have their own separate revision history.

D. This is incorrect. System Checkpoints are used to save the entire FortiManager system configuration, not the configuration of a specific ADOM.

1. FortiManager Administration Guide 7.4.0

Chapter: Administrative Domains (ADOMs)

Section: Revisions

Page 131.

The guide states

"You can create a revision of an ADOM. An ADOM revision saves the policy packages and objects for that ADOM. You can revert the ADOM to a previous revision if necessary." This directly supports option B.

2. FortiManager Administration Guide 7.4.0

Chapter: System Settings

Section: Creating system checkpoints

Page 53.

This section describes System Checkpoints as a way to "back up the entire FortiManager configuration

" distinguishing it from ADOM-specific revisions and confirming that option D is incorrect.

When both FortiManager and FortiGate are behind NAT devices, the connection must be initiated from the FortiGate to the public IP of the FortiManager.

A. FortiManager discovers the FortiGate using the public IP address of the NAT device in front of the FortiGate. This IP is recorded as the device's IP address in the FortiManager's device list.

D. By default, FortiManager advertises its own private IP address to the FortiGate for management. When FortiManager is behind NAT, this private IP is unreachable. The administrator must manually configure the FortiManager's public (NATed) IP address on the FortiManager itself so it can provide the correct, reachable IP to the FortiGate. Therefore, the NATed IP is not configured by default.

B. The FortiGate must be configured with the FortiManager's public (NATed) IP address to establish a connection, as its private (non-NATed) IP is not routable from the FortiGate's network.

C. Because the FortiGate initiates the connection from behind its NAT device, it is also responsible for re-establishing the FGFM management tunnel if the connection is torn down.

1. FortiManager Administration Guide 7.4

Device Manager > Adding devices > Adding a FortiGate to FortiManager when FortiGate is behind NAT

Page 131: "FortiManager automatically adds the FortiGate device to its device list using the FortiGate NAT device's public IP address." This supports answer A.

2. FortiManager Administration Guide 7.4

Device Manager > Adding devices > Adding a FortiGate to FortiManager when both are behind NAT

Page 132: "When a FortiGate is behind a NAT device

and it is connecting to a FortiManager that is also behind a NAT device

you must configure the FortiManager with its public IP address... Use the config system admin setting and set fmg-source-ip command." This supports answer D

as it shows the NATed IP is not used by default and requires manual configuration.

3. FortiManager Administration Guide 7.4

Device Manager > About the FGFM protocol

Page 118: "If the connection is lost

the FortiGate unit attempts to re-establish the connection." This confirms that the FortiGate

not the FortiManager

re-establishes the tunnel

making option C incorrect.

The exhibit displays a dynamic firewall address object configured in FortiManager. This feature allows an object to have different values depending on the target FortiGate. The object Internal-LAN has a "Default Value" of 192.168.1.0/24. A specific "Per-Device Mapping" is set for the device FGTA to use 192.168.1.0/28. For any FortiGate device that is not explicitly listed in the Per-Device Mapping table, FortiManager will use the configured "Default Value" when installing the policy package. Therefore, devices without a specific mapping will receive the IP/netmask 192.168.1.0/24.

A. An error is not generated because the default value is specifically designed to be used as a fallback for devices without a custom mapping.

C. 192.168.1.0/28 is the mapped value for the specific device FGTA, not for devices that lack a per-device mapping.

D. The object is not set to none; it is populated with the default value, ensuring policy integrity on the target device.

1. FortiManager Administration Guide 7.4.1

Page 388

Section: "Dynamic objects".

The guide states: "When you create a dynamic firewall object

you can define a default value for the object

and then define per-device mapping for the object... When you install the policy package to a device that is not in the mapping list

the default value is used." This directly supports the use of the default value for unmapped devices.

A FortiManager backup file (.dat) is designed to save the essential configuration data required to restore the system's operational state. This includes the FortiManager's own system settings, such as network interfaces, administrator accounts, and logging configurations (often referred to as the flash configuration). Crucially, it also contains the entire database of managed devices, including their configurations, policies, and objects. Items that are large, dynamic, or easily re-downloaded, such as firmware images and the FortiGuard database, are intentionally excluded to ensure the backup process is efficient and the file size is manageable.

B. Firmware images: Firmware images are explicitly excluded from the backup. They must be manually re-imported to the FortiManager appliance after a system restore.

C. FortiGuard database: The FortiGuard database is dynamic data downloaded from Fortinet's services. It is not included in the backup and is re-downloaded after a restore.

1. Fortinet FortiManager Administration Guide 7.4.0

System Settings > Backup and Restore > Backing up the configuration

Page 138: "The backup file is a .dat file that contains the FortiManager configuration

including the device list

and device configuration. The backup file does not include firmware images saved on the FortiManager unit

the FortiGuard database

or logs." This reference directly confirms that device configurations (A) and the FortiManager's own configuration (D) are included

while explicitly stating that firmware images (B) and the FortiGuard database (C) are not.