Free Practice Questions for Fortinet NSE6_FNC_AD-7.6 Exam

The correct answer is A . In the exhibit, the Template Name is Engineer-Contractor , and the selected Role option is Use a unique Role based on this template name . That means FortiNAC-F uses the template name itself as the role value for any account created from this guest/contractor template. The study guide confirms this behavior: by default, the Role field is populated with the template name, although the administrator can alternatively select from an existing role list. It also states that the role value in the guest and contractor template populates the Role field of any account created from that template.

Option B , Eng-Contractor , is wrong because that value is entered in the Security and Access Value field, not the Role field. That value can still be used in user/host profiles or policies, but it does not populate the account Role field. Option C , Contractor , is only the Visitor Type , which controls the kind of guest/contractor account and associated icon behavior. Option D , Accounting Contractor , is visible in the disabled Select Role dropdown, but that option is not selected because the template is configured to use a unique role based on the template name.

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 . For FortiGate VPN integration, FortiNAC-F depends on syslog from FortiGate to receive VPN user, IP address, and session information. The FortiNAC-F study guide states that after a remote user successfully authenticates and establishes a VPN connection, FortiGate sends user, IP, and session information to FortiNAC-F using syslog. This keeps FortiNAC-F aware of the VPN session so it can apply the correct access control state and update FortiGate when the device becomes trusted.

Option A is wrong because SNMP traps are commonly used for infrastructure events, link traps, or third-party event inputs, but this VPN workflow uses FortiGate syslog. Option B is wrong because RADIUS accounting can update session information in some NAC workflows, but the FortiGate VPN integration described in the guide uses syslog. Option C is wrong because Security Fabric integration is not the required mechanism for keeping FortiNAC-F updated with VPN session details in this scenario.

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.

This behavior directly indicates that the matching Device Profiling Rule has Registration configured as Manual . The FortiNAC-F 7.6 Administrator Study Guide explains that when registration is Automatic , FortiNAC-F performs the configured registration operations immediately after the device matches the rule. When registration is Manual , however, the rule still matches and the device is successfully profiled and classified , but the registration settings are not executed until an authorized sponsor or administrator manually registers the device.

Consequently, the device can legitimately appear in Profiled Devices with its matched rule and assigned device type while the Registered column remains No . The Administration Guide confirms that this column specifically indicates whether the profiled device has been registered.

Option A is incorrect because rule confirmation determines whether an already-profiled device is periodically or subsequently revalidated against its associated rule; it does not control initial registration. Option B is incorrect because rules are evaluated in ranked order until the applicable match is processed. Option D concerns Persistent Agent communications and does not determine device-profiler registration status.

Study Guide Reference: Identification and Classification of Rogues → Device Profiling Rules → General Rule Information / Registration Settings , approximately pp. 110–111 .

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 answer is D . The log output shows the local IP address as 192.168.10.10 , which the question identifies as the primary FortiNAC-F server. In the same output, FortiNAC-F reports inControl true and controlServer true , which means the local primary server is currently the control server. The line showing communication to 192.168.10.110 returns Running - Not In Control , confirming that the secondary server is alive but is not the active controlling node.

This matches FortiNAC-F 1+1 HA behavior. The study guide describes a 1+1 HA pair as an active-passive deployment where one FortiNAC-F device is designated primary and the other secondary. Database and configuration synchronization keep the devices aligned, but only one server is in control at a time. If the primary fails, the secondary assumes control automatically; otherwise, the primary remains the active control server.

Option A is wrong because the secondary explicitly reports Not In Control . Option B is wrong because the output does not show database replication failure. Option C is wrong because failover is not in progress; the output shows a stable state where the primary is in control and the secondary is running as the passive node.