Pass the Fortinet NSE 6 Network Security Specialist NSE6_FNC_AD-7.6 Questions and answers with ExamsMirror

In FortiNAC-F, theInventory topologyuses specific icons to represent the status and model of discovered network infrastructure. When a switch or other network device is discovered via SNMP, FortiNAC-F retrieves itsSystem ObjectID (sysObjectID)to identify the specific make and model. This OID is then compared against the internal database of supported device mappings.

Aquestion mark (?)icon appearing on a discovered switch indicates that while the discovery process successfully communicated with the device (meaning SNMP credentials were correct), theSNMP ObjectID is not recognizedor mapped in the current version of FortiNAC-F. This essentially means the device is " unsupported " by the current software out-of-the-box. Because the OID is unknown, FortiNAC-F does not know which CLI or SNMP command set to use for critical functions like L2 polling (host visibility) or VLAN switching (enforcement). To resolve this, an administrator can manually " Set Device Mapping " to a similar existing model or a " Generic SNMP Device " if only basic L3 visibility is required.

" Discovered devices displaying a ' ? ' iconindicate the currently running version does not have a mapping for that device ' sSystem OID(device is not supported). Device mappings are used to manage the device by performing functions such as L2/L3 Polling, Reading, and Switching VLANs. " —Fortinet Technical Tip: Options for devices unable to be modeled in Inventory.

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 integration between FortiNAC-F and Mobile Device Management (MDM) platforms (such as Microsoft Intune, VMware Workspace ONE, or Jamf) is a critical component for providing visibility into mobile assets that do not connect directly to the managed infrastructure via standard wired or wireless protocols.

According to theFortiNAC-F MDM Integration Guide, the communication between the FortiNAC-F appliance and the MDM server is handled throughREST APIcalls. FortiNAC-F acts as an API client, periodically polling the MDM server to retrieve device metadata, compliance status, and ownership information. If communication is failing, it is most likely because the API credentials (Client ID/Secret) are incorrect, the MDM ' s API endpoint is unreachable from the FortiNAC-F service port, or the SSL certificate presented by the MDM is not trusted by the FortiNAC-F root store.

While SSH (B) is used for switch CLI management and the Security Fabric (A) uses proprietary protocols for FortiGate synchronization, neither is the primary vehicle for MDM data exchange. SOAP API (D) is an older protocol that has been largely replaced by REST in modern FortiNAC integrations.

" FortiNAC integrates with MDM systems by utilizingREST APIcommunication to query the MDM database for device information. To establish this link, administrators must configure the MDM Service Connector with the appropriateAPI URLand authentication credentials. If the ' Test Connection ' fails, verify that the FortiNAC can reach the MDM provider via theREST APIport (usually HTTPS 443). " —FortiNAC-F Administration Guide: MDM Integration and Troubleshooting.

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.

A FortiNAC-F port can belong to both Forced Registration and Forced Remediation system groups . These enforcement groups are not mutually exclusive and are not evaluated according to a ranking between the groups. Instead, FortiNAC-F determines the applicable enforcement according to the state of each host connected through that point of connection .

The Study Guide explicitly demonstrates overlapping enforcement membership: all Building 1 ports are members of Forced Registration , while second- and third-floor ports are additionally members of Forced Remediation .

FortiNAC-F then applies state-specific logic:

A rogue/unregistered host on the port satisfies Forced Registration and is moved to the Registration isolation network.

An at-risk host on the same port satisfies Forced Remediation and is moved to the Quarantine/Remediation isolation network.

The exhibit is particularly relevant because the highlighted port shows Multiple Hosts connected. Each host is evaluated independently according to its state, so different enforcement mechanisms can apply to different endpoints sharing that port.

Therefore, placing the port in both groups enables both types of enforcement , depending on the state of the connected hosts.

Study Guide Reference: State-Based Control → System Groups; Logic to Determine Isolation; Non-Normal Status Device Evaluation , pp. 212–214 .

Top of Form

Bottom of Form

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 correct answer is A . FortiNAC-F Manager provides global visibility by collecting user and endpoint visibility information from the FortiNAC-F devices it manages, creating a centralized repository of users, hosts, and adapters. The study guide describes this as a global visibility function where endpoint information received by the Manager includes the local FortiNAC-F device from which the information came, allowing administrators to search and filter endpoint records across managed systems.

The key point is that this is not a real-time host-status trigger. Fortinet’s FortiNAC-F Manager documentation states that FortiNAC Manager controls host and user record replication between managed FortiNAC CA servers and initiates synchronization every five minutes between servers. It also states that global object synchronization uses an interval-based process, not an administrator manually synchronizing each CA for endpoint visibility.

Option B is wrong because host status changes are not treated as immediate real-time updates to every managed FortiNAC-F database. Option C is wrong because manual synchronization applies to global/shared configuration objects, not routine endpoint visibility updates. Option D is wrong because the mechanism is not a CA-side scheduled push to the Manager; the Manager-controlled synchronization/collection process is what maintains the shared endpoint view.

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.