Quick Answer
The correct answer is Device Manager -> ADOM settings. Meta fields in FortiManager must be defined at the ADOM level rather than globally because they are scoped to a specific administrative domain, ensuring that custom metadata—such as location, contact, or device role—applies consistently to all FortiGates within that ADOM. This design allows administrators to tailor metadata per ADOM without affecting other domains, which is critical when managing separate customer or departmental environments. On the Fortinet NSE 7 Advanced Security NSE7 exam, this concept tests your understanding of ADOM scoping versus global database objects; a common trap is assuming meta fields are defined under System Settings or Global Objects, but those apply universally. Remember: meta fields live where the ADOM lives—Device Manager > ADOM settings. A helpful memory tip is “Meta per ADOM, not per globe”—if you need fields for a specific ADOM, you configure them inside that ADOM’s settings, not in the global database.
This NSE7 practice question tests your understanding of enterprise firewall and vdoms. This is a configuration task: choose the command set that satisfies every stated requirement. Small differences — like 'secret' vs 'password' or 'transport input ssh' vs 'all' — change whether the answer is correct. After answering, compare your reasoning against the explanation and wrong-answer breakdown below. Once you have made your selection, read the full explanation to reinforce the concept and understand why each distractor is designed to mislead on exam day.
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?
Policy & Objects -> Object configurations
Why wrong: Object configurations include policies, but not meta fields.
Device Manager -> ADOM settings
Meta fields are configured in ADOM settings under Device Manager.
System settings -> Admin
Why wrong: Admin settings handle administrators, not meta fields.
Global database objects
Why wrong: Global objects are shared, but meta fields are ADOM-specific.
Answer choices
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.
Key principle: Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
Answer analysis
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
Object configurations include policies, but not meta fields.
Device Manager -> ADOM settings
Why this is correct
Meta fields are configured in ADOM settings under Device Manager.
Related concept
Read the scenario before looking for a memorised answer.
System settings -> Admin
Why it's wrong here
Admin settings handle administrators, not meta fields.
Global database objects
Why it's wrong here
Global objects are shared, but meta fields are ADOM-specific.
Common exam traps
The trap here is that candidates may 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.
Detailed technical explanation
Meta fields are custom attributes (e.g., location, contact info) that can be attached to devices in FortiManager. They are defined per ADOM under Device Manager -> ADOM settings, and once defined, they appear as editable fields in the device dashboard. This granularity allows different ADOMs to have distinct meta fields tailored to their operational needs, which is critical in multi-tenant or large-scale deployments where each ADOM represents a separate customer or business unit.
Key takeaway
Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
Real-world example
A practitioner preparing for the NSE7 exam encounters this exact type of scenario on the job. The correct answer here is not the most general option — it is the best answer for the specific constraint described. Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option. Real exam questions reward reading the full scenario before eliminating options, because the constraint defines which answer fits.
What to study next
Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.
Enterprise Firewall and VDOMs — study guide chapter
Learn the concepts, then practise the questions
Enterprise Firewall and VDOMs practice questions
Targeted practice on this topic area only
All NSE7 questions
1,000 questions across all exam domains
Fortinet NSE 7 Advanced Security NSE7 study guide
Full concept coverage aligned to exam objectives
NSE7 practice test guide
How to use practice tests most effectively before exam day
Related practice questions
Use these pages to review the topic behind this question. This is how one missed question becomes focused revision.
Practise NSE7 questions linked to Advanced Networking and SD-WAN.
Practise NSE7 questions linked to Advanced VPN and Zero Trust.
Practise NSE7 questions linked to Enterprise Firewall and VDOMs.
Practise NSE7 questions linked to Advanced Threat Protection.
Practise NSE7 questions linked to Troubleshooting and Diagnostics.
Practise NSE7 questions linked to NSE7 fundamentals.
Practise NSE7 questions linked to NSE7 scenario.
Practise NSE7 questions linked to NSE7 troubleshooting.
Practice this exam
Short sessions build daily habit. Longer sessions build exam-day stamina. Try a timed session to simulate real conditions.
FAQ
Enterprise Firewall and VDOMs — This question tests Enterprise Firewall and VDOMs — Read the scenario before looking for a memorised answer..
The correct answer is: 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.
Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.
Read the scenario before looking for a memorised answer.
About these practice questions
Courseiva creates original exam-style practice questions with explanations and wrong-answer analysis. It does not publish real exam questions, exam dumps, or protected exam content. Learn why practice questions differ from exam dumps →
Last reviewed: Jun 24, 2026
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.
Question Discussion
Share a tip, memory trick, or ask about the reasoning behind this question. Do not post real exam questions, leaked content, braindumps, or copyrighted exam material. Comments are moderated and may be removed without notice.
Sign in to join the discussion.