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

（A）They can be set to optional or required.

（B）They are available across all ADOMs by default.

（C）They cannot be created in the global database ADOM.

（D）They can be used as variables in scripts.

（A）You can invoke them using the $ character.

（B）You can add them to objects as custom attributes.

（C）You can use them as variables in scripts.

（D）You can export them to be used in other ADOMs.

（A）An administrator can also lock the Local-FortiGate_root policy package.

（B）The FortiManager ADOM workspace mode is set to Normal.

（C）The FortiManager ADOM is locked by the administrator.

（D）FortiManager is in workflow mode.

（A）To save the current state of all policy packages and objects for an ADOM

（B）To revert individual policy packages and device-level settings for a managed FortiGate

（C）To save the current state of the whole ADOM

（D）To save the FortiManager configuration in the System Checkpoints

（A）The diagnose dvm check-integrity command attempts to fix a corrupted file system.

（B）Scheduled backups run database integrity commands automatically.

（C）Not following the correct upgrade path may cause inconsistencies in the databases.

（D）The diagnose cdb check adom-integrity command can correct issues related to looked devices.

（E）You should fix all database integrity issues before performing a backup.

（A）Policy ID 1 for this managed FortiGate already exists on FortiManager in the policy package named Remote-FortiGate.

（B）Policy ID 1 does not have the ADOM Interface mapping configured on FortiManager.

（C）The address object used in policy ID 1 already exists in the ADOM database with any as the interface association, and conflicts with the address object interface association locally on FortiGate.

（D）Policy ID 1 is configured from the interface any to port6. FortiManager rejects the request to import this policy because the any interface does not exist on FortiManager.