Courseiva

Cross-VDOM Administrative Access via Management VDOM

A multi-tenant FortiGate uses VDOMs. The administrator notices that logins via SSH to the management VDOM succeed, but attempts to SSH to a traffic VDOM's management IP fail. The traffic VDOM has an administrative user configured. What is the most likely cause?

⚠ Common exam trap

Many candidates assume a configured admin user and a valid management IP are sufficient for SSH access, overlooking the per-interface administrative access control that must be explicitly enabled.

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

✓

SSH access is not enabled on the traffic VDOM's management interface

SSH access to a VDOM's management IP requires that the management interface explicitly permits SSH administrative access. In a multi-tenant FortiGate with VDOMs, each VDOM's management interface has its own independent administrative access settings. Even if the admin user exists and the VDOM is licensed, SSH will be rejected if the management interface does not have SSH access enabled under config system interface or via the GUI. The fact that SSH to the management VDOM succeeds but fails to the traffic VDOM's management IP points directly to this per-interface access control.

Answer analysis

Option-by-option breakdown

For each option: why learners choose it and why it is or isn't the right answer here.

  • ✗

    The traffic VDOM does not have a license

    Why it's wrong here

    VDOMs on one FortiGate share the appliance licence; no per-VDOM licence exists, so licensing cannot block SSH. It is tempting because licensing failures do cause feature restrictions elsewhere, but that mechanism applies to the device, not to individual traffic VDOMs.

  • ✗

    The traffic VDOM is in transparent mode

    Why it's wrong here

    Transparent-mode VDOMs still permit administrative access on their management interface, so mode does not explain the failure. It is tempting because transparent VDOMs alter forwarding behaviour, but that mechanism concerns packet handling, not SSH termination, and would be relevant only when diagnosing traffic flow, not admin login.

  • ✗

    The admin user is not in the correct trust group

    Why it's wrong here

    Trust groups are not a FortiGate administrative-access control; access is governed by the interface's allowaccess settings and admin trusthost definitions. It is tempting because trust concepts appear in authentication, but that mechanism applies to third-party authentication servers, not to local SSH access on a VDOM interface.

  • ✓

    SSH access is not enabled on the traffic VDOM's management interface

    Why this is correct

    Each VDOM's management interface maintains its own administrative access settings. Even with an admin account present, SSH must be explicitly enabled under the traffic VDOM's interface configuration; otherwise the connection is refused despite valid credentials.

About these practice questions

This NSE7 question is part of Courseiva's 718-question bank — original exam-style content with full explanations and wrong-answer analysis, never real exam questions or exam dumps. Learn why practice questions differ from exam dumps →

How Courseiva writes practice questions · Editorial policy

You might also like

Similar NSE7 questions

Written by Johnson Ajibi, MSc IT Security

Security Systems Architect · 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.