NSE6_FNC_AD-7.6 Dumps with Practice Exam Questions Answers

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.

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.

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 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.