NSE6_FNC_AD-7.6 Questions and Answers

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.

TheFortiNAC-F Manager (FortiNAC-M)is designed as a centralized management platform for large-scale distributed environments where multiple FortiNAC-F Control and Application (CA) appliances are deployed across different sites. According to theFortiNAC-F Manager Administration Guide, the deployment of a Manager simplifies administrative overhead in three specific ways:

First, it providesGlobal Version Control (B). The Manager serves as a central repository for firmware and software updates, allowing administrators to push specific versions to all managed CAs simultaneously, ensuring consistency across the entire fabric. Second, it enablesPooled Licenses (D). Instead of purchasing and managing individual licenses for every CA, licenses are centralized on the Manager. The Manager then distributes these licenses to the CAs as needed based on their host counts. This " floating " license model optimizes cost and prevents individual sites from running out of capacity while others have excess. Third, it offersGlobal Visibility (E). The Manager aggregates host and device data from every managed CA into a single console. This " single pane of glass " allows an administrator to search for a specific MAC address or user across the entire global organization without logging into individual servers.

While the Manager can assist with configuration templates, authentication security policies (C) and infrastructure modeling (A) are still predominantly managed at the local CA level to ensure site-specific logic and performance.

" The FortiNAC Manager provides a central management console for multiple FortiNAC-F servers (CAs). Key benefits include: •License Management: Licenses are pooled on the Manager and allocated to managed CAs as needed. •Software Management: Firmware updates can be centrally managed and pushed to all CAs from the Manager. •Centralized Monitoring: Provides a global view of all hosts, adapters, and events across the entire managed environment. " —FortiNAC-F Manager Administration Guide: Overview and Benefits.

In FortiNAC-F, the expiration of a guest or contractor account is determined by the configuration settings within theAccount Creation Wizardand the associatedGuest/Contractor Template. While a template can define a default " Account Duration " (as seen in the 12-hour setting in the second exhibit), theAccount Creation Wizardallows an administrator to manually specify or override the start and end parameters for a specific user session.

According to theFortiNAC-F Administration Guideregarding guest management, theAccount End Datefield in the creation wizard is the definitive timestamp for when the account object will be disabled or deleted from the system. In the provided exhibit (Account Creation Wizard), the administrator has explicitly set theAccount Start Dateto2025/09/12 08:00:00and theAccount End Dateto2025/09/13 17:00:00.

Even though the template indicates an " Account Duration " of 12 hours, this value typically serves as a pre-populated default. When a manual date and time are entered into the wizard, those specific values take precedence for that individual account. The account will remain active and valid until5:00 PM (17:00:00)on the following day,2025/09/13. It is also important to note the " Login Availability " from the template (8:00 AM - 7:00 PM); while the accountexistsuntil the 13th at 17:00:00, the user would only be able to authenticate during the active hours defined by the login schedule on both days.

" When creating an account, the administrator can select a template to provide default settings. However, specific values such as theAccount End Datecan be modified within theAccount Creation Wizard. The date and time specified in the ' Account End Date ' field determines the absolute expiration of the account. Once this time is reached, the account is moved to an expired state and the user ' s network access is revoked. " —FortiNAC-F Administration Guide: Guest and Contractor Account Management.

In FortiNAC-F, accountability and forensic tracking of configuration changes are managed through theAdmin Auditingfunctionality. When an administrator performs an action that modifies the system state—such as creating a policy, changing a device ' s status, or adding a switch port to anEnforcement Group—the system generates an audit record. This record is essential for troubleshooting scenarios where unauthorized or accidental configuration changes have occurred, leading to unintended network behavior.

TheAdmin Auditingview (found underLogs > Admin Auditing) provides a comprehensive log of the " Who, What, and When " for every administrative session. Each entry includes the username of the administrator, the source IP address from which they accessed the FortiNAC-F console, a precise timestamp, and a detailed description of the modification. In the scenario described, where ports have been incorrectly added to enforcement groups, the Admin Auditing view allows a supervisor to filter by the specific " Port " or " Group " object to identify exactly which administrator executed the command.

In contrast, theEvent Managementview (B) is designed to monitor system and network events, such as RADIUS authentications, host connections, and SNMP trap arrivals. While it tracks system activity, it does not typically log the manual configuration changes performed by admins. ThePort Changesview (C) tracks the operational history of a port (such as VLAN assignment changes and host movements) but does not attribute the administrative assignment of the port to a group. Finally, theSecurity Eventsview (D) is dedicated to alerts triggered by security rules and external threat feeds.

" Admin Auditing displays a record of all modifications made to the FortiNAC-F system by an administrator. This view includes the administrator ' s name, the date and time of the change, and a description of the action taken. It is the primary resource for determining which administrative user performed a specific configuration change, such as modifying port group memberships or altering policy settings. " —FortiNAC-F Administration Guide: Logging and Auditing Section.

The integration of FortiNAC-F withFortiGate VPNrequires a specific policy workflow to bridge the gap between initial user authentication and full network access. When a user connects to the VPN, the FortiGate typically provides the User ID and IP address, but FortiNAC-F requires aMAC addressto uniquely identify and manage the endpoint ' s record.

According to theFortiGate VPN Integration Guide, theEndpoint Compliance Policyis a mandatory component of this setup because it is used todesignate the required agent type. Because a VPN connection is Layer 3, FortiNAC cannot " see " the MAC address through traditional SNMP or L2 polling. The compliance policy instructs the system to present aCaptive Portalto the remote user, requiring them to download and run either thePersistentorDissolvable Agent. The agent then reports the device ' s MAC address back to FortiNAC, allowing the system to correlate the VPN session with a host record.

Once the agent is running and the MAC is known, FortiNAC-F can evaluate the device ' s security posture (if scanning is configured) and send the necessaryFSSO tagsback to the FortiGate to lift the initial network restrictions. Without the compliance policy to enforce the agent requirement, the connection would remain in an isolated " IP-only " state with no unique hardware identity.

" TheEndpoint Compliance Policyis necessary to control the agent requirement for VPN users. Create a default VPN Endpoint Compliance Policy todistribute an agentvia captive portal for isolated machines. This policy allows the administrator todesignate the required agent type(Persistent or Dissolvable) that will be used to collect the hardware (MAC) address and perform health scans on the remote endpoint. " —FortiNAC FortiGate VPN Integration Guide: Default Endpoint Compliance Policy (Optional) Section.

In FortiNAC-F,Security Triggersare used to identify specific security-related activities based on incoming data such as Syslog messages or SNMP traps from external security devices (like a FortiGate or an IDS). These triggers act as a filtering mechanism to determine if an incoming notification should be escalated from a standard system event to aSecurity Event.

According to theFortiNAC-F Administrator Guideand relevant training materials for versions 7.2 and 7.4, theFilter Matchsetting is the critical logic gate for this process. As seen in the exhibit, the " Filter Match " configuration is set to " All " . This means that for the Security Trigger named " Infected File Detected " to " fire " and generate a Security Event or a subsequent Security Alarm,every single filterlisted in the Security Filters table must be satisfied simultaneously by the incoming data.

In the provided exhibit, there are two filters: one looking for the Vendor " Fortinet " and another looking for the Sub Type " virus " . If only one of these filters is satisfied (for example, a message from Fortinet that does not contain the " virus " subtype), the logic for the Security Trigger is not met. Consequently, FortiNAC-F does not escalate the notification. Instead, it processes theincoming data as aNormal Event, which is recorded in the Event Log but does not trigger the automated security response workflows associated with security alarms.

" The Filter Match option defines the logic used when multiple filters are defined. If ' All ' is selected, then all filter criteria must be met in order for the trigger to fire and aSecurity Eventto be generated. If the criteria are not met, the incoming data is processed as anormal event. If ' Any ' is selected, the trigger fires if at least one of the filters matches. " —FortiNAC-F Administration Guide: Security Triggers 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 answers are B and C . FortiNAC-F must have a persistent agent on the endpoint if the goal is continual or background endpoint monitoring. The study guide states that the persistent agent is an install-and-stay resident agent and that, after deployment, it communicates back to FortiNAC-F every 15 minutes. It also performs scheduled scans in the background without normal user interaction unless the scan fails. That is the agent model required for continuous compliance monitoring, not a one-time captive portal scan.

A custom scan is also required because the administrator wants to check very specific endpoint conditions: a registry key and a security service. The FortiNAC-F study guide lists Windows custom scan types including Registry Keys and Service , which directly match the two conditions in the question.

Option A is wrong because MDM integration is used to synchronize mobile device data, retrieve MDM-known hosts, receive MDM host updates, and apply policies based on MDM attributes; it is not the required mechanism for checking Windows registry keys or Windows service status. Option D is wrong because a remediation admin scan is not what defines the compliance check itself. The compliance logic must be created as a custom scan, and continuous monitoring requires the persistent agent.

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.

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.

In FortiNAC-F, theGuest & Contractor Templateis a configuration object that defines the parameters for accounts created by sponsors or through self-registration. One of the critical security controls within this template is theLogin Availabilitysetting. This setting restricts the specific days and times during which a guest or contractor is permitted to authenticate and access the network.

As shown in the exhibit, the " StandardGuest " template hasLogin Availabilityset to " Specify Time " , with a schedule defined asMon-Fri, 6:00 AM to 7:00 PM. If a guest user attempts to connect or authenticate at8:00 PM, which is outside of the permitted window, FortiNAC-F ' s policy engine will automatically deny the authentication request. When an authentication attempt is denied due to schedule restrictions, the system does not move the host into the " Authenticated " or " Registered " state required for production access. Instead, the host ismarked as non-authenticatedin the adapter or host view.

This behavior ensures that even if a guest possesses valid credentials, their access is strictly bound by the organizational policy for visitor hours. The host will typically remain in its current isolation or registration VLAN, and the user will see a message on the captive portal indicating that their account is not currently authorized for login. It is important to distinguish this from " at-risk " (C), which relates to security scan failures, or " rogue " (B), which typically refers to unknown devices that have not yet been associated with a valid account or profiling rule.

" Login Availabilitydefines the timeframe during which the guest or contractor account is valid for network access. This schedule is enforced at the time of authentication. If a user attempts to log in outside of the designated window, the authentication is rejected by the system. Consequently, the host record will reflect anon-authenticatedstatus, and the device will remain restricted to the isolation or registration network until a valid login window is reached. " —FortiNAC-F Administration Guide: Guest and Contractor Templates Section.

The correct answers are C, D, and E . In a Layer 3 captive or isolation network design, FortiNAC-F port2 acts as the captive network service interface. The study guide states that Layer 3 captive networks require DHCP traffic to be relayed to port2 from the captive networks, and that the FortiNAC-F interface provides DHCP, DNS, and captive portal services to hosts assigned to any captive network.

That means the firewall path between the isolation VLANs and FortiNAC-F must allow DHCP , so isolated endpoints can receive an IP address from the FortiNAC-F captive network scope; DNS , so the isolated endpoint uses FortiNAC-F as its DNS server and gets redirected correctly; and HTTP/HTTPS , so the endpoint can load the FortiNAC-F captive portal page. The guide’s browser-redirection flow confirms this sequence: the host is moved to the isolation VLAN, requests DHCP, receives FortiNAC-F as the DNS server, performs DNS lookup, and then Apache/Tomcat services present the portal content.

Option A , DDNS, is not required for captive portal operation. Option B , NTP, may be useful for endpoint time accuracy or certificate-related workflows, but it is not part of the minimum traffic required for FortiNAC-F isolation network operation.

In FortiNAC-F, theSecurity Incidentsengine is used to automate responses to security threats reported by external devices. When an administrator wants to enforce a policy, such as quarantining contractors who access restricted websites, they must create aSecurity Rule. A Security Rule acts as the " if-then " logic that correlates incoming security data with the internal host database.

The documentation specifies that a Security Rule consists of three primary configurable components:

User/Host Profile:This identifieswhoorwhatthe rule applies to (in this case, " Contractors " ).

Trigger:This is theeventthat initiates the rule evaluation. In this scenario, the Trigger would be configured to match specific syslog messages or NetFlow data indicating access to prohibited websites. Triggers use filters to match vendor-specific data, such as a " Web Filter " event from a FortiGate.

Action:This defineswhathappens when the Trigger and User/Host Profile are matched. For this scenario, the administrator would select a " Quarantine " action, which instructs FortiNAC-F to move the endpoint to a restricted VLAN or apply a restrictive ACL.

While " Methods " (A) relate to authentication and " Security Strings " (E) are used for specific SNMP or CLI matching, they are not the structural components of a Security Rule in the Security Incidents menu.

" Security Rules are used to perform a specific action based on certain criteria... To configure a Security Rule, navigate toLogs > Security Incidents > Rules. Each rule requires aTriggerto define the event criteria, anActionto define the automated response (such as Quarantine), and aUser/Host Profileto limit the rule to specific groups. " —FortiNAC-F Administration Guide: Security Rules and Incident Management.