Ultimate Guide to Prepare NSE5_FNC_AD_7.6 with Accurate PDF Questions [May 26, 2026]
Pass Fortinet With VCEDumps Exam Dumps
Fortinet NSE5_FNC_AD_7.6 Exam Syllabus Topics:
| Topic | Details |
|---|---|
| Topic 1 |
|
| Topic 3 |
|
| Topic 4 |
|
| Topic 5 |
|
NEW QUESTION # 10
Refer to the exhibit.
What would FortiNAC-F generate if only one of the security fitters is satisfied?
- A. A normal alarm
- B. A security alarm
- C. A normal event
- D. A security event
Answer: C
Explanation:
In FortiNAC-F, Security Triggers are used to identify specific security-related activities based on incoming data such as Syslog messages or SNMP traps from external security devices (like a FortiGate or an IDS). These triggers act as a filtering mechanism to determine if an incoming notification should be escalated from a standard system event to a Security Event.
According to the FortiNAC-F Administrator Guide and relevant training materials for versions 7.2 and 7.4, the Filter Match setting is the critical logic gate for this process. As seen in the exhibit, the "Filter Match" configuration is set to "All". This means that for the Security Trigger named "Infected File Detected" to "fire" and generate a Security Event or a subsequent Security Alarm, every single filter listed in the Security Filters table must be satisfied simultaneously by the incoming data.
In the provided exhibit, there are two filters: one looking for the Vendor "Fortinet" and another looking for the Sub Type "virus". If only one of these filters is satisfied (for example, a message from Fortinet that does not contain the "virus" subtype), the logic for the Security Trigger is not met. Consequently, FortiNAC-F does not escalate the notification. Instead, it processes the incoming data as a Normal Event, which is recorded in the Event Log but does not trigger the automated security response workflows associated with security alarms.
"The Filter Match option defines the logic used when multiple filters are defined. If 'All' is selected, then all filter criteria must be met in order for the trigger to fire and a Security Event to be generated. If the criteria are not met, the incoming data is processed as a normal event. If 'Any' is selected, the trigger fires if at least one of the filters matches." - FortiNAC-F Administration Guide: Security Triggers Section.
NEW QUESTION # 11
During an evaluation of state-based enforcement, an administrator discovers that ports that should not be under enforcement have been added to enforcement groups.
In which view would the administrator be able to identify who added the ports to the groups?
(Selected)
- A. The Event Management view
- B. The Admin Auditing view
- C. The Security Events view
- D. The Port Changes view
Answer: B
Explanation:
In FortiNAC-F, accountability and forensic tracking of configuration changes are managed through the Admin Auditing functionality. When an administrator performs an action that modifies the system state-such as creating a policy, changing a device's status, or adding a switch port to an Enforcement Group-the system generates an audit record. This record is essential for troubleshooting scenarios where unauthorized or accidental configuration changes have occurred, leading to unintended network behavior.
The Admin Auditing view (found under Logs > Admin Auditing) provides a comprehensive log of the "Who, What, and When" for every administrative session. Each entry includes the username of the administrator, the source IP address from which they accessed the FortiNAC-F console, a precise timestamp, and a detailed description of the modification. In the scenario described, where ports have been incorrectly added to enforcement groups, the Admin Auditing view allows a supervisor to filter by the specific "Port" or "Group" object to identify exactly which administrator executed the command.
In contrast, the Event Management view (B) is designed to monitor system and network events, such as RADIUS authentications, host connections, and SNMP trap arrivals. While it tracks system activity, it does not typically log the manual configuration changes performed by admins. The Port Changes view (C) tracks the operational history of a port (such as VLAN assignment changes and host movements) but does not attribute the administrative assignment of the port to a group. Finally, the Security Events view (D) is dedicated to alerts triggered by security rules and external threat feeds.
"Admin Auditing displays a record of all modifications made to the FortiNAC-F system by an administrator. This view includes the administrator's name, the date and time of the change, and a description of the action taken. It is the primary resource for determining which administrative user performed a specific configuration change, such as modifying port group memberships or altering policy settings." - FortiNAC-F Administration Guide: Logging and Auditing Section.
NEW QUESTION # 12
An organization wants to add a FortiNAC-F Manager to simplify their large FortiNAC-F deployment.
Which two policy types can be managed globally? (Choose two.)
- A. Authentication
- B. Endpoint Compliance
- C. Network Access
- D. Supplicant EasyConnect
Answer: B,C
Explanation:
The FortiNAC-F Manager is 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 the FortiNAC 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 specific Authentication (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 enables Global Policy Management, allowing for the creation and distribution of policies across all managed CA appliances. This includes Network Access Policies, which control VLAN and ACL assignment, and Endpoint 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.
NEW QUESTION # 13
How can an administrator configure FortiNAC-F to normalize incoming syslog event levels across vendors?
- A. Configure severity mappings.
- B. Configure the vendor OUI settings.
- C. Configure event to alarm mappings.
- D. Configure the security rule settings.
Answer: A
Explanation:
FortiNAC-F serves as a central manager for security events originating from a diverse ecosystem of third-party security appliances, such as FortiGate, Check Point, and Cisco. Each vendor utilizes its own internal scale for severity levels within syslog messages (e.g., Check Point uses a 1-5 scale, while others may use 0-7). To provide a consistent response regardless of the source, FortiNAC-F uses Severity Mappings to normalize these incoming values.
According to the FortiNAC-F Administration Guide, severity mappings allow the administrator to translate vendor-specific threat levels into standardized FortiNAC Security Levels (such as High, Medium, or Low Violation). When a syslog message arrives, the parser extracts the vendor's severity code, and the system immediately references the Security Event Severity Level Mappings table to determine how that event should be categorized internally. This normalization is vital because it allows a single Security Alarm to be configured to respond to any "High Violation" event, whether it was reported as a "Critical" by one vendor or a "Level 5" by another. Without these mappings, the administrator would have to create separate, redundant security rules for every vendor to account for their different naming conventions and numerical scales.
"Each vendor defines its own severity levels for syslog messages. The following table shows the equivalent FortiNAC security level... To normalize these events, configure the Severity Level Mappings found in the device integration guides. This allows FortiNAC to generate a consistent security event that can then trigger an alarm regardless of the reporting vendor's specific terminology." - FortiNAC-F Administration Guide: Vendor Severity Levels and Syslog Management.
NEW QUESTION # 14
Where should you configure MAC notification traps on a supported switch?
- A. Only on ports defined as learned uplinks
- B. Only on ports that generate linkup and linkdown traps
- C. On all ports on the switch
- D. On all ports except uplink ports
Answer: D
Explanation:
In FortiNAC-F, MAC notification traps (also known as MAC Move or MAC Change traps) are essential for achieving real-time visibility of endpoint connections and disconnections. When a device connects to a switch port, the switch generates an SNMP trap that informs FortiNAC-F of the new MAC address on that specific interface. This allows FortiNAC-F to immediately initiate the profiling and policy evaluation process without waiting for the next scheduled L2 poll.
According to the FortiNAC-F Administration Guide and Switch Integration documentation, MAC notification traps should be configured on all ports except uplink ports. Uplink ports are the interfaces that connect one switch to another or to the core network. Because these ports see the MAC addresses of every device on the downstream switches, enabling MAC notification on uplinks would cause the switch to send a massive volume of redundant traps to FortiNAC-F every time any device anywhere in the downstream branch moves or reconnects. This can overwhelm the FortiNAC-F process queue and degrade system performance.
By only enabling these traps on "edge" or "access" ports-where individual endpoints like PCs, printers, and VoIP phones connect-FortiNAC-F receives precise data regarding exactly where a device is physically located. Uplinks should be identified in the FortiNAC-F inventory as "Uplink" or "Learned Uplink," which tells the system to ignore MAC data seen on those specific ports.
"To ensure accurate host tracking and optimal system performance, SNMP MAC notification traps must be enabled on all access (downlink) ports. Do not enable MAC notification traps on uplink ports, as this will result in excessive and unnecessary trap processing. Uplink ports should be excluded to prevent the system from attempting to map multiple downstream MAC addresses to a single infrastructure interface." - FortiNAC-F Administration Guide: SNMP Configuration for Network Devices.
NEW QUESTION # 15
While discovering network infrastructure devices, a switch appears in the inventory topology with a question mark (?) on the icon. What would cause this?
- A. A read-only SNMP community siring was used.
- B. The SNMP ObjectlD is not recognized by FortiNAC-F.
- C. The wrong SNMP community string was entered during discovery.
- D. SNMP is not enabled on the switch.
Answer: B
Explanation:
In FortiNAC-F, the Inventory topology uses 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 its System ObjectID (sysObjectID) to identify the specific make and model. This OID is then compared against the internal database of supported device mappings.
A question mark (?) icon appearing on a discovered switch indicates that while the discovery process successfully communicated with the device (meaning SNMP credentials were correct), the SNMP ObjectID is not recognized or 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 '?' icon indicate the currently running version does not have a mapping for that device's System 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.
NEW QUESTION # 16
Refer to the exhibit.
What will happen to the host of a guest user created from this template if the time of connection is 8:00 PM?
- A. The host will be administratively disabled.
- B. The host will be marked as a rogue device.
- C. The host will be marked as non-authenticated.
- D. The host will be marked as at-risk.
Answer: C
Explanation:
In FortiNAC-F, the Guest & Contractor Template is a configuration object that defines the parameters for accounts created by sponsors or through self-registration. One of the critical security controls within this template is the Login Availability setting. This setting restricts the specific days and times during which a guest or contractor is permitted to authenticate and access the network.
As shown in the exhibit, the "StandardGuest" template has Login Availability set to "Specify Time", with a schedule defined as Mon-Fri, 6:00 AM to 7:00 PM. If a guest user attempts to connect or authenticate at 8:00 PM, which is outside of the permitted window, FortiNAC-F's policy engine will automatically deny the authentication request. When an authentication attempt is denied due to schedule restrictions, the system does not move the host into the "Authenticated" or "Registered" state required for production access. Instead, the host is marked as non-authenticated in the adapter or host view.
This behavior ensures that even if a guest possesses valid credentials, their access is strictly bound by the organizational policy for visitor hours. The host will typically remain in its current isolation or registration VLAN, and the user will see a message on the captive portal indicating that their account is not currently authorized for login. It is important to distinguish this from "at-risk" (C), which relates to security scan failures, or "rogue" (B), which typically refers to unknown devices that have not yet been associated with a valid account or profiling rule.
"Login Availability defines the timeframe during which the guest or contractor account is valid for network access. This schedule is enforced at the time of authentication. If a user attempts to log in outside of the designated window, the authentication is rejected by the system. Consequently, the host record will reflect a non-authenticated status, and the device will remain restricted to the isolation or registration network until a valid login window is reached." - FortiNAC-F Administration Guide: Guest and Contractor Templates Section.
NEW QUESTION # 17
An administrator wants FortiNAC-F to return a group of user-defined RADIUS attributes in RADIUS responses.
Which condition must be true to achieve this?
- A. Inbound RADIUS requests must contain the Calling-Station-ID attribute.
- B. The requesting device must support RFC 5176.
- C. RADIUS accounting must be enabled on the FortiNAC-F RADIUS server configuration.
- D. The device models in the inventory view must be configured for proxy-based authentication.
Answer: A
Explanation:
In FortiNAC-F, the RADIUS Attribute Groups feature allows administrators to return customized RADIUS attributes (such as specific VLAN IDs, filter IDs, or vendor-specific attributes) in an Access-Accept packet 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 the FortiNAC-F Generic RADIUS Wired Cookbook and the RADIUS Attribute Groups section of the Administration Guide, there is one critical prerequisite for this feature to function: the inbound RADIUS request must contain the Calling-Station-ID attribute. The Calling-Station-ID typically contains the MAC address of 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, will not include any user-defined RADIUS attributes in 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.
NEW QUESTION # 18
Refer to the exhibit.
An administrator wants to use FortiNAC-F to automatically provision printers throughout their organization. Each building uses its own local VLAN for printers.
Which FortiNAC-F feature would allow this to be accomplished with a single network access policy?
- A. Logical networks
- B. Dynamic host groups
- C. Preferred VLAN designations
- D. Device profiling rules
Answer: A
Explanation:
The FortiNAC-F Logical Network feature is specifically designed to provide an abstraction layer between high-level security policies and the underlying physical network infrastructure. In large-scale deployments where different physical locations (like Building 1, 2, and 3 in the exhibit) use different local VLAN IDs for the same type of device (e.g., VLAN 10, 20, and 30 for printers), managing separate policies for each building would create significant administrative overhead.
By using a Logical Network, an administrator can create a single entity-for example, a logical network named "Printers"-and use it as the "Access Value" in a single Network Access Policy. The mapping of this logical label to a specific physical VLAN occurs at the Model Configuration level for each network device. When a printer connects to a switch in Building 1, FortiNAC-F evaluates the policy, identifies that the printer should be in the "Printers" logical network, and checks the Model Configuration for that specific switch to see which VLAN ID is mapped to that label (VLAN 10). If the same printer moves to Building 3, the same single policy applies, but FortiNAC-F provisions it to VLAN 30 based on the local mapping for that building's switch.
This architectural approach ensures that policies remain consistent and easy to manage regardless of the complexity or variations in the local network topology.
"Logical Networks provide a way to define a network access requirement once and apply it across many different network devices that may use different VLAN IDs for that access... Each managed device can use different VLAN IDs for the same Logical Network label. You can define the Logical Networks based on requirements and then associate the network to a VLAN ID when the managed device is configured in the Model Configuration." - FortiNAC-F IoT Deployment Guide: Define the Logical Networks.
NEW QUESTION # 19
When configuring isolation networks in the configuration wizard, why does a layer 3 network typo allow for mora than ono DHCP scope for each isolation network typo?
- A. Any scopes beyond the first scope are used if the initial scope runs out of IP addresses.
- B. Configuring more than one DHCP scope allows for DHCP server redundancy
- C. The layer 3 network type allows for one scope for each possible host status.
- D. There can be more than one isolation network of each type
Answer: D
Explanation:
In FortiNAC-F, the Layer 3 Network type is specifically designed for deployments where the isolation networks-such as Registration, Remediation, and Dead End-are separated from the FortiNAC appliance's service interface (port2) by one or more routers. This architecture is common in large, distributed enterprise environments where endpoints in different physical locations or branches must be isolated into subnets that are local to their respective network equipment.
The reason the Configuration Wizard allows for more than one DHCP scope for a single isolation network type (state) is that there can be more than one isolation network of each type across the infrastructure. For instance, if an organization has three different sites, each site might require its own unique Layer 3 registration subnet to ensure efficient routing and to accommodate local IP address management. By allowing multiple scopes for the "Registration" state, FortiNAC can provide the appropriate IP address, gateway, and DNS settings to a rogue host regardless of which site's registration VLAN it is placed into.
When an endpoint is isolated, the network infrastructure (via DHCP Relay/IP Helper) directs the DHCP request to the FortiNAC service interface. FortiNAC then identifies which scope to use based on the incoming request's gateway information. This flexibility ensures that the system is not limited to a single flat subnet for each isolation state, supporting a scalable, multi-routed network topology.
"Multiple scopes are allowed for each isolation state (Registration, Remediation, Dead End, VPN, Authentication, Isolation, and Access Point Management). Within these scopes, multiple ranges in the lease pool are also permitted... This configWizard option is used when Isolation Networks are separated from the FortiNAC Appliance's port2 interface by a router." - FortiNAC-F Configuration Wizard Reference Manual: Layer 3 Network Section.
NEW QUESTION # 20
While deploying FortiNAC-F devices in a 1+1 HA configuration, the administrator has chosen to use the shared IP address option.
Which condition must be met for this type of deployment?
- A. The primary and secondary administrative interfaces are on the same subnet.
- B. The isolation network type is layer 3.
- C. The isolation network type is Layer 2.
- D. There is a direct cable link between FortiNAC-F devices.
Answer: A
Explanation:
In a 1+1 High Availability (HA) deployment, FortiNAC-F supports two primary methods for management access: individual IP addresses or a Shared IP Address (also known as a Virtual IP or VIP). The Shared IP option is part of a Layer 2 HA design, which simplifies administration by providing a single URL or IP that always points to whichever appliance is currently in the "Active" or "In Control" state.
For a Shared IP configuration to function correctly, the Primary and Secondary administrative interfaces (port1) must be on the same subnet. This requirement exists because the Shared IP is a logical address that is dynamically assigned to the physical interface of the active unit. Since only one unit can own the IP at a time, both units must reside on the same broadcast domain (Layer 2) to ensure that ARP requests for the Shared IP are correctly answered and that the gateway remains reachable regardless of which unit is active. If the appliances were on different subnets (a Layer 3 HA design), a shared IP could not be used because it cannot "float" across different network segments; instead, administrators would need to manage each unit via its unique physical IP or use a FortiNAC Manager.
"For L2 HA configurations, click the Use Shared IP Address checkbox and enter the Shared IP Address information... If your Primary and Secondary Servers are not in the same subnet, do not use a shared IP address. The shared IP address moves between appliances during a failover and recovery and requires both units to reside on the same network." - FortiNAC-F High Availability Reference Manual: Shared IP Configuration.
NEW QUESTION # 21
While deploying FortiNAC-F devices in a 1+1 HA configuration, the administrator has chosen to use the shared IP address option.
Which condition must be met for this type of deployment?
- A. The primary and secondary administrative interfaces are on the same subnet.
- B. The isolation network type is layer 3.
- C. The isolation network type is Layer 2.
- D. There is a direct cable link between FortiNAC-F devices.
Answer: A
Explanation:
In a 1+1 High Availability (HA) deployment, FortiNAC-F supports two primary methods for management access: individual IP addresses or a Shared IP Address (also known as a Virtual IP or VIP). The Shared IP option is part of a Layer 2 HA design, which simplifies administration by providing a single URL or IP that always points to whichever appliance is currently in the "Active" or "In Control" state.
For a Shared IP configuration to function correctly, the Primary and Secondary administrative interfaces (port1) must be on the same subnet. This requirement exists because the Shared IP is a logical address that is dynamically assigned to the physical interface of the active unit. Since only one unit can own the IP at a time, both units must reside on the same broadcast domain (Layer 2) to ensure that ARP requests for the Shared IP are correctly answered and that the gateway remains reachable regardless of which unit is active. If the appliances were on different subnets (a Layer 3 HA design), a shared IP could not be used because it cannot "float" across different network segments; instead, administrators would need to manage each unit via its unique physical IP or use a FortiNAC Manager.
"For L2 HA configurations, click the Use Shared IP Address checkbox and enter the Shared IP Address information... If your Primary and Secondary Servers are not in the same subnet, do not use a shared IP address. The shared IP address moves between appliances during a failover and recovery and requires both units to reside on the same network." - FortiNAC-F High Availability Reference Manual: Shared IP Configuration.
NEW QUESTION # 22
Refer to the exhibit.
A FortiNAC-F N+1 HA configuration is shown.
What will occur if CA-2 fails?
- A. CA-3 will continue to operate as a secondary in an N+1 HA configuration.
- B. CA-1 and CA-3 will operate as a 1+1 HA cluster with CA-3 acting as a hot standby.
- C. CA-3 will be promoted to a primary and FortiNAC-F manager will load balance between CA-1 and CA-3.
- D. CA-3 will be promoted to a primary and share management responsibilities with CA-1.
Answer: A
Explanation:
In an N+1 High Availability (HA) configuration, a single secondary Control and Application (CA) server provides backup for multiple primary CA servers. The FortiNAC-F Manager (FortiNAC-M) acts as the centralized orchestrator for this cluster, monitoring the health of all participating nodes.
According to the FortiNAC-F 7.6.0 N+1 Failover Reference Manual, when a primary CA (such as CA-2 in the exhibit) fails, the secondary CA (CA-3) is automatically promoted by the Manager to take over the specific workload and database functions of that failed primary. Crucially, the documentation specifies that even after this promotion, the system architecture maintains its N+1 logic. The secondary CA effectively "assumes the identity" of the failed primary while continuing to operate within the N+1 framework established by the Manager.
It does not merge with CA-1 to form a traditional 1+1 active/passive cluster (A), nor does it engage in load balancing (D), as FortiNAC-F HA is designed for redundancy and failover rather than active traffic distribution. Furthermore, CA-3 does not "share" management with CA-1 (C); it independently handles the tasks originally assigned to CA-2. Throughout this failover state, the Manager continues to oversee the group, and CA-3 remains the designated secondary unit currently acting in a primary capacity for the downed node until CA-2 is restored.
"In an N+1 Failover Group, the Secondary CA is designed to take over the functionality of any single failed primary component within the group. The FortiNAC Manager monitors the primaries and initiates the failover to the secondary... Once failover occurs, the secondary continues to operate as the backup unit for the failed primary while remaining part of the managed N+1 HA configuration." - FortiNAC-F 7.6.0 N+1 Failover Reference Manual: Failover Behavior Section.
NEW QUESTION # 23
A user was attempting to register their host through the registration captive portal. After successfully registering, the host remained in the registration VLAN. Which two conditions would cause this behavior? (Choose two.)
- A. There is another unregistered host on the same port
- B. The port default VLAN is the same as the Registration VLAN.
- C. The wrong agent s installed.
- D. There is no agent installed on the host.
Answer: A,B
Explanation:
The process of moving a host from a Registration VLAN to a Production VLAN (Access VLAN) is a fundamental part of the FortiNAC-F "VLAN steering" workflow. When a host successfully registers via the captive portal, FortiNAC-F evaluates its Network Access Policies to determine the correct VLAN. If the host remains stuck in the Registration VLAN despite a successful registration, it is typically due to port-level restrictions or the presence of other unregistered devices.
The two most common reasons for this behavior as per the documentation are:
The port default VLAN is the same as the Registration VLAN: If the "Default VLAN" field in the switch port's model configuration is set to the same ID as the Registration VLAN, the port will not change state because FortiNAC-F believes it is already in its "normal" or "forced" state.
There is another unregistered host on the same port: FortiNAC-F maintains the security posture of the physical port. If multiple hosts are connected to a single port (e.g., via a hub or unmanaged switch) and at least one host remains "Rogue" (unregistered), FortiNAC-F will generally keep the entire port in the isolation/registration VLAN to prevent the unregistered host from gaining unauthorized access to the production network.
Issues with agents (A, B) typically prevent a host from completing compliance or registration but do not usually result in a "stuck" status after registration has already been marked as successful in the system.
"If a port is identified as having Multiple Hosts, and those hosts require different levels of access, FortiNAC remains in the most restrictive state (Registration or Isolation) until all hosts on that port are authorized... Additionally, verify the Default VLAN setting for the port; if the Default VLAN and Registration VLAN match, the system will not trigger a VLAN change upon registration." - FortiNAC-F Administration Guide: Troubleshooting Host Management.
NEW QUESTION # 24
......
Latest NSE5_FNC_AD_7.6 Exam Dumps - Valid and Updated Dumps: https://testinsides.vcedumps.com/NSE5_FNC_AD_7.6-examcollection.html
