Cyber Monday 2024! Hurry Up, Grab the Special Discount - Save 25% - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions

Fortinet Exam NSE5_FMG-7.2 Topic 3 Question 16 Discussion

Actual exam question for Fortinet's NSE5_FMG-7.2 exam
Question #: 16
Topic #: 3
[All NSE5_FMG-7.2 Questions]

Refer to the exhibit showing a Download Import Report.

Why is it failing to import firewall policy ID 1?

Show Suggested Answer Hide Answer
Suggested Answer: B

Contribute your Thoughts:

Cherelle
3 months ago
Hmm, that makes sense too. It could be the reason for the import failure.
upvoted 0 times
...
Edison
3 months ago
I disagree, I believe the answer is B. The address object conflicts with the interface association on FortiGate.
upvoted 0 times
...
Cherelle
3 months ago
I think the answer is A. FortiManager rejects the request because the any interface does not exist.
upvoted 0 times
...
Joni
4 months ago
I bet the policy already exists on FortiManager. Those duplicate policy IDs can really throw a wrench in the works.
upvoted 0 times
Gaynell
3 months ago
D) Policy ID 1 for this managed FortiGate already exists on FortiManager in the policy package named Remote-FortiGate.
upvoted 0 times
...
Joana
3 months ago
B) The address object used in policy ID 1 already exists in the ADOM database with any as the interface association, and conflicts with the address object interface association locally on FortiGate.
upvoted 0 times
...
Quentin
3 months ago
A) Policy ID 1 is configured from the interface any to port6. FortiManager rejects the request to import this policy because the any interface does not exist on FortiManager.
upvoted 0 times
...
Tamekia
3 months ago
B) The address object used in policy ID 1 already exists in the ADOM database with any as the interface association, and conflicts with the address object interface association locally on FortiGate.
upvoted 0 times
...
Carin
3 months ago
A) Policy ID 1 is configured from the interface any to port6. FortiManager rejects the request to import this policy because the any interface does not exist on FortiManager.
upvoted 0 times
...
...
Milly
4 months ago
Hah, gotta love those ADOM Interface mapping issues. Definitely a common problem in the FortiManager world.
upvoted 0 times
Javier
3 months ago
C) Policy ID 1 does not have the ADOM Interface mapping configured on FortiManager.
upvoted 0 times
...
Florinda
4 months ago
B) The address object used in policy ID 1 already exists in the ADOM database with any as the interface association, and conflicts with the address object interface association locally on FortiGate.
upvoted 0 times
...
Vincent
4 months ago
A) Policy ID 1 is configured from the interface any to port6. FortiManager rejects the request to import this policy because the any interface does not exist on FortiManager.
upvoted 0 times
...
...
Gladys
4 months ago
The address object conflict seems like the culprit here. Looks like a configuration mismatch between the FortiGate and FortiManager.
upvoted 0 times
...
Ora
4 months ago
The any interface not existing on FortiManager is the most likely reason. I've seen that issue before.
upvoted 0 times
Bettina
4 months ago
C) Policy ID 1 does not have the ADOM Interface mapping configured on FortiManager.
upvoted 0 times
...
Stefanie
4 months ago
A) That makes sense. It's important to ensure consistency between the ADOM database and FortiGate configurations.
upvoted 0 times
...
Gene
4 months ago
B) The address object used in policy ID 1 already exists in the ADOM database with any as the interface association, and conflicts with the address object interface association locally on FortiGate.
upvoted 0 times
...
Delfina
4 months ago
A) Policy ID 1 is configured from the interface any to port6. FortiManager rejects the request to import this policy because the any interface does not exist on FortiManager.
upvoted 0 times
...
...

Save Cancel