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.

You can configure the FortiManger NATed IP address on FortiGate under the central management configuration. This allows FortiGate to announce itself to FortiManager and try to re- establish the FGFM tunnel, if it is torn down. Configuring the FortiManager NATed IP address on FortiGate allows both FortiManager and FortiGate to re-establish the FGFM tunnel. Also, if you configure the FortiManager NATed IP address under the FortiManager system administrator settings, FortiManager sets this address on FortiGate during the discovery process.