NSE6_FNC_AD-7.6 Exam Dumps - Fortinet NSE 6 - FortiNAC-F 7.6 Administrator

The correct answer is D . The question is about guest onboarding , and the exhibit shows the Guest Network using gateway 10.20.1.250 . In a Layer 3 captive network design, FortiNAC-F provides DHCP and DNS services to isolated or captive-network hosts, but the DHCP scope must still give the endpoint the correct default gateway for the network where that endpoint is placed. The study guide specifically warns that, when configuring Layer 3 captive network scopes, the administrator must think from the isolated host’s perspective for the IP pool and gateway configuration . It also states that each captive network interface configuration includes an IP address, subnet mask, default gateway, and one or more DHCP scopes.

Option A , 10.0.1.254 , is the infrastructure gateway on the FortiNAC-F service/production-side segment, not the guest network gateway. Option B , 10.0.1.110 , is the FortiNAC-F interface address shown in the diagram, not the default gateway for guest clients. Option C , 10.10.1.250 , is the gateway for the Isolation Network , not the Guest Network . Since the administrator is configuring guest onboarding, the DHCP scope for guest users must hand out 10.20.1.250 as the gateway.

The process of moving a host from aRegistration VLANto aProduction VLAN(Access VLAN) is a fundamental part of the FortiNAC-F " VLAN steering " workflow. When a host successfully registers via the captive portal, FortiNAC-F evaluates its Network Access Policies to determine the correct VLAN. If the host remains stuck in the Registration VLAN despite a successful registration, it is typically due to port-level restrictions or the presence of other unregistered devices.

The two most common reasons for this behavior as per the documentation are:

The port default VLAN is the same as the Registration VLAN:If the " Default VLAN " field in the switch port ' s model configuration is set to the same ID as the Registration VLAN, the port will not change state because FortiNAC-F believes it is already in its " normal " or " forced " state.

There is another unregistered host on the same port:FortiNAC-F maintains the security posture of the physical port. If multiple hosts are connected to a single port (e.g., via a hub or unmanaged switch) and at least one host remains " Rogue " (unregistered), FortiNAC-F will generally keep the entire port in the isolation/registration VLAN to prevent the unregistered host from gaining unauthorized access to the production network.

Issues with agents (A, B) typically prevent a host from completing compliance or registration but do not usually result in a " stuck " statusafterregistration has already been marked as successful in the system.

" If a port is identified as havingMultiple Hosts, and those hosts require different levels of access, FortiNAC remains in the most restrictive state (Registration or Isolation) until all hosts on that port are authorized... Additionally, verify theDefault VLANsetting for the port; if the Default VLAN and Registration VLAN match, the system will not trigger a VLAN change upon registration. " —FortiNAC-F Administration Guide: Troubleshooting Host Management.