NSE6_FNC-7-2 Practice Questions

Fortinac-admin-operations, P. 391

The command and output shown in the exhibit indicate that the host FortiNAC-Secondary is

referencing FortiNAC-Primary, and it states "Slave is active." In database replication terminology

within a high availability setup, the term "Slave is active" typically means that the secondary server

(slave) is actively receiving data from the primary server (master). This implies that the

synchronization process from the primary to the secondary database has been successful and is

currently active​​.

Reference

FortiNAC 7.2 Study Guide, Security Policies section

Reference: https://docs.fortinet.com/document/fortinac/8.8.0/administration-guide/167668/addor-modify-a-rule

The FortiNAC 7.2 Study Guide does not explicitly mention Dot1x Auto Registration and MDM

integration as the specific device classification options for automatic and transparent registration to

the end user. However, based on the general functioning of FortiNAC, Dot1x Auto Registration and

MDM integration are typically used for such purposes. The guide discusses automatic device

registration in the context of profiling rules

The persistent agent has the ability to display messages on the desktop of an endpoint. These

messages can target an individual host, a group of hosts, or all hosts with the persistent agent

installed. The messaging options include sending a message content with an optional web address

link

To gather a list of installed applications and application details from a host, two methods can be

used:

Agent technology: FortiNAC uses agent technology to collect all installed applications on an

endpoint.

Integration with MDMs (Mobile Device Management systems): MDMs that support application

gathering can be integrated with FortiNAC to collect application information​​.

Reference

FortiNAC 7.2 Study Guide, page 302

Thank you for your visit.

:

:

To allow FortiNAC to process incoming syslog messages from an unknown vendor, two steps must be

taken:

Creation of a customized event parser: This enables FortiNAC to parse and integrate syslog messages

from any vendor or device, as long as the messages are in CSV, CEF, or Tag/Value format​​.

Modeling the device in the Topology view: Any device that sends syslog messages to FortiNAC must

be modeled in this view. FortiNAC will not process syslog or trap messages unless the source address

belongs to a device modeled in the topology​​.

Reference

FortiNAC 7.2 Study Guide, pages 428 and 399