Refer to the exhibit. What can you conclude from the downloaded import report? (Choose one answer)

A. FortiManager does not support per-device mapping for firewall addresses.
B. The administrator will see a new policy package named Remote-FortiGate_root in the FortiManager ADOM database.
C. FortiManager will change the configuration of REMOTE_SUBNET to match the interface mapping coming in from Remote-FortiGate.
D. As a result of this policy import process, FortiManager will create a new firewall address called REMOTE_SUBNET in the ADOM database.

Correct Answer: B

Brave-Dump Clients Votes

A 40%

B 40%

D 20%

Comments

Saeed Abd El Halim Hamada 2025-07-16 22:53:22

Selected Answers: A

Correct Answer: A

Mahboab Ali Ghaleb 2025-07-22 11:08:57
This is incorrect. FortiManager does support per-device mappings. The failure for REMOTE_SUBNET is a specific "interface binding fail," implying a conflict or misconfiguration, not a general lack of feature support.

Mahboab Ali Ghaleb 2025-07-22 11:31:47

Selected Answers: B

Based the first line there is a new Policy package created named (Remote-FortiGate_root).
Though, the imported REMOTE_SUBNET address and a firewall policy are failed, but the package container itself is created.

eze 2025-11-22 16:39:44

Selected Answers: A

“During policy/package import, object binding mismatch results in FAIL and stops import.”
(Study Guide – sección Policy Package Import behavior)

Angelo Clemente 2025-12-03 17:27:18

Selected Answers: D

When you import a policy package from a FortiGate device into FortiManager:

FortiManager parses the configuration and creates corresponding objects in the ADOM database.
If the imported policy references an address object (e.g., REMOTE_SUBNET) that does not already exist in the ADOM database, FortiManager automatically creates that object during the import process.
This behavior ensures that the imported policy remains consistent and functional within FortiManager.

Anonymous User 2026-02-07 18:04:13

Selected Answers: B

Here you can see the exact same scenario:
https://community.fortinet.com/t5/FortiManager/Troubleshooting-Tip-FortiManager-import-fails-due-to-binding/ta-p/327485

Policy Pack is created, but the import has errors --> B is the right answer.

A is wrong, per Device mappings are supported for adress objects.
C is wrong, the import failed, the manager won't just change attributes. The error stems from contradicting values.
D is wrong, the object is only created when the import goes without fail. Because of the error, the object is not created.