Fortinet NSE5_FNC_AD_7.6 Based on Real Exam Environment

In a corporate domain environment where " enhanced endpoint visibility " is required, thePersistent Agentis the recommended choice. Unlike the Dissolvable Agent, which is temporary and intended for one-time compliance scans during registration, the Persistent Agent is an " install-and-stay-resident " application.

The Persistent Agent is specifically designed to be distributed through automated enterprise methods, includinglogin scripts, Group Policy Objects (GPO), or third-party software management tools. When deployed via a login script, the agent can be configured to silently install and immediately begin communicating with the FortiNAC-F service interface. Once active, it provides continuous visibility by reporting host details such as logged-on users, installed applications, and adapter information. It also listens for Windows session events (logon/logoff) to trigger automatic single-sign-on (SSO) registration in FortiNAC-F, ensuring that as soon as a user connects to the domain, their device is identified and assigned the correct network access policy.

" The Persistent Agent can be distributed to Windows domain machines vialogin scriptor by any other software distribution method your organization might use. The Persistent Agent remains installed on the host at all times. Once the agent is installed it runs in the background and communicates with FortiNAC at intervals established by the FortiNAC administrator. " —FortiNAC-F Administration Guide: Persistent Agent Overview.

In FortiNAC-F, theLayer 3 Network typeis specifically designed for deployments where the isolation networks—such as Registration, Remediation, and Dead End—are separated from the FortiNAC appliance ' s service interface (port2) by one or more routers. This architecture is common in large, distributed enterprise environments where endpoints in different physical locations or branches must be isolated into subnets that are local to their respective network equipment.

The reason the Configuration Wizard allows for more than one DHCP scope for a single isolation network type (state) is thatthere can be more than one isolation network of each typeacross the infrastructure. For instance, if an organization has three different sites, each site might require its own unique Layer 3 registration subnet to ensure efficient routing and to accommodate local IP address management. By allowing multiple scopes for the " Registration " state, FortiNAC can provide the appropriate IP address, gateway, and DNS settings to a rogue host regardless of which site ' s registration VLAN it is placed into.

When an endpoint is isolated, the network infrastructure (via DHCP Relay/IP Helper) directs the DHCP request to the FortiNAC service interface. FortiNAC then identifies which scope to use based on the incoming request ' s gateway information. This flexibility ensures that the system is not limited to a single flat subnet for each isolation state, supporting a scalable, multi-routed network topology.

" Multiple scopes are allowed for each isolation state (Registration, Remediation, Dead End, VPN, Authentication, Isolation, and Access Point Management). Within these scopes, multiple ranges in the lease pool are also permitted... This configWizard option is used when Isolation Networks are separated from the FortiNAC Appliance ' s port2 interface by a router. " —FortiNAC-F Configuration Wizard Reference Manual: Layer 3 Network Section.

The correct answers are A and C . Fortinet’s FortiNAC-F 7.6 documentation states that, to receive and interpret traps from devices or applications, those devices or applications must be modeled in FortiNAC and must have an associated IP address. That validates option A directly. The same Fortinet Trap MIB Files documentation also lists a FortiNAC-OS requirement: the snmp option must be included in the set allowaccess command. That validates option C .

Option B is wrong because Trap MIB integration is not limited to SNMPv3. Fortinet states that Trap MIB supports receiving SNMPv1 and SNMPv2 traps from external devices, while SNMPv3 is discussed separately for traps that populate host and user records.

Option D is the trap. The Fortinet documentation explicitly says IP address OID, MAC address OID, and user ID OID are not all required ; any one OID can be used to identify the host or user that triggered the trap. So the statement that both the IP address OID and MAC address OID must be configured is false.

The correct answer is A . In a FortiNAC-F 1+1 HA deployment, failover from primary to secondary is automatic, but failback to the primary is not automatic . The study guide states that if the primary device or its network connectivity fails, the secondary assumes control automatically, but restoration of a failed-over HA deployment is a manual administrator-driven process. It further explains that after the cause of the failover is resolved, the administrator must use the Resume Control button to transfer control back to the primary server.

That means when the primary comes back online, it does not immediately take over again. The pair can resume HA communication, but the secondary remains the in-control node until an administrator deliberately returns control to the primary. Option B is wrong because FortiNAC-F 1+1 HA is active-passive, not load-balanced. Option C is wrong because the restored primary does not power itself down for maintenance. Option D is a trap: five failed heartbeats are used in failure detection and gateway validation logic, not as an automatic failback timer. The exam point is simple: automatic failover, manual failback .