Free Fortinet NSE 5 - FortiNAC-F 7.6 Administrator Practice Questions

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.

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.

TheFortiNAC-F Manager (FortiNAC-M)is designed as a centralized management platform for large-scale distributed environments where multiple FortiNAC-F Control and Application (CA) appliances are deployed across different sites. According to theFortiNAC-F Manager Administration Guide, the deployment of a Manager simplifies administrative overhead in three specific ways:

First, it providesGlobal Version Control (B). The Manager serves as a central repository for firmware and software updates, allowing administrators to push specific versions to all managed CAs simultaneously, ensuring consistency across the entire fabric. Second, it enablesPooled Licenses (D). Instead of purchasing and managing individual licenses for every CA, licenses are centralized on the Manager. The Manager then distributes these licenses to the CAs as needed based on their host counts. This " floating " license model optimizes cost and prevents individual sites from running out of capacity while others have excess. Third, it offersGlobal Visibility (E). The Manager aggregates host and device data from every managed CA into a single console. This " single pane of glass " allows an administrator to search for a specific MAC address or user across the entire global organization without logging into individual servers.

While the Manager can assist with configuration templates, authentication security policies (C) and infrastructure modeling (A) are still predominantly managed at the local CA level to ensure site-specific logic and performance.

" The FortiNAC Manager provides a central management console for multiple FortiNAC-F servers (CAs). Key benefits include: •License Management: Licenses are pooled on the Manager and allocated to managed CAs as needed. •Software Management: Firmware updates can be centrally managed and pushed to all CAs from the Manager. •Centralized Monitoring: Provides a global view of all hosts, adapters, and events across the entire managed environment. " —FortiNAC-F Manager Administration Guide: Overview and Benefits.