Instantly download NSE6_FMG_AD-7.6 updated real questions

The administrator uses FortiManager to push a CLI script using the Remote FortiGate Directly (via CLI) option to configure an IPsec VPN. However, when running the script, the administrator receives the following error:
config vpn ipsec phase2-interface [parameter(s) invalid. detail: object mismatch] What must the administrator do to resolve the script error and successfully apply the IPsec configuration?

• A. Use IPsec templates to deploy provisioning templates.
• B. Add a second config vpn ipsec phase2-interface block without linking it to phase1.
• C. Add the end command after finishing the IPsec phase 1-interface configuration block.
• D. Run the script using the policy package or ADOM database method.

An administrator has assigned a global policy package to a new ADOM named ADOM1.
What will happen if the administrator tries to create a new policy package in ADOM1?

• A. The administrator will have to assign the global policy package from the global ADOM.
• B. FortiManager will automatically assign the global policy package to the new policy package.
• C. FortiManager will automatically install policies on the policy package in ADOM1.
• D. The administrator will be able to select the option to assign the global policy package to the new policy package.

What is the best explanation of how FortiManager helps with mass provisioning?

• A. It provides local FortiGuard Distribution Server (FDS) services to the network.
• B. It sends email alerts when new devices connect.
• C. It uses templates to configure the same settings on many devices simultaneously.
• D. It upgrades the OS of each FortiGate device.

An administrator has a FortiGate-HQ device with VDOMs-root, HR and Facilities, currently managed under the FortiManager ADOM-Site1. They try to move VDOM HR to the FortiManager ADOM-Site2, but it does not work.
Why is the administrator not able to move FortiGate-HQ VDOM HR to FortiManager ADOM-Site2?

• A. The FortiGate-HQ must be managed under the FortiManager ADOM-root to allow moving its VDOMs to different ADOMs.
• B. The administrator must delete the FortiGate-HQ device from FortiManager and add it again using the Add Device wizard before moving the VDOM.
• C. FortiManager must be in ADOM normal mode, which does not allow VDOMs to be managed separately.
• D. The administrator must have full access in the device layer of FortiGate-HQ VDOM-root before they can VDOMs to different ADOMs.

An administrator configures a new BGP peer in the FortiManager device-level database of FortiGate. They reinstall the policy package to the managed FortiGate device without any errors. However, when the administrator logs in to FortiGate, they do not see the BGP configuration changes.
What is the most likely reason why FortiManager did not push the BGP peer changes to FortiGate?

• A. The FortiGate firmware version is different from the FortiManager ADOM version.
• B. Fortigate has a BGP template assigned on the FortiManager database.
• C. The administrator must use the Install Wizard and select Install device settings only to push BGP settings
• D. The administrator must run a sanity check on FortiManager to make sure the database is not corrupted.