FCP – FortiManager Administrator 7.6 — Question 4

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?

Answer options

• A. The administrator must run a sanity check on FortiManager to make sure the database is not corrupted.
• 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 FortiGate firmware version is different from the FortiManager ADOM version.

Correct answer: C

Explanation

The correct answer is C because using the Install Wizard and selecting 'Install device settings only' is necessary to specifically push BGP settings to FortiGate. Option A is incorrect since a sanity check does not affect the push process. Option B is not relevant as the presence of a BGP template does not prevent the changes from being pushed. Option D is also incorrect because firmware version differences do not inherently block configuration changes from being applied.