Fortinet FCP_FMG_AD-7.4 Dumps Questions Answers

When a new policy package is created in a custom ADOM that already has a global policy package assigned, the global policy package is automatically assigned to the new policy package. This behavior ensures consistent policy enforcement across different ADOMs.

Options A, C, and D are incorrect because:

A and C incorrectly suggest that manual reassignment or reapplication is needed.

D implies optional assignment, whereas it is automatically done.

FortiManager References:

Refer to FortiManager 7.4 Administrator Guide: Working with Global and Custom ADOM Policy Packages

To create and install a policy on a FortiGate device in an ADOM (Administrative Domain) that is in backup mode, the administrator must use a FortiManager script. This is because backup mode restricts direct configuration changes, and scripts can be used to push specific configuration changes without altering the ADOM mode.

Options A, C, and D are incorrect because:

A requires the ADOM to be in normal or advanced mode to create policies directly in the Policy & Objects section.

C suggests disabling offline mode, which is irrelevant to the backup mode configuration.

D implies changing the ADOM mode, which is unnecessary if using a script to perform the task.

FortiManager References:

Refer to FortiManager 7.4 Administrator Guide: Working with ADOMs and Using Scripts for managing policies in backup mode.

The provided screenshot from FortiManager shows several key elements that help answer the question:

Thepadlock iconnext to the "Remote-FortiGate" policy package indicates that this policy package islocked, 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 inuse, and a session is active where an administrator is working on a policy package.

Theabsence of a lock iconnext 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 istrue. The fact that one of the policy packages is locked suggests that FortiManager is operating inADOM workflow modeor at least in a state where it enforces locking for editing, typically seen in Normal ADOM modes. Inworkflow mode, an administrator needs to lock a workspace before making changes.

Statement C(The FortiManager ADOM is locked by the administrator): This istrue. 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 isnotnecessarily true. The administrator can lock the "Local-FortiGate_root" policy package, but as shown in the exhibit, it iscurrently not locked, so this option is not a certainty in this state.

Statement D(The FortiManager ADOM workspace mode is set to Normal): This istrue, 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.