Free Practice Questions for Fortinet NSE5_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 FortiNAC-FLogical Networkfeature is specifically designed to provide an abstraction layer between high-level security policies and the underlying physical network infrastructure. In large-scale deployments where different physical locations (like Building 1, 2, and 3 in the exhibit) use different local VLAN IDs for the same type of device (e.g., VLAN 10, 20, and 30 for printers), managing separate policies for each building would create significant administrative overhead.

By using aLogical Network, an administrator can create a single entity—for example, a logical network named " Printers " —and use it as the " Access Value " in a singleNetwork Access Policy. The mapping of this logical label to a specific physical VLAN occurs at theModel Configurationlevel for each network device. When a printer connects to a switch in Building 1, FortiNAC-F evaluates the policy, identifies that the printer should be in the " Printers " logical network, and checks the Model Configuration for that specific switch to see which VLAN ID is mapped to that label (VLAN 10). If the same printer moves to Building 3, the same single policy applies, but FortiNAC-F provisions it to VLAN 30 based on the local mapping for that building ' s switch.

This architectural approach ensures that policies remain consistent and easy to manage regardless of the complexity or variations in the local network topology.

" Logical Networks provide a way to define a network access requirement once and apply it across many different network devices that may use different VLAN IDs for that access... Each managed device can usedifferent VLAN IDs for the same Logical Network label. You can define the Logical Networks based on requirements and then associate the network to a VLAN ID when the managed device is configured in theModel Configuration. " —FortiNAC-F IoT Deployment Guide: Define the Logical Networks.

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.

When troubleshooting network access in FortiNAC-F, it is often necessary to verify exactly why a host has been granted a specific level of access. Since FortiNAC-F evaluates policies from the top down and assigns access based on the first match, an administrator needs a clear way to see the results of this evaluation for a specific live endpoint.

ThePolicy Details (C)view is the designated tool for this purpose. By navigating to theHosts > Hosts(or Adapter View) in the Administration UI, an administrator can search for the specific MAC address or IP of the host in question. Right-clicking on the host record reveals a context menu from whichPolicy Detailscan be selected. This view provides a real-time " look " into the policy engine ' s decision for that specific host, showing theNetwork Access Policythat was matched, theUser/Host Profilethat triggered the match, and the resultingNetwork Access Configuration(VLAN/ACL) currently applied.

WhilePolicy Logs (A)provide a historical record of all policy transitions across the system, they are often too high-volume to efficiently find a single host ' s current state. TheConnections view (B)shows the physical port and basic status but lacks the granular policy logic breakdown. ThePort Properties (D)view shows the configuration of the switch interface itself, which is only one component of the final access determination.

" To identify which policy is currently applied to a specific endpoint, use thePolicy Detailsview. Navigate toHosts > Hosts, select the host, right-click and choosePolicy Details. This window displays the specificNetwork Access Policy, User/Host Profile, and Network Access Configuration currently in effect for that host record. " —FortiNAC-F Administration Guide: Policy Details and Troubleshooting.

In FortiNAC-F,MAC notification traps(also known as MAC Move or MAC Change traps) are essential for achieving real-time visibility of endpoint connections and disconnections. When a device connects to a switch port, the switch generates an SNMP trap that informs FortiNAC-F of the new MAC address on that specific interface. This allows FortiNAC-F to immediately initiate the profiling and policy evaluation process without waiting for the next scheduled L2 poll.

According to theFortiNAC-F Administration GuideandSwitch Integrationdocumentation, MAC notification traps should be configured onall ports except uplink ports. Uplink ports are the interfaces that connect one switch to another or to the core network. Because these ports see the MAC addresses of every device on the downstream switches, enabling MAC notification on uplinks would cause the switch to send a massive volume of redundant traps to FortiNAC-F every time any device anywhere in the downstream branch moves or reconnects. This can overwhelm the FortiNAC-F process queue and degrade system performance.

By only enabling these traps on " edge " or " access " ports—where individual endpoints like PCs, printers, and VoIP phones connect—FortiNAC-F receives precise data regarding exactly where a device is physically located. Uplinks should be identified in the FortiNAC-F inventory as " Uplink " or " Learned Uplink, " which tells the system to ignore MAC data seen on those specific ports.

" To ensure accurate host tracking and optimal system performance, SNMP MAC notification traps must be enabled on all access (downlink) ports.Do not enable MAC notification traps on uplink ports, as this will result in excessive and unnecessary trap processing. Uplink ports should be excluded to prevent the system from attempting to map multiple downstream MAC addresses to a single infrastructure interface. " —FortiNAC-F Administration Guide: SNMP Configuration for Network Devices.

The correct answer is D . FortiNAC-F limits what a sponsor can create and manage through the administrator profile assigned to that sponsor. The study guide explains that sponsors can be restricted to specific guest or contractor templates and that the Manage Guests settings in the admin profile define whether the sponsor can manage all accounts, no accounts, or only accounts they created. It also states that allowed templates are defined in the admin profile, meaning each department can be given access only to its own contractor template.

The contractor template defines account fields, role values, authentication method, account duration, and related account properties, but it does not by itself restrict what a sponsor can manage. Portal settings control how users interact with the captive portal or kiosk page, not sponsor administrative scope. A user/host profile is used for matching users or hosts in policy decisions; it does not delegate sponsor permissions. For departmental separation, the administrator must create sponsor-specific administrative profiles that allow only the appropriate templates and account-management scope.

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.