Important Fortinet NSE6_FNC_AD-7.6 Exam Questions

Answer: A

Explanation:

The correct answer is A. In FortiNAC-F, device profiling rules are used primarily to classify unknown or untrusted devices when they are first discovered. The study guide explains that when a device does not already exist in the database, FortiNAC-F adds it, treats it as a rogue, and evaluates it against enabled device profiling rules. It also states that devices are initially evaluated against device profiling rules only if they do not already exist in the database, because this avoids unnecessary repeated evaluation of known devices.

The exhibit also matters: the rules are enabled and set to Automatic registration, but Confirm Rule On Connect is not enabled and Confirm Rule Interval is set to None. That means FortiNAC-F will not automatically revalidate already-profiled or trusted devices every time they connect. Option B is wrong because trusted devices are not repeatedly evaluated unless rule confirmation is configured. Option C is too broad because all hosts are not processed through profiling rules on every connection. Option D is also wrong because changing location does not by itself force automatic device profiling; location can be used as a rule method, but the automatic evaluation described here applies when the rogue device is initially added to the database.

Answer: D

Explanation:

In FortiNAC-F, the maximum number of conference attendees/accounts is controlled by the Guest & Contractor template, not by the sponsor's administrative profile. The FortiNAC-F 7.6 Administrator Study Guide states that conference accounts are initiated by a sponsor but automatically generated by FortiNAC-F, and specifically that ''the maximum number of attendees is defined within the template.''

The Administration Guide provides the corresponding configuration field: Max Number Of Accounts, which is available when Visitor Type = Conference. Enabling this option allows the administrator to enter the maximum number of accounts that can ever be created using that template. Therefore, a value of exactly 30 can be configured; there is no requirement to use multiples of 25.

The administrative profile instead determines sponsor capabilities such as permitted account types, allowed templates, account-management scope, and maximum account duration. It does not define the numerical conference-account ceiling.

Thus, to enforce a limit of 30 conference accounts, configure Max Number Of Accounts = 30 in the conference Guest & Contractor template.

Study Guide Reference: Guest and Contractor Management Creating Conference Accounts, pp. 292--302.

Answer: B, C

Explanation:

Comprehensive and Detailed Explanation From Exact Extract of FortiNAC-F 7.6 Administrator Guide or Knowledge:

Exact Extract:

The FortiNAC-F study guide states that MAC notification traps are preferred because FortiNAC-F does not need to connect back to the infrastructure device every time a link-up or link-down trap is received. The required MAC and port information is already included in the MAC notification trap, which makes database updates faster and uses fewer resources. It also states that hosts and devices connected through hubs or IP phones are seen immediately, even when the downstream device cannot generate link-up or link-down traps.

Technical Deep Dive:

The correct answers are B and C. With link-up/link-down traps, the trap only tells FortiNAC-F that an interface changed state. FortiNAC-F then has to perform an L2 poll against the switch forwarding table to discover which MAC address appeared or disappeared. That means extra SNMP/CLI activity, more delay, and more processing on both FortiNAC-F and the switch. The guide confirms that link traps trigger FortiNAC-F to perform a Layer 2 poll, while MAC notification traps directly contain the learned or removed MAC address and associated port.

Option A is wrong because MAC notification traps are Layer 2 visibility events. They identify MAC address and port, not IP address. IP-to-MAC correlation comes from Layer 3 polling or DHCP fingerprinting, not MAC notification traps. Option D is badly worded and should not be selected: MAC notification traps do provide faster updates, but the processing overhead is reduced, not slightly increased.

Operationally, on supported switches you enable SNMP traps for MAC address-table changes and point the trap destination to FortiNAC-F. On Cisco-style infrastructure, this is usually done with commands such as snmp-server host <FortiNAC-IP> version 2c <community> plus MAC notification trap configuration. Do not enable MAC notification traps on uplinks, because uplinks learn many downstream MAC addresses and would create misleading endpoint-location data.

Answer: A

Explanation:

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.

Answer: B, D

Explanation:

TheFortiNAC-F Manageris designed to centralize the management of multiple Control and Application (CA) appliances, ensuring consistent security posture across a distributed enterprise. To achieve this, the Manager allows administrators to define and distribute specific types of policies globally rather than configuring them on each individual CA.

According to theFortiNAC Manager Guide, the two primary policy types that are managed globally are:

Network Access Policies (D):These policies define the 'If-Then' logic for network entry. By managing these at the global level, an administrator can ensure that a 'Contractor' receives the same restricted access regardless of which branch office or campus they connect to.

Endpoint Compliance Policies (B):Global management of compliance policies---which consist of scans and configurations---allows for a unified security baseline. For example, a global policy can mandate that all Windows devices across the entire organization must have a specific antivirus version installed and active before gaining access to the production network.

While the Manager provides visibility into authentication events and can synchronize directory data, the specificAuthentication(A) configurations (like local RADIUS secrets or specific LDAP server links) are often localized to the CA to account for site-specific infrastructure.Supplicant EasyConnect(C) is a feature set for onboarding, but the structural 'Global Policy' engine focuses primarily on the Access and Compliance frameworks.

'The FortiNAC Manager enablesGlobal Policy Management, allowing for the creation and distribution of policies across all managed CA appliances. This includesNetwork Access Policies, which control VLAN and ACL assignment, andEndpoint Compliance Policies, which define the security requirements for hosts. Centralizing these policies ensures that security standards are enforced uniformly across the global network fabric.' ---FortiNAC Manager Administration Guide: Global Policy Management Overview.