Fortinet NSE5_FSW_AD-7.6 Practice Test 28
Question 270
A FortiGate cluster has HA heartbeats but only the failed member owns a working FortiLink path. Which diagnostic evidence should the FortiSwitch administrator examine FIRST?
- Inspect primary/secondary FortiGate roles, HA health, FortiLink uplinks, downstream switch topology and session continuity.
- Check ingress port, assigned VLAN ID, owner VDOM, gateway, firewall session path and cross-tenant deny counters.
- Check switch PoE budget, port class, negotiated allocation, PSU state, LLDP-MED power TLV and port events.
- Check VDOM assignment, sharing support, allowed VLANs, policy scope, QoS or port-security support and MAC-learning state.
Explanation
Correct Answer
A:Inspect primary/secondary FortiGate roles, HA health, FortiLink uplinks, downstream switch topology and session continuity. FortiGate HA design and FortiSwitch stacking/MCLAG are separate mechanisms; their failure paths must both be evaluated. The paired action is: Plan FortiLink management under FortiGate HA with supported links, peer roles and deterministic failover tests.
Incorrect Answers
B:Check ingress port, assigned VLAN ID, owner VDOM, gateway, firewall session path and cross-tenant deny counters. These observations are applicable to Managed tenant troubleshooting across controller and access layer, but would not isolate the main failure first. The decisive evidence is: Inspect primary/secondary FortiGate roles, HA health, FortiLink uplinks, downstream switch topology and session continuity.
C:Check switch PoE budget, port class, negotiated allocation, PSU state, LLDP-MED power TLV and port events. These observations are applicable to PoE and LLDP-MED endpoint power coordination, but would not isolate the main failure first. The decisive evidence is: Inspect primary/secondary FortiGate roles, HA health, FortiLink uplinks, downstream switch topology and session continuity.
D:Check VDOM assignment, sharing support, allowed VLANs, policy scope, QoS or port-security support and MAC-learning state. These observations are applicable to Shared port multi-VDOM policy boundaries, but would not isolate the main failure first. The decisive evidence is: Inspect primary/secondary FortiGate roles, HA health, FortiLink uplinks, downstream switch topology and session continuity.
Question 271
A switch has IGMP snooping enabled but no effective querier and group entries age out unexpectedly. Which diagnostic evidence should the FortiSwitch administrator examine FIRST?
- Inspect FortiGate FortiLink status, supported discovery port, LLDP frames, interface IP, link errors and switch serial.
- Check group membership table, querier identity, IGMP report traffic, VLAN and target egress port.
- Inspect source MAC entries by VLAN, ingress/egress port, address aging, LAG membership and broadcast counters.
- Inspect FortiLink operational mode, controller ownership, current management address, VDOM and switch model support.
Explanation
Correct Answer
B:Check group membership table, querier identity, IGMP report traffic, VLAN and target egress port. A multicast VLAN alone does not indicate that IGMP receiver membership or querier operation is healthy. The paired action is: Configure supported IGMP snooping and querier expectations to forward multicast only where receivers request it.
Incorrect Answers
A:Inspect FortiGate FortiLink status, supported discovery port, LLDP frames, interface IP, link errors and switch serial. These observations are applicable to FortiLink discovery failure and physical uplink path, but would not isolate the main failure first. The decisive evidence is: Check group membership table, querier identity, IGMP report traffic, VLAN and target egress port.
C:Inspect source MAC entries by VLAN, ingress/egress port, address aging, LAG membership and broadcast counters. These observations are applicable to Layer 2 MAC-learning and forwarding decisions, but would not isolate the main failure first. The decisive evidence is: Check group membership table, querier identity, IGMP report traffic, VLAN and target egress port.
D:Inspect FortiLink operational mode, controller ownership, current management address, VDOM and switch model support. These observations are applicable to FortiSwitch standalone versus FortiLink managed L3 ownership, but would not isolate the main failure first. The decisive evidence is: Check group membership table, querier identity, IGMP report traffic, VLAN and target egress port.
Question 272
An automated branch rollout fails because its bootstrap port sits on a VLAN that cannot contact the controller. Which observable result BEST proves the intended FortiSwitch operation or security policy works?
- The switch successfully onboards to the intended FortiGate and retains a recoverable controller-managed baseline.
- All subtending managed switches remain discoverable and user service survives expected single-link failures where supported.
- Two tenants can use the supported shared port without accidental cross-tenant broadcasts or privilege escalation.
- Controller and switch return to supported synchronized software and configuration with test-client services restored.
Explanation
Correct Answer
A:The switch successfully onboards to the intended FortiGate and retains a recoverable controller-managed baseline. Zero-touch deployment works only when the necessary discovery path and identity checks function; a link LED is insufficient.
Incorrect Answers
B:All subtending managed switches remain discoverable and user service survives expected single-link failures where supported. This result relates to FortiSwitch multi-tier managed topology, not the acceptance condition under test. The relevant result is: The switch successfully onboards to the intended FortiGate and retains a recoverable controller-managed baseline.
C:Two tenants can use the supported shared port without accidental cross-tenant broadcasts or privilege escalation. This result relates to Shared port multi-VDOM policy boundaries, not the acceptance condition under test. The relevant result is: The switch successfully onboards to the intended FortiGate and retains a recoverable controller-managed baseline.
D:Controller and switch return to supported synchronized software and configuration with test-client services restored. This result relates to FortiLink synchronization and upgrade troubleshooting, not the acceptance condition under test. The relevant result is: The switch successfully onboards to the intended FortiGate and retains a recoverable controller-managed baseline.
Question 273
A private customer VLAN unexpectedly appears in another tenant's MAC table after a trunk change. Which diagnostic evidence should the FortiSwitch administrator examine FIRST?
- Inspect actor partner system IDs, LACP mode, partner synchronization, port speed, VLAN membership and member counters.
- Compare desired switch controller settings, switch synchronization indicators, port VLANs, user roles and post-reboot configuration.
- Inspect MCLAG peer group, peer-link status, LACP members, VLAN consistency and split-brain safeguards.
- Check ingress port, assigned VLAN ID, owner VDOM, gateway, firewall session path and cross-tenant deny counters.
Explanation
Correct Answer
D:Check ingress port, assigned VLAN ID, owner VDOM, gateway, firewall session path and cross-tenant deny counters. A packet may be correctly switched but rejected by VDOM routing or firewall policy, or incorrectly admitted to another tenant at Layer 2. The paired action is: Diagnose multi-VDOM client isolation issues by correlating switch VLAN assignment and FortiGate VDOM routing/policy evidence.
Incorrect Answers
A:Inspect actor partner system IDs, LACP mode, partner synchronization, port speed, VLAN membership and member counters. These observations are applicable to LACP negotiation on FortiSwitch FortiLink trunks, but would not isolate the main failure first. The decisive evidence is: Check ingress port, assigned VLAN ID, owner VDOM, gateway, firewall session path and cross-tenant deny counters.
B:Compare desired switch controller settings, switch synchronization indicators, port VLANs, user roles and post-reboot configuration. These observations are applicable to Managed switch configuration synchronization, but would not isolate the main failure first. The decisive evidence is: Check ingress port, assigned VLAN ID, owner VDOM, gateway, firewall session path and cross-tenant deny counters.
C:Inspect MCLAG peer group, peer-link status, LACP members, VLAN consistency and split-brain safeguards. These observations are applicable to MCLAG multichassis access redundancy, but would not isolate the main failure first. The decisive evidence is: Check ingress port, assigned VLAN ID, owner VDOM, gateway, firewall session path and cross-tenant deny counters.
Question 274
A firmware image is upgraded successfully but the switch does not reconnect to the FortiGate management controller. Which FortiSwitch configuration or corrective action BEST addresses the requirement?
- Mirror only the relevant source ports or VLAN traffic to a dedicated analyzer destination using supported SPAN settings.
- Apply supported egress CoS queue policy to reduce latency under congestion without starving other required traffic.
- Identify FortiLink failures caused by split-interface, HA, MCLAG peer or ISL mismatches before changing unrelated ports.
- Investigate managed switch offline or configuration mismatch after firmware upgrade or controller resynchronization using both endpoints.
Explanation
Correct Answer
D:Investigate managed switch offline or configuration mismatch after firmware upgrade or controller resynchronization using both endpoints. Managed switches can be reachable at Layer 2 yet show stale policy after incompatible upgrade or failed controller push. Verify the action with: Review FortiGate/FortiSwitch version matrix, upgrade logs, auto-authorize state, synchronization events, switch restart and rollback image.
Incorrect Answers
A:Mirror only the relevant source ports or VLAN traffic to a dedicated analyzer destination using supported SPAN settings. This action is relevant to FortiSwitch port mirroring to network analyzer, not the controlling requirement in this case. A mirrored stream is passive evidence and can be incomplete if analyzer bandwidth is lower than the observed traffic. The targeted response is: Investigate managed switch offline or configuration mismatch after firmware upgrade or controller resynchronization using both endpoints.
B:Apply supported egress CoS queue policy to reduce latency under congestion without starving other required traffic. This action is relevant to Egress priority scheduling and congestion visibility, not the controlling requirement in this case. QoS prioritizes scarce link capacity but cannot create bandwidth beyond the physical egress rate. The targeted response is: Investigate managed switch offline or configuration mismatch after firmware upgrade or controller resynchronization using both endpoints.
C:Identify FortiLink failures caused by split-interface, HA, MCLAG peer or ISL mismatches before changing unrelated ports. This action is relevant to FortiLink HA and MCLAG topology faults, not the controlling requirement in this case. FortiGate HA, FortiLink split-interface and FortiSwitch MCLAG have distinct failover behaviors that cannot be inferred from link LEDs alone. The targeted response is: Investigate managed switch offline or configuration mismatch after firmware upgrade or controller resynchronization using both endpoints.
Question 275
An engineer enables authorization during business hours without recognizing that the switch may reboot into FortiLink mode. Which observable result BEST proves the intended FortiSwitch operation or security policy works?
- The offending misassignment is corrected with both permitted traffic and forbidden cross-tenant traffic tested.
- Exactly the intended serial joins managed inventory and receives approved controller settings after authorization.
- Known printers and IoT devices enter their restricted VLANs while unknown endpoints have no excessive access.
- The new FortiSwitch discovers the designated controller while unrelated FortiGate interfaces retain their normal function.
Explanation
Correct Answer
B:Exactly the intended serial joins managed inventory and receives approved controller settings after authorization. Switch discovery is not the same as authorization; auto-authorization has governance implications and a managed-mode transition may reboot the device.
Incorrect Answers
A:The offending misassignment is corrected with both permitted traffic and forbidden cross-tenant traffic tested. This result relates to Managed tenant troubleshooting across controller and access layer, not the acceptance condition under test. The relevant result is: Exactly the intended serial joins managed inventory and receives approved controller settings after authorization.
C:Known printers and IoT devices enter their restricted VLANs while unknown endpoints have no excessive access. This result relates to NAC dynamic port policy device classification, not the acceptance condition under test. The relevant result is: Exactly the intended serial joins managed inventory and receives approved controller settings after authorization.
D:The new FortiSwitch discovers the designated controller while unrelated FortiGate interfaces retain their normal function. This result relates to FortiLink management interface provisioning, not the acceptance condition under test. The relevant result is: Exactly the intended serial joins managed inventory and receives approved controller settings after authorization.
Question 276
A technician plugs a managed FortiSwitch into an arbitrary WAN port and waits for it to register automatically. Which observable result BEST proves the intended FortiSwitch operation or security policy works?
- Authorized monitoring receives timely, interpretable switch evidence without exposing community strings or overwhelming CPU.
- Each customer's tagged traffic reaches only its assigned service context without S-VLAN collision.
- A controlled FortiGate HA failover leaves managed switches authorized and required client access functioning.
- The new FortiSwitch discovers the designated controller while unrelated FortiGate interfaces retain their normal function.
Explanation
Correct Answer
D:The new FortiSwitch discovers the designated controller while unrelated FortiGate interfaces retain their normal function. A FortiGate port not configured for FortiLink cannot assume managed-switch ownership from physical connection alone.
Incorrect Answers
A:Authorized monitoring receives timely, interpretable switch evidence without exposing community strings or overwhelming CPU. This result relates to SNMP and sFlow monitoring configuration, not the acceptance condition under test. The relevant result is: The new FortiSwitch discovers the designated controller while unrelated FortiGate interfaces retain their normal function.
B:Each customer's tagged traffic reaches only its assigned service context without S-VLAN collision. This result relates to QinQ outer and inner VLAN tenant mapping, not the acceptance condition under test. The relevant result is: The new FortiSwitch discovers the designated controller while unrelated FortiGate interfaces retain their normal function.
C:A controlled FortiGate HA failover leaves managed switches authorized and required client access functioning. This result relates to HA FortiGate pair managing switch topology, not the acceptance condition under test. The relevant result is: The new FortiSwitch discovers the designated controller while unrelated FortiGate interfaces retain their normal function.
Question 277
One upstream switch loses power and all child switches disappear from the FortiGate management screen. Which FortiSwitch configuration or corrective action BEST addresses the requirement?
- Create an appropriate FortiGate FortiLink physical or logical interface with supported addressing and controller capabilities before onboarding a switch.
- Choose supported FortiSwitchOS version and maintenance workflow compatible with the FortiGate version and topology.
- Set measured storm-control thresholds for broadcast, multicast or unknown unicast as supported and validate needed discovery protocols.
- Build a documented supported FortiSwitch daisy chain or multi-tier topology with adequate ISL uplink capacity and safeguards.
Explanation
Correct Answer
D:Build a documented supported FortiSwitch daisy chain or multi-tier topology with adequate ISL uplink capacity and safeguards. A FortiGate controls each FortiSwitch through the managed Layer-2 topology, but downstream reachability depends on upstream FortiLink links. Verify the action with: Check managed tree, ISL link health, model compatibility, VLAN carriage, depth limitations and upstream aggregate status.
Incorrect Answers
A:Create an appropriate FortiGate FortiLink physical or logical interface with supported addressing and controller capabilities before onboarding a switch. This action is relevant to FortiLink management interface provisioning, not the controlling requirement in this case. A FortiGate port not configured for FortiLink cannot assume managed-switch ownership from physical connection alone. The targeted response is: Build a documented supported FortiSwitch daisy chain or multi-tier topology with adequate ISL uplink capacity and safeguards.
B:Choose supported FortiSwitchOS version and maintenance workflow compatible with the FortiGate version and topology. This action is relevant to Firmware and lifecycle preparation for FortiSwitch, not the controlling requirement in this case. A successful image upload does not prove switch operation or controller compatibility after reboot. The targeted response is: Build a documented supported FortiSwitch daisy chain or multi-tier topology with adequate ISL uplink capacity and safeguards.
C:Set measured storm-control thresholds for broadcast, multicast or unknown unicast as supported and validate needed discovery protocols. This action is relevant to Storm-control thresholds and broadcast containment, not the controlling requirement in this case. Overaggressive storm control can break DHCP, ARP or group discovery even when physical links remain healthy. The targeted response is: Build a documented supported FortiSwitch daisy chain or multi-tier topology with adequate ISL uplink capacity and safeguards.
Question 278
A voice ACL blocks the signaling network because a new permit rule was placed after a broader deny. Which FortiSwitch configuration or corrective action BEST addresses the requirement?
- Use supported MAC-based access controls with narrow authorized device roles and avoid treating MAC addresses as strong identity proof.
- Apply supported switch ACL entries to targeted port or VLAN traffic with documented match, action, and policy sequence.
- Use documented trusted DHCP-server lists or Option 82 information where supported to enforce authorized address assignment.
- Create an appropriate FortiGate FortiLink physical or logical interface with supported addressing and controller capabilities before onboarding a switch.
Explanation
Correct Answer
B:Apply supported switch ACL entries to targeted port or VLAN traffic with documented match, action, and policy sequence. Switch ACLs and FortiGate firewall policies operate at different enforcement points; a deny on one does not prove the other applied. Verify the action with: Review ACL direction and attachment, permit/drop rules, hit counters, supported match fields and resulting packet path.
Incorrect Answers
A:Use supported MAC-based access controls with narrow authorized device roles and avoid treating MAC addresses as strong identity proof. This action is relevant to MAC-based authentication and restricted legacy devices, not the controlling requirement in this case. A MAC address can be cloned; MAC authentication must be combined with appropriate segmentation and monitoring. The targeted response is: Apply supported switch ACL entries to targeted port or VLAN traffic with documented match, action, and policy sequence.
C:Use documented trusted DHCP-server lists or Option 82 information where supported to enforce authorized address assignment. This action is relevant to DHCP server allowlist and Option 82 validation, not the controlling requirement in this case. DHCP server allowlist and Option 82 metadata provide additional context but cannot correct a failed VLAN or missing upstream relay. The targeted response is: Apply supported switch ACL entries to targeted port or VLAN traffic with documented match, action, and policy sequence.
D:Create an appropriate FortiGate FortiLink physical or logical interface with supported addressing and controller capabilities before onboarding a switch. This action is relevant to FortiLink management interface provisioning, not the controlling requirement in this case. A FortiGate port not configured for FortiLink cannot assume managed-switch ownership from physical connection alone. The targeted response is: Apply supported switch ACL entries to targeted port or VLAN traffic with documented match, action, and policy sequence.
Question 279
An added FortiSwitch uplink remains individual because its peer LACP mode is incompatible. Which FortiSwitch configuration or corrective action BEST addresses the requirement?
- Repair LACP member settings and physical port errors independently before increasing aggregate traffic.
- Set only mutually supported Ethernet port rates and verify operational negotiation instead of forcing mismatched speeds.
- Validate the supported PoE budget and LLDP-MED endpoint power negotiation rather than equating link up with adequate wattage.
- Apply changes on the FortiGate controller and verify installed FortiSwitch state and reconciliation before rebooting.
Explanation
Correct Answer
A:Repair LACP member settings and physical port errors independently before increasing aggregate traffic. One healthy physical link is not proof an aggregate has balanced traffic or that the peer LACP policy matches. Verify the action with: Check per-member speed, partner identity, state, optical counters, VLAN tags and aggregate distribution.
Incorrect Answers
B:Set only mutually supported Ethernet port rates and verify operational negotiation instead of forcing mismatched speeds. This action is relevant to Switch port speed and duplex commissioning, not the controlling requirement in this case. Incorrect forced port speed or duplex can mimic application loss even when the VLAN configuration is valid. The targeted response is: Repair LACP member settings and physical port errors independently before increasing aggregate traffic.
C:Validate the supported PoE budget and LLDP-MED endpoint power negotiation rather than equating link up with adequate wattage. This action is relevant to PoE and LLDP-MED endpoint power coordination, not the controlling requirement in this case. Port count and Ethernet link state do not guarantee sufficient power for high-draw endpoints. The targeted response is: Repair LACP member settings and physical port errors independently before increasing aggregate traffic.
D:Apply changes on the FortiGate controller and verify installed FortiSwitch state and reconciliation before rebooting. This action is relevant to Managed switch configuration synchronization, not the controlling requirement in this case. Local changes on a FortiLink-managed switch can be discarded when the FortiGate controller reapplies its known configuration. The targeted response is: Repair LACP member settings and physical port errors independently before increasing aggregate traffic.
Question 280
A phone and computer share one access port but the policy authenticates only the first observed MAC address. Which observable result BEST proves the intended FortiSwitch operation or security policy works?
- Authorized endpoints enter only permitted VLANs while failed authentication is denied or restricted according to policy.
- All subtending managed switches remain discoverable and user service survives expected single-link failures where supported.
- Legitimate clients lease addresses while rogue DHCP servers connected to untrusted access ports cannot answer.
- Approved legacy devices gain only restricted services while unknown or spoofed MAC addresses remain constrained.
Explanation
Correct Answer
D:Approved legacy devices gain only restricted services while unknown or spoofed MAC addresses remain constrained. A MAC address can be cloned; MAC authentication must be combined with appropriate segmentation and monitoring.
Incorrect Answers
A:Authorized endpoints enter only permitted VLANs while failed authentication is denied or restricted according to policy. This result relates to FortiSwitch 802.1X port-based authentication, not the acceptance condition under test. The relevant result is: Approved legacy devices gain only restricted services while unknown or spoofed MAC addresses remain constrained.
B:All subtending managed switches remain discoverable and user service survives expected single-link failures where supported. This result relates to FortiSwitch multi-tier managed topology, not the acceptance condition under test. The relevant result is: Approved legacy devices gain only restricted services while unknown or spoofed MAC addresses remain constrained.
C:Legitimate clients lease addresses while rogue DHCP servers connected to untrusted access ports cannot answer. This result relates to DHCP snooping trust-boundary enforcement, not the acceptance condition under test. The relevant result is: Approved legacy devices gain only restricted services while unknown or spoofed MAC addresses remain constrained.