A. FortiManager updated the object ALL using FortiGate’s value in its database

B. FortiManager updated the object ALL using FortiManager’s value in its database

C. FortiManager created the object ALL as a unique entity in its database, which can be only used by this managed FortiGate

D. FortiManager installed the object ALL with the updated value

A. The setting allows automatic updates to the policy package configuration for a managed device

B. The setting enables the ADOMs feature on FortiManager

C. This setting allows you to assign different VDOMs from the same FortiGate to different ADOMs

D. The setting disables concurrent ADOM access and adds ADOM locking

A. To find and provide recommendation to combine multiple separate policy packages into one common policy package

B. To find and merge duplicate policies in the policy package

C. To find and provide recommendation for optimizing policies in a policy package

D. To find and delete disabled firewall policies in the policy package

A. It will not create a new revision in the revision history

B. It installs device-level changes to FortiGate without launching the Install Wizard

C. It cannot be canceled once initiated and changes will be installed on the managed device

D. It provides the option to preview configuration changes prior to installing them

A. Set to workflow and use the ADOM locking feature

B. Set to read/write and use the policy locking feature

C. Set to normal and use the policy locking feature

D. Set to disable and use the policy locking feature

A. The address object used in policy ID 2 already exist in ADON database with any as interface association and conflicts with address object interface association locally on the FortiGate

B. Policy ID 2 is configured from interface any to port6 FortiManager rejects to import this policy because any interface does not exist on FortiManager

C. Policy ID 2 does not have ADOM Interface mapping configured on FortiManager

D. Policy ID 2 for this managed FortiGate already exists on FortiManager in policy package named Remote-FortiGate

A. Device name and serial number of the original device

B. Device name and serial number of the replacement device

C. Device name of the replacement device and serial number of the original device

D. Device name of the original device and serial number of the replacement device

A. This setting will enable the ADOMs feature on FortiManager

B. This setting is applied globally to all ADOMs

C. This setting will allow assigning different VDOMs from the same FortiGate to different ADOMs

D. This setting will allow automatic updates to the policy package configuration for a managed device

A. FortiGate is discovered by FortiManager through the FortiGate NATed IP address

B. FortiGate can announce itself to FortiManager only if the FortiManager IP address is configured on FortiGate under central management

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

D. If the FCFM tunnel is torn down, FortiManager will try to re-establish the FGFM tunnel

A. FortiManager updated the object ALL using the FortiGate value in its database

B. FortiManager installed the object ALL with the updated value

C. FortiManager created the object ALL as a unique entity in its database, which can be only used by this managed FortiGate

D. FortiManager updated the object ALL using the FortiManager value in its database

A. It allows two or more administrators to make configuration changes at the same time, in the same ADOM

B. It disables concurrent read-write access to an ADOM

C. It allows the same administrator to lock more than one ADOM at the same time

D. It is used to validate administrator login attempts through external servers

A. When you configure MEA, you must open TCP or UDP port 540

B. You must open the ports to the Fortinet registry

C. You must create a MEA special policy on FortiManager using the super user profile

D. The administrator must have the super user profile