NSE5_FNC_AD-7.6 Exam Study Guide Free Practice Test LAST UPDATED DATE Aug 11, 2026
The New NSE5_FNC_AD-7.6 2026 Updated Verified Study Guides & Best Courses
NEW QUESTION # 10
In which three ways would deploying a FortiNAC-F Manager into a large environment consisting of several FortiNAC-F CAs simplify management? (Choose three.)
- A. Global version control
- B. Global authentication security policies
- C. Pooled licenses
- D. Global infrastructure device inventory
- E. Global visibility
Answer: A,C,E
Explanation:
The FortiNAC-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 the FortiNAC-F Manager Administration Guide, the deployment of a Manager simplifies administrative overhead in three specific ways:
First, it provides Global 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 enables Pooled 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 offers Global 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.
NEW QUESTION # 11
An administrator wants to use FortiNAC-F to prevent internal engineers from accessing specific websites as defined in web filter categories on FortiGate.
In addition to a security trigger and associated action, which configuration must also be defined on FortiNAC-F?
- A. A user/host profile
- B. A firewall policy
- C. A compliance policy
- D. A profiling method
Answer: A
NEW QUESTION # 12
How can an administrator configure FortiNAC-F to normalize incoming syslog event levels across vendors?
- A. Configure the security rule settings.
- B. Configure severity mappings.
- C. Configure the vendor OUI settings.
- D. Configure event to alarm mappings.
Answer: B
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? scale, while others may use 0?). 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."
NEW QUESTION # 13
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. Device profiling rules
- B. Logical networks
- C. Dynamic host groups
- D. Preferred VLAN designations
Answer: B
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."
NEW QUESTION # 14
What must an administrator configure to allow FortiNAC-F to process incoming syslog messages that are not supported by default?
- A. A Log Receiver
- B. A Security Event Parser
- C. A Security Action
- D. A Syslog Service Connector
Answer: B
Explanation:
FortiNAC-F provides a robust engine for processing security notifications from third-party devices.
For standard integrations, such as FortiGate or Check Point, the system comes pre-loaded with templates to interpret incoming data. However, when an administrator needs FortiNAC-F to process syslog messages from a vendor or device that is not supported by default, they must configure a Security Event Parser.
The Security Event Parser acts as the translation layer. It uses regular expressions (Regex) or specific field mappings to identify key data points within a raw syslog string, such as the source IP address, the threat type, and the severity. Without a parser, FortiNAC-F may receive the syslog message but will be unable to "understand" its contents, meaning it cannot generate the necessary Security Event required to trigger automated responses. Once a parser is created, the system can extract the host's IP address from the message, resolve it to a MAC address via L3 polling, and then apply the appropriate security rules. This allows for the integration of any security appliance capable of sending RFC-compliant syslog messages.
"FortiNAC parses the information based on pre-defined security event parsers stored in FortiNAC's database... If the incoming message format is not recognized, a new Security Event Parser must be created to define how the system should extract data fields from the raw syslog message. This enables FortiNAC to generate a security event and take action based on the alarm configuration."
NEW QUESTION # 15
Which group type can have members added directly from the FortiNAC Control Manager?
- A. Port
- B. Host
- C. Administrator
- D. Device
Answer: C
NEW QUESTION # 16
Refer to the exhibits. What would happen if the highlighted port with connected hosts was placed in both the Forced Registration and Forced Remediation port groups?
- A. Multiple enforcement groups could not contain the same port.
- B. Enforcement would be applied only to rogue hosts
- C. Both types of enforcement would be applied
- D. Only the higher ranked enforcement group would be applied.
Answer: D
Explanation:
In FortiNAC-F, Port Groups are used to apply specific enforcement behaviors to switch ports.
When a port is assigned to an enforcement group, such as Forced Registration or Forced Remediation, FortiNAC-F overrides normal policy logic to force all connected adapters into that specific state. The exhibit shows a port (IF#13) with "Multiple Hosts" connected, which is a common scenario in environments using unmanaged switches or hubs downstream from a managed switch port.
According to the FortiNAC-F Administrator Guide, it is possible for a single port to be a member of multiple port groups. However, when those groups have conflicting enforcement actions--such as one group forcing a registration state and another forcing a remediation state--FortiNAC-F utilizes a ranking system to resolve the conflict. In the FortiNAC-F GUI under Network > Port Management > Port Groups, each group is assigned a rank. The system evaluates these ranks, and only the higher ranked enforcement group is applied to the port. If a port is in both a Forced Registration group and a Forced Remediation group, the group with the numerical priority (rank) will dictate the VLAN and access level assigned to all hosts on that port.
This mechanism ensures consistent behavior across the fabric. If the ranking determines that
"Forced Registration" is higher priority, then even a known host that is failing a compliance scan (which would normally trigger Remediation) will be held in the Registration VLAN because the port-level enforcement takes precedence based on its rank.
"A port can be a member of multiple groups. If more than one group has an enforcement assigned, the group with the highest rank (lowest numerical value) is used to determine the enforcement for the port. When a port is placed in a group with an enforcement, that enforcement is applied to all hosts connected to that port, regardless of the host's current state."
NEW QUESTION # 17
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 isolation network type is layer 3.
- B. The primary and secondary administrative interfaces are on the same subnet.
- C. There is a direct cable link between FortiNAC-F devices.
- D. The isolation network type is Layer 2.
Answer: B
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."
NEW QUESTION # 18
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. The port default VLAN is the same as the Registration VLAN.
- B. There is another unregistered host on the same port
- C. There is no agent installed on the host.
- D. The wrong agent s installed.
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.
NEW QUESTION # 19
During the testing of a newly modeled infrastructure switch, the administrator is not seeing hosts as they connect or move from one port to another.
What would cause this issue?
- A. The default scheduled polling is disabled.
- B. Layer 3 polling is failing.
- C. Contact polling is not configured.
- D. MAC notification traps are misconfigured.
Answer: D
Explanation:
FortiNAC-F relies on correctly configured MAC notification (link) traps to detect hosts connecting or moving between ports in real time. If these traps are misconfigured, the system will not receive port-level MAC change events, so newly connected or moved hosts will not be detected as expected.
NEW QUESTION # 20
When creating a device profiling rule, what are two advantages of registering the device in the host view? (Choose two.)
- A. The devices can be associated with a user.
- B. The devices can be managed as a generic SNMP device.
- C. The devices can be polled for connection status.
- D. The devices will have connection logs.
Answer: A,D
Explanation:
In FortiNAC-F, the Device Profiler is a rule-based engine that evaluates unknown "rogue" devices and classifies them based on fingerprints and behavior. When a profiling rule matches a device, the administrator can configure the rule to automatically register that device. The registration process can place the device record in two primary locations: the Topology View (as a device) or the Host View (as a registered host).
According to the FortiNAC-F Administration Guide, registering a device in the Host View provides significant advantages for identity management and historical tracking. First, the devices can be associated with a user (C). In the FortiNAC database architecture, the Host View is the primary repository for endpoint identity; placing a profiled device here allows the system to link that hardware (MAC address) to a specific user account, whether that user is an employee, guest, or a system-level "owner". This association is essential for Role-Based Access Control (RBAC) and for tracking accountability across the network fabric.
Second, devices registered in the Host View will have connection logs (B). FortiNAC-F maintains a detailed operational history for all host records, including every instance of the device connecting to or disconnecting from a port, its IP address assignments, and the specific policies applied during each session. These logs are invaluable for troubleshooting connectivity issues and for security forensic audits, as they provide a clear timeline of the device's lifecycle on the network. In contrast, devices managed only in the Topology View are typically treated as infrastructure components where the focus is on device availability rather than individual session history.
"Devices that are registered and associated with a user are placed in the Host View and removed from the Profiled Devices window... Placing a device in the Host View allows for the tracking of connection history and the association of the device with a specific identity or user record within the FortiNAC database."
NEW QUESTION # 21
An administrator wants to build a security rule that will quarantine contractors who attempt to access specific websites.
In addition to a user host profile, which two components must the administrator configure to create the security rule? (Choose two.)
- A. Action
- B. Methods
- C. Endpoint compliance policy
- D. Security String
- E. Trigger
Answer: A,E
Explanation:
A security rule requires a trigger to detect the condition, such as contractors accessing specific websites based on security or traffic events. It also requires an action to define the response, such as quarantining the contractor when the trigger condition is met.
NEW QUESTION # 22
An administrator wants FortiNAC-F to pass firewall tags to FortiGate to leverage dynamic address groups used in firewall policies.
On FortiNAC-F, what determines the values that are passed?
- A. Device profiling rule
- B. Security rule
- C. RADIUS group attribute
- D. Model configuration
Answer: B
Explanation:
The values of firewall tags sent from FortiNAC-F to FortiGate are defined within the security rule.
The security rule determines the action applied to a host or user, including which tags are assigned and passed to FortiGate for use in dynamic address groups and associated firewall policies.
NEW QUESTION # 23
Refer to the exhibit.
After a successful layer 2 poll, two hosts were learned on the same port. The port is a member of the Role-Based Access and Forced Registration groups. The switch has been configured to leverage a single isolation VLAN.
How will FortiNAC-F manage this port?
- A. The port will be added to the Access Point Management group.
- B. The port will be provisioned as an uplink to a hub or unmanaged switch.
- C. The port will be provisioned for the normal state host, but the second host will have access to only the isolation portal page.
- D. The port will be provisioned to the isolation network.
Answer: D
Explanation:
Because two hosts were learned on the same switch port, FortiNAC-F must enforce access at the port level rather than per-host. With a single isolation VLAN configured, the port is placed into the isolation network to ensure the port's learned devices are restricted and can be forced through the registration/isolation workflow.
NEW QUESTION # 24
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?
- A. The Admin Auditing view
- B. The Security Events view
- C. The Event Management view
- D. The Port Changes view
Answer: A
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 port 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.
NEW QUESTION # 25
Which two requirements must be met to set up an N+1 HA cluster? (Choose two.)
- A. A FortiNAC-F manager
- B. At least two FortiNAC-F devices designated as primary
- C. A dedicated VLAN for primary and secondary synchronization
- D. A FortiNAC-F device designated as a secondary
Answer: A,D
Explanation:
The N+1 High Availability (HA) architecture was introduced in FortiNAC-F version 7.6 to provide a more scalable and flexible redundancy model compared to the traditional 1+1 active/passive setup.
In an N+1 configuration, a single secondary (standby) appliance can provide coverage for multiple primary (active) Control and Application (CA) appliances.
To set up an N+1 HA cluster, there are two fundamental structural requirements:
A FortiNAC-F Manager (FortiNAC-M): Unlike standard 1+1 HA, which can be configured directly between two CAs, N+1 management is centralized. The FortiNAC-M acts as the orchestrator that manages the failover groups, monitors the health of the primaries, and coordinates the promotion of the secondary server if a primary fails.
A FortiNAC-F device designated as a Secondary: The cluster must have one appliance explicitly configured with the Secondary failover role. This device remains in a standby state, receiving database replications from all N primaries in its group until it is called upon to take over the functions of a failed unit
NEW QUESTION # 26
Refer to the exhibits.
Given the current configuration, what would happen if a contractor triggered two of the defined security filters?
- A. Three security events and one security alarm would be generated.
- B. A security alarm and two security events would be generated.
- C. A security event and a security alarm would be generated.
- D. Two security events would be generated, but no security alarm would be generated.
Answer: A
Explanation:
Each matched security filter generates its own security event. Since the trigger is configured to match any one filter within the defined time limit, multiple matched filters will generate multiple events, but only one security alarm is created when the security rule condition is satisfied.
NEW QUESTION # 27
While discovering network infrastructure devices, a switch appears in the inventory topology with a question mark (?) on the icon. What would cause this?
- A. The SNMP ObjectlD is not recognized by FortiNAC-F.
- B. SNMP is not enabled on the switch.
- C. The wrong SNMP community string was entered during discovery.
- D. A read-only SNMP community siring was used.
Answer: A
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."
NEW QUESTION # 28
An administrator wants to build device profiling rules based on network traffic, but the network session view is not populated with any records.
Which two settings can be enabled to gather network session information? (Choose two.)
- A. Netflow setting on the FortiNAC-F interfaces
- B. Layer 3 polling on the infrastructure devices
- C. Network traffic polling on any modeled infrastructure device
- D. Firewall session polling on modeled FortiGate devices
Answer: A,D
Explanation:
In FortiNAC-F, the Network Sessions view provides a real-time and historical log of traffic flows, including source/destination IP addresses, ports, and protocols. This data is essential for building Device Profiling Rules that rely on "Traffic Patterns" or "Network Footprints" to identify devices (e.g., an IP camera communicating with its specific NVR). If the network session view is empty, the system is not receiving the necessary flow or session data from the network infrastructure.
According to the FortiNAC-F Administration Guide, there are two primary methods to populate this view:
NetFlow/sFlow/IPFIX (C): FortiNAC-F can act as a flow collector. By enabling NetFlow settings on the FortiNAC-F service interface (port2/eth1) and configuring your switches or routers to export flow data to the FortiNAC IP, the system can parse these packets and record sessions.
Firewall Session Polling (B): For environments with FortiGate firewalls, FortiNAC-F can proactively poll the FortiGate via the REST API to retrieve its current session table. This is particularly useful as it provides session visibility without requiring the overhead of configuring NetFlow on every access layer switch.
NEW QUESTION # 29
As part of a company policy, all end stations must be scanned for compliance each day. The security administrators want to satisfy this requirement without any necessary interaction from the end user. Which two agents can provide that functionality? (Choose two.)
- A. Passive
- B. Persistent
- C. Mobile
- D. Dissolvable
Answer: A,B
Explanation:
The persistent agent remains installed on the endpoint and can perform scheduled compliance scans automatically without user interaction. The passive agent collects endpoint information without requiring installation or user action, enabling ongoing compliance evaluation transparently.
NEW QUESTION # 30
When configuring isolation networks in the configuration wizard, why does a layer 3 network type allow for more than one DHCP scope for each isolation network type?
- A. There can be more than one isolation network of each type
- B. Any scopes beyond the first scope are used if the initial scope runs out of IP addresses.
- C. Configuring more than one DHCP scope allows for DHCP server redundancy
- D. The layer 3 network type allows for one scope for each possible host status.
Answer: A
Explanation:
With a layer 3 isolation network type, FortiNAC-F supports multiple isolation networks of the same type, each with its own routed subnet. This design allows administrators to define more than one DHCP scope per isolation network type to accommodate multiple layer 3 isolation segments.
NEW QUESTION # 31
An administrator is configuring FortiNAC-F to manage FortiGate VPN users. As part of the configuration, the administrator must configure a few FortiGate firewall policies.
What is the purpose of the FortiGate firewall policy that applies to clients not yet authorized by FortiNAC-F?
- A. To allow access to only the FortiNAC-F VPN interface
- B. To allow access to only the FortiGate VPN interface
- C. To allow access to only the production DNS server
- D. To allow access to only the production DNS server
Answer: A
Explanation:
The firewall policy for clients not yet authorized by FortiNAC-F is designed to restrict their access so they can communicate only with the FortiNAC-F VPN interface. This allows FortiNAC-F to perform authentication and authorization before granting broader network access.
NEW QUESTION # 32
An administrator wants to control user access to corporate resources by integrating FortiNAC-F with FortiGate using firewall tags defined on FortiNAC-F.
Where would the administrator assign the firewall tag value that will be sent to FortiGate?
- A. Device profiling rule
- B. RADIUS group attribute
- C. Logical network
- D. Security rule
Answer: C
Explanation:
In FortiNAC-F, the integration with FortiGate for Security Fabric and Single Sign-On (FSSO) allows the system to communicate the access level of an endpoint directly to the firewall using firewall tags. This eliminates the need for complex VLAN steering in some environments by allowing the FortiGate to apply policies based on these dynamic tags instead of just a physical or virtual network segment.
The actual assignment of the firewall tag value occurs within a Logical Network. In the FortiNAC- F architectural model, a Logical Network acts as a container for "Access Values". When an administrator configures a Logical Network (located under Network > Logical Networks), they define what that network represents--such as "Corporate Access" or "Contractor Limited". Within that definition, they assign the specific Firewall Tag that matches the tag created on the FortiGate. Once a user or host matches a Network Access Policy, FortiNAC-F identifies the associated Logical Network and pushes the defined tag to the FortiGate via the FSSO connector.
It is important to note that while Network Access Policies (and by extension Security Rules) are the logic engines that trigger the assignment, they do not hold the tag value itself. They simply point to a Logical Network, which serves as the central repository for that specific access configuration.
"To assign firewall tags, navigate to Network > Logical Networks. Select the desired logical network and click Edit. Under the Access Value section, select Firewall Tag as the type and enter the tag name exactly as it appears on the FortiGate. When a Network Access Policy matches a host, FortiNAC sends this tag to the FortiGate as an FSSO message."
NEW QUESTION # 33
Two FortiNAC-F devices have been configured as a 1+1 HA pair. The primary server went offline and a successful failover to the secondary has occurred.
What happens if the primary server comes back online?
- A. The secondary server will update the primary and the servers will load balance until an administrator forces the primary to resume full control.
- B. The primary and secondary servers will resume communication and the secondary will maintain control.
- C. The primary server will determine that the secondary has control and power down for maintenance.
- D. After five successful heartbeats between the servers, the primary server will resume control.
Answer: B
Explanation:
In a 1+1 HA configuration, once failover has occurred and the secondary assumes control, it remains the active controller when the original primary comes back online. The restored primary rejoins as the standby unit, and control is not automatically reverted.
NEW QUESTION # 34
......
Get Prepared for Your NSE5_FNC_AD-7.6 Exam With Actual 71 Questions: https://www.exam4free.com/NSE5_FNC_AD-7.6-valid-dumps.html
Authentic NSE5_FNC_AD-7.6 Exam Dumps PDF - 2026 Updated: https://drive.google.com/open?id=1by8kRDWIk_DHDQh9zDCvA-0cR0CLSV0R
