Fortinet NSE6_FNC_AD-7.6 - Fortinet NSE 6 - FortiNAC-F 7.6 Administrator

The correct answer is C . The FortiNAC-F study guide explains that all VPN hosts are initially treated as unauthorized. For those unauthorized VPN hosts, the FortiGate firewall policy must allow traffic only to and from the FortiNAC-F VPN isolation interface and deny all other traffic. This forces the connecting VPN client into the FortiNAC-F validation process, including captive portal presentation and FortiNAC-F agent communication or download.

Options A and B are incorrect, and they appear duplicated in the question. The client is not supposed to be granted access only to the production DNS server while still unauthorized. FortiGate assigns DNS during VPN connection setup, with production DNS as primary and the FortiNAC-F VPN isolation interface as secondary, but the unauthorized firewall policy restricts useful access to FortiNAC-F so that validation can occur. Option D is wrong because the VPN client has already connected to the FortiGate VPN service; the authorization workflow requires access to the FortiNAC-F VPN isolation interface , not merely the FortiGate VPN interface.

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.

This behavior directly indicates that the matching Device Profiling Rule has Registration configured as Manual . The FortiNAC-F 7.6 Administrator Study Guide explains that when registration is Automatic , FortiNAC-F performs the configured registration operations immediately after the device matches the rule. When registration is Manual , however, the rule still matches and the device is successfully profiled and classified , but the registration settings are not executed until an authorized sponsor or administrator manually registers the device.

Consequently, the device can legitimately appear in Profiled Devices with its matched rule and assigned device type while the Registered column remains No . The Administration Guide confirms that this column specifically indicates whether the profiled device has been registered.

Option A is incorrect because rule confirmation determines whether an already-profiled device is periodically or subsequently revalidated against its associated rule; it does not control initial registration. Option B is incorrect because rules are evaluated in ranked order until the applicable match is processed. Option D concerns Persistent Agent communications and does not determine device-profiler registration status.

Study Guide Reference: Identification and Classification of Rogues → Device Profiling Rules → General Rule Information / Registration Settings , approximately pp. 110–111 .

In FortiNAC-F, theRADIUS Attribute Groupsfeature allows administrators to return customized RADIUS attributes (such as specific VLAN IDs, filter IDs, or vendor-specific attributes) in anAccess-Acceptpacket sent back to a network device. This is particularly useful for supporting " Generic RADIUS " devices that are not natively supported but can be managed using standard AVPairs.

According to theFortiNAC-F Generic RADIUS Wired Cookbookand theRADIUS Attribute Groups sectionof the Administration Guide, there is one critical prerequisite for this feature to function: theinbound RADIUS request must contain the Calling-Station-ID attribute. The Calling-Station-ID typically contains theMAC addressof the connecting endpoint. Because FortiNAC-F is a host-centric system, it uses the MAC address as the unique identifier to look up the host record, evaluate the associated Network Access Policy, and determine which Logical Network (and thus which Attribute Group) should be applied. If the incoming request lacks this attribute, FortiNAC-F cannot reliably identify the host and, as a safety mechanism, willnot include any user-defined RADIUS attributesin the response. This ensures that unauthorized or unidentifiable devices do not receive privileged access through misapplied attributes.

" Configure a set of attributes that must be included in the RADIUS Access-Accept packet returned by FortiNAC...Requirement: Inbound RADIUS request must contain Calling-Station-Id. Otherwise, FortiNAC will not include the RADIUS attributes.This attribute is used to identify the host and its current state within the FortiNAC database. " —FortiNAC-F 7.6.0 Generic RADIUS Wired Cookbook: Configure RADIUS Attribute Groups.

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 C . FortiNAC-F security automation does not rely only on a trigger and action. After a security alert is received and the security trigger is satisfied, FortiNAC-F can also evaluate an associated user/host profile before generating the security alarm and executing the action. The study guide explains that user/host profiles are the same profiles used by security policies and are used in security rules to leverage “who, what, where, and when” visibility information. This is exactly what the question requires: the rule must apply specifically to internal engineers , not every user who triggers the FortiGate web-filter category event.

A compliance policy is wrong because compliance policies evaluate endpoint health, posture, scans, or agent results; they do not scope FortiGate web-filter-triggered automation to a user population. A firewall policy is configured on FortiGate, not as the FortiNAC-F-side matching condition in the security rule. A profiling method is also wrong because profiling methods classify rogue or unknown devices, such as printers, cameras, or phones; they do not identify internal engineers for a security automation workflow. The user/host profile is the correct FortiNAC-F object because it lets the same FortiGate security trigger produce a different response depending on the matched user, host, group, location, or ownership context.

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

In a FortiNAC-F deployment, the configuration of theDHCP scopefor isolation networks (Registration, Remediation, etc.) must perfectly align with the underlying network infrastructure to ensure that isolated hosts can communicate with the FortiNAC appliance. In the provided exhibits, there is a clear discrepancy between theDHCP configurationand theNetwork Topology.

As shown in the " Network Topology " exhibit, theRegistration Networkresides on a router interface (or sub-interface) with the IP address192.168.180.1. This address represents the default gateway for any host placed into the Registration VLAN. However, the " DHCP configuration " exhibit shows the scope " REG-ScopeOne " configured with aGateway of 10.0.1.254. This 10.0.1.254 address belongs to the management/service network (port2 of FortiNAC), not the registration subnet. If a host in the Registration VLAN receives this incorrect gateway via DHCP, it will attempt to send all off-link traffic to an unreachable IP, preventing it from loading theCaptive Portalor communicating with the FortiNAC server.

According to theFortiNAC-F Configuration Wizard Reference, when defining a Layer 3 network scope, the " Gateway " field must contain the IP address of the router interface that acts as the gateway for that specific isolation VLAN. The FortiNAC appliance itself usually sits on a different subnet, and traffic is directed to it via the router ' s DHCP Relay (IP Helper) and DNS redirection.

" When configuring scopes for a Layer 3 network, theGatewayvalue must be the IP address of the router interface for that subnet. This allows the host to reach its local gateway to route traffic. If the gateway is misconfigured, the host will be unable to reach the FortiNAC eth1/port2 interface for registration... Ensure the Gateway matches the network topology for the isolation VLAN. " —FortiNAC-F Configuration Wizard Reference Manual: DHCP Scopes.