Fortinet FCP_FMG_AD-7.4 Dumps

The statement that is true about the policy lock feature on FortiManager is:

A. Policy locking is available in workspace normal mode.

In FortiManager, when working in "workspace-mode normal," policies can be locked by administrators to prevent other administrators from editing them simultaneously. This ensures that only one administrator makes changes at any given time, reducing conflicts or mistakes due to concurrent modifications.

Statements B, C, and D are incorrect because:

B is incorrect since locking a policy does not override a locked ADOM. The ADOM lock takes precedence.

C is incorrect because when a policy is locked, it does not necessarily mean the ADOM is locked.

D is incorrect because administrators in the approval group cannot work concurrently on a locked policy; the policy lock prevents concurrent modifications.

FortiManager References:

Refer to FortiManager 7.4 Administrator Guide: Policy and Objects > Policy Locking to understand how the policy lock feature functions in different workspace modes.

If the script is run using the "Device Database" option on FortiManager, the following occurs:

A.You must install these changes on a managed device using the Install Wizard.

Running the script on the Device Database updates only the configuration in the FortiManager's database, not on the actual FortiGate device. To apply the changes, you need to use the Install Wizard to push these configurations to the managed device.

D.The device Config Status is tagged as Modified.

After running the script on the Device Database, FortiManager tags the device's configuration status as "Modified," indicating that there are pending changes that have not yet been installed on the device.

Options B and C are incorrect because:

Bsuggests a new revision history is created, but this only happens when changes are actually installed on the managed device.

Cimplies the script is directly executed on the FortiGate, which is not the case when using the Device Database option.

FortiManager References:

Refer to FortiManager 7.4 Administrator Guide: Scripting and Configuration Management.

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