Courseiva
Enterprise Firewall and VDOMsmediumMultiple ChoiceObjective-mapped

NSE7 Enterprise Firewall and VDOMs Practice Question

Exhibit

config system interface
edit "port1"
set vdom "root"
set ip 10.0.1.1 255.255.255.0
set allowaccess ping https ssh snmp
set type physical
set role wan
next
end
config system admin
edit "admin"
set trusthost1 192.168.1.0 255.255.255.0
next
end

Refer to the exhibit. A FortiGate is configured with the above settings. The FortiManager at 192.168.1.100 cannot establish a management connection to the FortiGate. What is the most likely cause?

⚠ Common exam trap

The trap here is that candidates may focus on the HTTPS access or trusthost settings, but the exhibit clearly shows the subnet mismatch between the FortiGate's port1 IP (10.0.1.1) and the FortiManager's IP (192.168.1.100), which is the fundamental Layer 3 connectivity issue that prevents the management session from being established.

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

The FortiGate's port1 IP is not in the same subnet as the FortiManager

The FortiGate's port1 IP (10.0.1.1/24) is on a different subnet (10.0.1.0/24) than the FortiManager's IP (192.168.1.100), which is on the 192.168.1.0/24 subnet. For a management connection to be established, the FortiGate and FortiManager must be able to route to each other, typically requiring them to be on the same subnet unless a gateway or static route is configured. Since no routing is mentioned, the subnet mismatch is the most likely cause of the failure.

Answer analysis

Option-by-option breakdown

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

  • HTTPS access is not enabled on port1

    Why it's wrong here

    HTTPS is enabled in allowaccess.

  • The admin user 'admin' is not configured correctly

    Why it's wrong here

    The admin user is present.

  • The FortiGate's port1 IP is not in the same subnet as the FortiManager

    Why this is correct

    The management IP is 10.0.1.1, but FortiManager is on 192.168.1.0/24, so they are on different subnets.

  • The trusthost configuration does not include the FortiManager IP

    Why it's wrong here

    The trusthost includes 192.168.1.0/24, which covers 192.168.1.100.

Visual reference

192.168.1.0 /24 256 addresses (254 usable) 192.168.1.0 /25 Subnet A 128 addr (126 usable) 192.168.1.128 /25 Subnet B 128 addr (126 usable) Borrowing 1 bit from host portion creates 2 subnets (/25)

About these practice questions

One of 940 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 →

How Courseiva writes practice questions · Editorial policy

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.