The correct answer is C . The exhibit shows a guest template with Login Availability set to Specify Time , allowing login only Monday through Friday from 6:00 AM to 7:00 PM . The study guide explains that the Account Duration and Login Availability fields define when the account is deleted from the database or what days and times the account is enabled. Therefore, outside the allowed login window, the guest cannot authenticate successfully using that guest account.
To stop network access outside those permitted times, FortiNAC-F must isolate hosts that are in the Not Authenticated state. The guide maps the Authentication captive network to hosts in the Not Authenticated state, and the isolation logic table shows that hosts in the Not Authenticated state are moved to the Authentication network when the point of connection is in the Forced Authentication group.
Option A is wrong because At-risk hosts are isolated to remediation/quarantine due to compliance or security posture problems, not because a guest login is outside allowed hours. Option B is wrong because Disabled hosts are intentionally disabled and sent to the dead-end network; the account here is time-restricted, not necessarily disabled. Option D is wrong because Rogue applies to unregistered or unclassified devices, while this scenario is about a known guest account that is not allowed to authenticate outside its login schedule.

The correct answers are B and C . The persistent agent is the strongest fit because it is installed and stays resident on the endpoint. The study guide states that after deployment, the persistent agent communicates back to FortiNAC-F every 15 minutes and performs scheduled scans in the background, transparent to the end user. That directly satisfies the requirement for recurring compliance scans without user involvement.
The passive agent can also scan Windows domain end stations without end-user interaction. The guide states that the passive agent is deployed through login/logoff scripts and administrative templates, and that passive agent registration can register and scan hosts associated with LDAP or Active Directory users. If enabled, the passive agent scans the host to verify compliance with the appropriate endpoint policy.
Option A is wrong because the dissolvable agent is a run-once agent that requires manual end-user interaction in the captive portal, then removes itself after reporting results. Option D is not the best answer for this requirement because the mobile agent is specifically for Android onboarding and is manually installed; it is not the general solution for daily compliance scanning of all end stations.

The correct answer is A . The exhibit shows two adapters learned on the same wired port: one appears as a rogue/unknown host, and the other is associated with the Lab Hosts rule. The port is in both Role-Based Access and Forced Registration . FortiNAC-F state-based control takes precedence over policy-based provisioning, and the study guide states that when a rogue host connects to a port in the Forced Registration group, FortiNAC-F isolates that host by moving it into the registration captive network. The guide also explains that the Isolation network can be used as a single network for abnormal host states while still presenting state-specific portal pages.
Because this is a wired switch port using VLAN-based control, FortiNAC-F cannot put one host on the production VLAN and the other host on the isolation portal VLAN at the same time on the same access port.
The VLAN change applies to the port, not independently to each MAC address behind that port. Therefore, the presence of the rogue host on a Forced Registration port causes the port to be provisioned to the isolation network. Option B is technically unrealistic for this access-port scenario. Option C is wrong because two MAC addresses alone do not make the port an uplink; FortiNAC-F uses uplink logic for infrastructure-device MACs, manually marked uplinks, or a threshold such as more than 20 MAC addresses. Option D is unrelated because Access Point Management is not triggered by learning two wired hosts on a port.

The firewall policy for an unauthorized VPN host is an isolation policy. When a remote endpoint first establishes its VPN tunnel, FortiGate assigns the client an IP address plus two DNS servers: the production DNS server as primary and the FortiNAC-F Port2 VPN-context address as secondary . Until FortiNAC-F validates the endpoint, FortiGate firewall policies restrict the client ' s traffic so that it can communicate only with the FortiNAC-F Port2 VPN interface .
This restriction deliberately prevents access to the primary production DNS server. Consequently, DNS resolution against the primary server fails and the endpoint falls back to the secondary DNS server- FortiNAC-F. FortiNAC-F then resolves the request toward its VPN isolation interface and presents the VPN captive portal . The user can subsequently run or download the required FortiNAC-F agent, allowing FortiNAC-F to perform identification and endpoint-compliance validation.
After successful authorization, FortiNAC-F sends the appropriate group/tag information to FortiGate, causing the host to match a different firewall policy that permits the required production resources and blocks the isolation interface.
Study Guide Reference: Advanced Features # FortiGate VPN Integration # VPN Host Isolation and Firewall Policies , pp. 346-354 .

In FortiNAC-F, theDevice Profileris a rule-based engine that evaluates unknown " rogue " devices and classifies them based on fingerprints and behavior. When a profiling rule matches a device, the administrator can configure the rule to automatically register that device. The registration process can place the device record in two primary locations: theTopology View(as a device) or theHost View(as a registered host).
According to theFortiNAC-F Administration Guide, registering a device in theHost Viewprovides significant advantages for identity management and historical tracking. First, the devices can beassociated with a user (C). In the FortiNAC database architecture, the Host View is the primary repository for endpoint identity; placing a profiled device here allows the system to link that hardware (MAC address) to a specific user account, whether that user is an employee, guest, or a system-level " owner " . This association is essential for Role-Based Access Control (RBAC) and for tracking accountability across the network fabric.
Second, devices registered in the Host View will haveconnection logs (B). FortiNAC-F maintains a detailed operational history for all host records, including every instance of the device connecting to or disconnecting from a port, its IP address assignments, and the specific policies applied during each session. These logs are invaluable for troubleshooting connectivity issues and for security forensic audits, as they provide a clear timeline of the device ' s lifecycle on the network. In contrast, devices managed only in the Topology View are typically treated as infrastructure components where the focus is on device availability rather than individual session history.
" Devices that are registered and associated with a user are placed in theHost Viewand removed from the Profiled Devices window... Placing a device in the Host View allows for the tracking ofconnection historyand the association of the device with a specificidentity or user recordwithin the FortiNAC database. " - FortiNAC-F Administration Guide: Device Profiler How it Works.