Fortinet
NSE5_FMG-6.2 · Question #59
Refer to the exhibit. Review the Download Import Report. Why is it failing to import firewall policy ID 2?
The correct answer is C. The policy package ID 2 on FortiGate is already used in the ADOM database with any as the interface association, and conflicts with the address object interface association locally on FortiGate. See the full explanation below for the reasoning.
Question
Refer to the exhibit. Review the Download Import Report.
Why is it failing to import firewall policy ID 2?
Options
- APolicy ID 2 does not have ADOM interface mapping configured on FortiManager.
- BPolicy ID 2 for this managed FortiGate already exists on FortiManager in policy package named Remote-FortiGate.
- CThe policy package ID 2 on FortiGate is already used in the ADOM database with any as the interface association, and conflicts with the address object interface association locally on FortiGate.
- DPolicy ID 2 is configured from the interface any to port0. FortiManager rejects to import this policy because the any interface does not exist on FortiManager.
How the community answered
(15 responses)- A13% (2)
- B7% (1)
- C80% (12)
Community Discussion
No community discussion yet for this question.