nerdexam
Fortinet

NSE5_FMG-6.4 · Question #17

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 address object used in policy ID 2 already exists in the ADOM database with any as the interface association, and conflicts with the address object. Explanation/Reference:

Policy and objects

Question

Refer to the exhibit. Review the Download Import Report. Why is it failing to import firewall policy ID 2?

Exhibit

NSE5_FMG-6.4 question #17 exhibit

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 address object used in policy ID 2 already exists in the ADOM database with any as the interface association, and conflicts with the address object
  • DPolicy ID 2 is configured from the interface any to port6. FortiManager rejects to import this policy because the any interface does not exist on FortiManager.

How the community answered

(25 responses)
  • A
    16% (4)
  • B
    8% (2)
  • C
    72% (18)
  • D
    4% (1)

Explanation

Explanation/Reference:

Topics

#policy import#address object#dynamic mapping#ADOM database conflict

Community Discussion

No community discussion yet for this question.

Full NSE5_FMG-6.4 Practice