FCP_FMG_AD-7.6 · Question #22
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 correct answer is C. The administrator must use the Install Wizard and select Install device settings only to push BGP. If you change BGP in FortiManager and only reinstall the policy package, the change will NOT reach FortiGate because BGP is a device setting. You must install device settings.
Question
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?
Options
- AThe administrator must run a sanity check on FortiManager to make sure the database is not
- BFortigate has a BGP template assigned on the FortiManager database.
- CThe administrator must use the Install Wizard and select Install device settings only to push BGP
- DThe FortiGate firmware version is different from the FortiManager ADOM version.
How the community answered
(30 responses)- A7% (2)
- B10% (3)
- C80% (24)
- D3% (1)
Explanation
If you change BGP in FortiManager and only reinstall the policy package, the change will NOT reach FortiGate because BGP is a device setting. You must install device settings.
Topics
Community Discussion
No community discussion yet for this question.