FCP - FortiManager 7.4 Administrator Practice Tests and PDFs

The provided screenshot from FortiManager shows several key elements that help answer the questio n: The padlock icon next to the "Remote-FortiGate" policy package indicates that this policy package is locked, which means it is currently being edited or has been checked out by an administrator. This is typical behavior when the ADOM (Administrative Domain) workspace is in use, and a session is active where an administrator is working on a policy package. The absence of a lock icon next to "Local-FortiGate_root" and "default" indicates that these policy packages are not locked and are available for editing. Statement B (FortiManager is in workflow mode): This is true. The fact that one of the policy packages is locked suggests that FortiManager is operating in ADOM workflow mode or at least in a state where it enforces locking for editing, typically seen in Normal ADOM modes. In workflow mode, an administrator needs to lock a workspace before making changes. Statement C (The FortiManager ADOM is locked by the administrator): This is true. The presence of the padlock on "Remote-FortiGate" signifies that the ADOM, or more specifically, this policy package within the ADOM, has been locked by the administrator. Statement A (An administrator can also lock the Local-FortiGate_root policy package): This is not necessarily true. The administrator can lock the "Local-FortiGate_root" policy package, but as shown in the exhibit, it is currently not locked, so this option is not a certainty in this state. Statement D (The FortiManager ADOM workspace mode is set to Normal): This is true, but not the best option compared to B and C, as it can be inferred that the mode is set to Normal due to the locking behavior, but the more direct information is about the ADOM being locked by an administrator.

The output indicates that: The device's status is shown as "dev-db: modified" and "conf: in sync," which means that there is a difference between the device-level database on FortiManager and the actual running configuration of the managed FortiGate. Therefore, the latest revision history for the managed FortiGate does not match the device-level database, which confirms statement A as true. "dm: retrieved" status indicates that configuration changes have been installed on the FortiGate, confirming statement B as true. It also means that the configuration has been modified, and those changes have been pulled from the FortiGate to the FortiManager. Statements C and D are incorrect because: C is incorrect as it implies an automatic update, whereas "dev-db: modified" indicates changes have been made on the FortiGate device that are not yet reflected in the FortiManager's database. D is incorrect because "dev-db: modified" shows that the device-level database and running configuration are not in sync. FortiManager Reference: Refer to the FortiManager 7.4 Administrator Guide: Device Manager > Device Status to understand the "dev-db" and "conf" status meanings.

When operating in workspace mode on FortiManager 7.4, the administrator must understand how object references and deletions work: Option C - "FortiManager will not allow the administrator to delete a referenced address object until they lock the ADOM": In workspace mode, all changes are managed within an Administrative Domain (ADOM) scope. When an object (like an address object) is referenced in a policy, FortiManager prevents its deletion to maintain configuration integrity. The ADOM must be locked by the administrator to make changes to any referenced objects. This locking mechanism ensures that no unintended deletions or changes occur that could disrupt the policies or configuration. FortiManager Reference: "In workspace mode, changes to objects or policies require the ADOM to be locked. If an object is referenced, you must lock the ADOM before deleting or modifying the object." (FortiManager 7.4 Administration Guide, Section on Workspace Mode and ADOM Management) Option D - "FortiManager will replace the deleted address object with the none address object in the referenced firewall policy": If the administrator attempts to delete an address object that is currently referenced by a firewall policy, FortiManager will replace the deleted object with the 'none' address object. This is done to maintain the policy structure and avoid policy corruption due to a missing reference. This behavior ensures that the firewall policy remains syntactically correct, even though the specific address object is no longer in use. FortiManager Reference: "When a referenced object is deleted, FortiManager will replace it with a 'none' object in the policy. This behavior is to ensure the integrity and continuity of the policy configurations." (FortiManager 7.4 Administration Guide, Object Management and Policy Handling in Workspace Mode)

Option B: To save the current state of all policy packages and objects for an ADOM is the correct answer. ADOM (Administrative Domain) revisions in FortiManager are used to create a snapshot of the current state of all policy packages and objects associated with an ADOM. This allows administrators to save a specific configuration state and revert to it if necessary. It helps in managing changes and recovering from configuration errors or unintended changes. Explanation of Incorrect Options: Option A: To save the current state of the whole ADOM is incorrect because ADOM revisions specifically save only the policy packages and object configurations, not the entire state of the ADOM, which may include logs, reports, and other non-policy data. Option C: To revert individual policy packages and device-level settings for a managed FortiGate is incorrect as ADOM revisions are not meant for reverting individual policy packages or device settings; they are designed to handle the entire set of policy packages and objects within an ADOM. Option D: To save the FortiManager configuration in the System Checkpoints is incorrect because ADOM revisions do not function as system checkpoints for FortiManager itself; they are specific to ADOM policy packages and objects. FortiManager Reference: Refer to the FortiManager 7.4 Administration Guide, "ADOM Management" section, which describes the purpose and usage of ADOM revisions for configuration management and restoration.

Option B: 192.168.1.0/24 is the correct answer. In FortiManager, when a firewall address object is defined and used across multiple policy packages without any Per-Device Mapping, the default value configured in the object definition (192.168.1.0/255.255.255.0) is applied to all devices. The exhibit shows that the address object LOCAL_SUBNET has a default IP/netmask of 192.168.1.0/24. Therefore, FortiManager will use this default value for any FortiGate device that does not have a specific Per-Device Mapping configured. Explanation of Incorrect Options: Option A: FortiManager generates an error for each FortiGate without a per-device mapping defined for that object is incorrect because FortiManager does not generate an error when a Per-Device Mapping is not set. Instead, it uses the default value provided in the object definition. Option C: 192.168.1.0/28 is incorrect because the default value is 192.168.1.0/24, as seen in the exhibit, not /28. Option D: FortiManager replaces the address object to none is incorrect because FortiManager does not replace address objects to "none" when a Per-Device Mapping is missing; it uses the default value instead. FortiManager Reference: Refer to the FortiManager 7.4 Administration Guide, specifically in sections related to "Address Object Management" and "Per-Device Mapping," which detail the behavior of address objects without specific device mappings.