NSE7 Enterprise Firewall and VDOMs Practice Question
An administrator configures a new ADOM in FortiManager for a set of FortiGates. The administrator wants to assign meta fields to devices in this ADOM. Where should the meta fields be defined?
⚠ Common exam trap
Test-takers frequently confuse ADOM-specific settings with global database objects, assuming meta fields must be defined globally for consistency, but FortiManager requires them to be defined at the ADOM level to maintain isolation between administrative domains.
Answer choices
Why each option matters
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Device Manager -> ADOM settings
Meta fields in FortiManager are defined at the ADOM level under Device Manager -> ADOM settings. This ensures that the custom fields are available for all devices within that specific ADOM, allowing consistent metadata assignment across managed FortiGates. Defining them elsewhere, such as in global database objects, would apply them globally rather than per-ADOM, which is not the administrator's intent.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Policy & Objects -> Object configurations
Why it's wrong here
Policy and object configurations hold firewall policies, addresses and services, not device metadata. It is tempting because meta fields are assigned to devices, and this menu is where most device-related objects live, but the correct location is the ADOM's device manager meta fields section.
- ✓
Device Manager -> ADOM settings
Why this is correct
Meta fields are ADOM-scoped objects, defined under Device Manager's ADOM settings so every device in that ADOM can be tagged consistently. Defining them here satisfies the requirement to assign meta fields to devices within the new ADOM.
- ✗
System settings -> Admin
Why it's wrong here
System settings and Admin manage administrator accounts, profiles and authentication, not device metadata. It is tempting because meta fields are configured by administrators and the name suggests system-level settings, yet the correct location is the ADOM device manager where per-device meta fields are defined.
- ✗
Global database objects
Why it's wrong here
Global database objects are shared across all ADOMs, so they cannot hold meta fields scoped to one ADOM's devices. It is tempting because global objects centralise reusable definitions, which is right when the same object must apply everywhere, but meta fields are per-ADOM device attributes.
About these practice questions
One of 718 original NSE7 practice questions on Courseiva, each with a full explanation and wrong-answer analysis — not exam dumps or protected exam content. Learn why practice questions differ from exam dumps →
JA
Written by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
This NSE7 practice question is part of Courseiva's free Fortinet certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the NSE7 exam.