Q: 7
Refer to the exhibit.
An administrator added a FortiGate device to FortiManager with the default object settings at the
ADOM layer.
What can you conclude from the import policy package process of the HQ-NGFW- 1 device?
An administrator added a FortiGate device to FortiManager with the default object settings at the
ADOM layer.
What can you conclude from the import policy package process of the HQ-NGFW- 1 device?Options
Discussion
C . If the wizard actually shows 'Create New' for LAN, port4, and port6, then FortiManager is going to add those as normalized interfaces in the ADOM. That's standard behavior in the import process. Pretty sure that's what they're asking here, but open to corrections.
Option C The trap is thinking manual steps are needed (like B), but FortiManager creates those missing interfaces during import if mapping is set to "Create New". Seen this on practice exams, pretty sure it's C.
C . FortiManager's import wizard auto-creates normalized interfaces at the ADOM layer when it shows 'Create New' for each interface, so LAN, port4, and port6 get added. Trap is D, but that's only an issue if objects aren't imported at all, which doesn't match the exhibit here. If anyone thinks otherwise let me know, but pretty sure it's C.
C . The trap is thinking B (manual creation needed), but as long as the wizard shows 'Create New' for LAN, port4, and port6, FortiManager auto-generates those as normalized interfaces in the ADOM layer. Pretty sure that's what's happening here but happy to hear opposing views.
Don't think B works here-C is correct. FortiManager auto-creates LAN, port4, and port6 as normalized interfaces when mapping is set to 'Create New', so no need for manual intervention unless mapping fails. Pretty sure that's what the screenshot implies but correct me if I missed something.
Its C, the real trap is B but FortiManager auto-creates normalized interfaces if 'Create New' is selected in the import.
C/D? Had something like this in a mock before and it pointed to C, but I could see D in some weird cases. Not 100% sure here, open to pushback.
C
I don’t think it's B. C fits because FortiManager auto-creates any missing interfaces like LAN, port4, and port6 as normalized objects when importing the policy package. You only need to create them manually if something fails or isn’t detected, but here the mapping says "Create New" by default. Pretty sure that's how it works but open to corrections.
Doesn't B make more sense if port4 wasn't mapped automatically? Feels like C is a trap if you miss how FortiManager handles interfaces that aren't pre-existing. Anyone else see this kind of confusion in the interface mapping step?
Be respectful. No spam.