FCP_FMG_AD-7.4 無料問題集「Fortinet FCP - FortiManager 7.4 Administrator」

（A）From the configured override server IP address 10.0.1.50 only

（B）From the list of configured override servers or public FDN servers

（C）From the default server fds1.fortinet.com

（D）From public FDNI server IP address with the fourth highest octet only

（A）If the FGFM tunnel is torn down, FortiManager will try to re-establish the FGFM tunnel.

（B）During discovery, the FortiManager NATed IP address is not set by default on FortiGate.

（C）FortiGate is discovered by FortiManager through the FortiGate NATed IP address.

（D）FortiGate can announce itself to FortiManager only if the FortiManager non-NATed IP address is configured on FortiGate under central management.

（A）When a policy is locked, the ADOM that contains it is also locked.

（B）Policy locking is available in workspace normal mode.

（C）Administrators in the approval group can work concurrently on a locked policy.

（D）Locking a policy takes precedence over a locked ADOM.

（A）Source ADOM policy database

（B）ADOM2 object database

（C）FortiManager file system

（D）ADOM2 device database

（A）The administrator must use the correct user name and password of the FortiAnalyzer device.

（B）The administrator must select the FortiManager administrative access checkbox on the FortiAnalyzer management interface.

（C）The administrator must use the Add Model Device section and discover the FortiAnalyzer device.

（D）The administrator must turn off the Use Legacy Device login and add the FortiAnalyzer device to the same network as FortiManager.

（A）Reconfigure the primary device to remove the peer IP of the failed device.

（B）The FortiManager HA state transition is transparent to administrators and does not require any reconfiguration.

（C）Manually promote one of the working secondary devices to the primary role, and reboot the old primary device to remove the peer IP of the failed device.

（D）Reboot the failed device to remove its IP from the primary device.