When FortiNAC-F manages VPN clients through a FortiGate, the agent plays a fundamental role in device identification that standard network protocols cannot provide on their own. In a standard VPN connection, the FortiGate establishes a Layer 3 tunnel and assigns a virtual IP address to the client. While the FortiGate sends a syslog message to FortiNAC-F containing the username and this assigned IP address, it typically does not provide the hardware (MAC) address of the remote endpoint ' s physical or virtual adapter.
FortiNAC-F relies on theMAC addressas the primary unique identifier for all host records in its database.
Without the MAC address, FortiNAC-F cannot correlate the incoming VPN session with an existing host record to apply specific policies or track the device ' s history. By running either a Persistent or Dissolvable Agent, the endpoint retrieves its own MAC address and communicates it directly to the FortiNAC-F service interface. This allows the " IP to MAC " mapping to occur. Once FortiNAC-F has both the IP and the MAC, it can successfully identify the device, verify its status, and send the appropriateFSSO tagsor group information back to the FortiGate to lift network restrictions.
Furthermore, while the agent can also perform compliance checks (Option D), the architectural requirement for the agent in a managed VPN environment is primarily driven by the need for session data correlation- specifically the collection of the IP and MAC address pairing.
" Session Data Components: * User ID (collected via RADIUS, syslog and API from the FortiGate). * Remote IP address for the remote user connection (collected via syslog and API from the FortiGate and from the FortiNAC agent). *Device IP and MAC address (collected via FortiNAC agent).... The Agent is used to provide the MAC address of the connecting VPN user (IP to MAC). " -FortiNAC-F FortiGate VPN Integration Guide: How it Works Section.

The correct answer is D . In a Layer 3 registration or isolation network design, DHCP requests from the isolated registration VLAN are not served locally on that VLAN by a normal production DHCP server.
Instead, the registration VLAN's DHCP relay must forward DHCP traffic to FortiNAC-F port2 , because port2 is the captive network service interface. The study guide states that in Layer 3 captive networks, DHCP traffic is relayed to port2 from the captive networks, and that the FortiNAC-F port2 interface provides DHCP, DNS, and captive portal services for hosts assigned to those captive networks.
In the exhibit, the registration VLAN is 192.168.10.x/24 , with gateway 192.168.10.254 . That gateway is where the DHCP relay would be configured, but it is not the relay destination. The relay destination must be the FortiNAC-F port2 address, shown as 192.168.200.10 . The corporate DHCP server 192.168.100.75 is for production network addressing, not registration isolation. The FortiNAC-F port1 address 192.168.100.20 is the administrative or production-facing interface, not the captive network service interface. Therefore, the DHCP relay should point to 192.168.200.10 .

The correct answer is A . When FortiNAC-F needs near real-time Layer 2 visibility, it relies on link traps, MAC notification traps, RADIUS, or scheduled/manual Layer 2 polling. The study guide explains that MAC notification traps contain the MAC address learned or removed from the switch MAC address table and the associated port, allowing FortiNAC-F to update its database when hosts connect, disconnect, or move. It also states that MAC notification traps are the preferred method for learning and updating Layer 2 information.
If a newly modeled switch does not show hosts as they connect or move between ports, the likely problem is that MAC notification traps are not correctly configured or not reaching FortiNAC-F . Layer 3 polling failure would affect IP-to-MAC correlation, not the ability to learn which switch port a MAC address is connected to. Disabled scheduled polling could delay updates, but it would not be the best explanation when the expected behavior is immediate host detection during connection or movement testing. Contact polling only checks whether the device is reachable; it does not collect host MAC-to-port visibility.

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.

TheN+1 High Availability (HA)architecture was introduced in FortiNAC-F version 7.6 to provide a more scalable and flexible redundancy model compared to the traditional 1+1 active/passive setup. In an N+1 configuration, a single secondary (standby) appliance can provide coverage for multiple primary (active) Control and Application (CA) appliances.
To set up an N+1 HA cluster, there are two fundamental structural requirements:
A FortiNAC-F Manager (FortiNAC-M):Unlike standard 1+1 HA, which can be configured directly between two CAs, N+1 management is centralized. The FortiNAC-M acts as the orchestrator that manages the failover groups, monitors the health of the primaries, and coordinates the promotion of the secondary server if a primary fails.
A FortiNAC-F device designated as a Secondary:The cluster must have one appliance explicitly configured with theSecondary failover role. This device remains in a standby state, receiving database replications from all N primaries in its group until it is called upon to take over the functions of a failed unit.
While a cluster can support multiple primaries (D), it does not strictly require " at least two " to function as an N+1 group; it simply requires N primaries (where N # 1). Additionally, N+1 is typically a Layer 3 managed solution via the Manager, meaning it does not mandate a " dedicated VLAN " for synchronization like some Layer 2 HA deployments.
" In FortiNAC-F 7.6,FortiNAC-Mfunctions as a manager to manage the N+1 Failover Groups... enabling N+M high availability for CAs. To create an N+1 Failover group, you should add thesecondary CAto the FortiNAC-M first, then add the primary CAs. The secondary CA is designed to take over the functionality of any single failed primary component. " -FortiNAC-F 7.6.0 N+1 Failover Reference Manual.