Fortinet NSE5_FSW_AD-7.6 Practice Test 80
Question 790
Two aggregation switches have two uplinks to an access device but lack a configured FortiSwitch MCLAG pair. Which diagnostic evidence should the FortiSwitch administrator examine FIRST?
- Inspect supported topology, FortiLink p2p settings, TPID, transport reachability, discovery frames and switch firmware.
- Inspect MCLAG peer group, peer-link status, LACP members, VLAN consistency and split-brain safeguards.
- Review queue maps, output drops, interface rate, strict versus weighted servicing and application latency.
- Inspect controller VDOM ownership, VLAN interface parent, port mapping, session policy and IP/routing separation.
Explanation
Correct Answer
B:Inspect MCLAG peer group, peer-link status, LACP members, VLAN consistency and split-brain safeguards. MCLAG requires peer coordination and correct downstream aggregation; it is not equivalent to connecting independent switches in parallel. The paired action is: Use documented peer-group and downstream trunk configuration for MCLAG rather than creating ad hoc parallel Ethernet links.
Incorrect Answers
A:Inspect supported topology, FortiLink p2p settings, TPID, transport reachability, discovery frames and switch firmware. These observations are applicable to FortiLink transport over nontrivial L2 or L3 paths, but would not isolate the main failure first. The decisive evidence is: Inspect MCLAG peer group, peer-link status, LACP members, VLAN consistency and split-brain safeguards.
C:Review queue maps, output drops, interface rate, strict versus weighted servicing and application latency. These observations are applicable to Egress priority scheduling and congestion visibility, but would not isolate the main failure first. The decisive evidence is: Inspect MCLAG peer group, peer-link status, LACP members, VLAN consistency and split-brain safeguards.
D:Inspect controller VDOM ownership, VLAN interface parent, port mapping, session policy and IP/routing separation. These observations are applicable to FortiGate VDOM-based FortiSwitch tenant assignment, but would not isolate the main failure first. The decisive evidence is: Inspect MCLAG peer group, peer-link status, LACP members, VLAN consistency and split-brain safeguards.
Question 791
A managed switch belongs to a common FortiLink while new customer VLANs are assigned to an unrelated FortiGate VDOM. Which observable result BEST proves the intended FortiSwitch operation or security policy works?
- The expected known switch becomes authorized and synchronizes without accepting an unrelated device.
- A tenant reaches only its approved VDOM resources and does not inherit another tenant's policies.
- The intended tenant configuration changes while other tenants retain their segmentation and service.
- Management control and authorized user traffic work over the direct connection without confusing them.
Explanation
Correct Answer
B:A tenant reaches only its approved VDOM resources and does not inherit another tenant's policies. A VDOM creates a separate policy and routing context; it does not by itself make a shared physical switch port safe for all tenants.
Incorrect Answers
A:The expected known switch becomes authorized and synchronizes without accepting an unrelated device. This result relates to Controller authorization and pending-switch state, not the acceptance condition under test. The relevant result is: A tenant reaches only its approved VDOM resources and does not inherit another tenant's policies.
C:The intended tenant configuration changes while other tenants retain their segmentation and service. This result relates to Multi-tenant change verification and rollback, not the acceptance condition under test. The relevant result is: A tenant reaches only its approved VDOM resources and does not inherit another tenant's policies.
D:Management control and authorized user traffic work over the direct connection without confusing them. This result relates to Single FortiGate and single FortiSwitch topology, not the acceptance condition under test. The relevant result is: A tenant reaches only its approved VDOM resources and does not inherit another tenant's policies.
Question 792
An IP phone connects at 100M after a port configuration was mistakenly forced to that rate. Which diagnostic evidence should the FortiSwitch administrator examine FIRST?
- Check managed topology view, controller switch state, ISL port counters, peer LLDP and suspected link events.
- Check both peer capabilities, auto-negotiation, administrative speed, cable quality and CRC/FCS counters.
- Inspect controller VDOM ownership, VLAN interface parent, port mapping, session policy and IP/routing separation.
- Inspect hardware SKU, firmware and phy-mode support, breakout cable specification, child port IDs and port restart effect.
Explanation
Correct Answer
B:Check both peer capabilities, auto-negotiation, administrative speed, cable quality and CRC/FCS counters. Incorrect forced port speed or duplex can mimic application loss even when the VLAN configuration is valid. The paired action is: Set only mutually supported Ethernet port rates and verify operational negotiation instead of forcing mismatched speeds.
Incorrect Answers
A:Check managed topology view, controller switch state, ISL port counters, peer LLDP and suspected link events. These observations are applicable to Stack failure isolation and switch-to-switch port roles, but would not isolate the main failure first. The decisive evidence is: Check both peer capabilities, auto-negotiation, administrative speed, cable quality and CRC/FCS counters.
C:Inspect controller VDOM ownership, VLAN interface parent, port mapping, session policy and IP/routing separation. These observations are applicable to FortiGate VDOM-based FortiSwitch tenant assignment, but would not isolate the main failure first. The decisive evidence is: Check both peer capabilities, auto-negotiation, administrative speed, cable quality and CRC/FCS counters.
D:Inspect hardware SKU, firmware and phy-mode support, breakout cable specification, child port IDs and port restart effect. These observations are applicable to FortiSwitch split port breakout mode, but would not isolate the main failure first. The decisive evidence is: Check both peer capabilities, auto-negotiation, administrative speed, cable quality and CRC/FCS counters.
Question 793
A new routed VLAN exists but its SVI stays down because no participating port is operational. Which observable result BEST proves the intended FortiSwitch operation or security policy works?
- Phones and access points receive stable allocated power while redundant PSU and priority policies remain within budget.
- Both ends connect at compatible rates with stable errors and required throughput.
- Hosts can reach their intended SVI and authorized routed destinations without overlapping address space.
- Exactly the intended serial joins managed inventory and receives approved controller settings after authorization.
Explanation
Correct Answer
C:Hosts can reach their intended SVI and authorized routed destinations without overlapping address space. Layer-3 SVI configuration and actual usable forwarding are separate from having a named Layer-2 VLAN.
Incorrect Answers
A:Phones and access points receive stable allocated power while redundant PSU and priority policies remain within budget. This result relates to PoE and LLDP-MED endpoint power coordination, not the acceptance condition under test. The relevant result is: Hosts can reach their intended SVI and authorized routed destinations without overlapping address space.
B:Both ends connect at compatible rates with stable errors and required throughput. This result relates to Switch port speed and duplex commissioning, not the acceptance condition under test. The relevant result is: Hosts can reach their intended SVI and authorized routed destinations without overlapping address space.
D:Exactly the intended serial joins managed inventory and receives approved controller settings after authorization. This result relates to Discovered versus authorized FortiSwitch state, not the acceptance condition under test. The relevant result is: Hosts can reach their intended SVI and authorized routed destinations without overlapping address space.
Question 794
A technician changes a phone port to a trunk but fails to restrict unrelated management VLANs. Which observable result BEST proves the intended FortiSwitch operation or security policy works?
- The handset and attached workstation use the intended separate networks and retain their authorized access.
- The user VLAN reaches the authorized gateway without being placed on an unrelated physical FortiGate interface.
- A trace shows the expected ingress/egress control packets without collecting unrelated sensitive network traffic.
- The impacted client can communicate on the permitted VLAN while unrelated tenant or guest VLANs remain separated.
Explanation
Correct Answer
A:The handset and attached workstation use the intended separate networks and retain their authorized access. Voice tagging is not secured merely because its VLAN ID differs from the workstation's native VLAN.
Incorrect Answers
B:The user VLAN reaches the authorized gateway without being placed on an unrelated physical FortiGate interface. This result relates to FortiGate managed FortiSwitch VLAN interface placement, not the acceptance condition under test. The relevant result is: The handset and attached workstation use the intended separate networks and retain their authorized access.
C:A trace shows the expected ingress/egress control packets without collecting unrelated sensitive network traffic. This result relates to FortiSwitch local packet-capture profile and filters, not the acceptance condition under test. The relevant result is: The handset and attached workstation use the intended separate networks and retain their authorized access.
D:The impacted client can communicate on the permitted VLAN while unrelated tenant or guest VLANs remain separated. This result relates to VLAN access isolation and troubleshooting of membership, not the acceptance condition under test. The relevant result is: The handset and attached workstation use the intended separate networks and retain their authorized access.
Question 795
A client manually assigns a privileged subnet address and tries to send packets through an access port. Which diagnostic evidence should the FortiSwitch administrator examine FIRST?
- Examine port binding list, packet source IP, ingress VLAN, IP-source guard counters and expected host subnet.
- Check interface type, FortiLink enablement, discovery setting, IP assignment, switch model support, and management VLAN reachability.
- Inspect port profile assignment, FortiGate controller policy, client role, enforcement counters and overlapping static controls.
- Inspect ARP inspection status, DHCP snooping binding database, source MAC/IP, trusted ports and violation logs.
Explanation
Correct Answer
A:Examine port binding list, packet source IP, ingress VLAN, IP-source guard counters and expected host subnet. Source guard is an ingress source-binding check, not a full replacement for routed firewall policies or endpoint security. The paired action is: Enable IPv4 source guard on supported switch interfaces only with appropriate DHCP snooping or static bindings.
Incorrect Answers
B:Check interface type, FortiLink enablement, discovery setting, IP assignment, switch model support, and management VLAN reachability. These observations are applicable to FortiLink management interface provisioning, but would not isolate the main failure first. The decisive evidence is: Examine port binding list, packet source IP, ingress VLAN, IP-source guard counters and expected host subnet.
C:Inspect port profile assignment, FortiGate controller policy, client role, enforcement counters and overlapping static controls. These observations are applicable to FortiSwitch security profile application and precedence, but would not isolate the main failure first. The decisive evidence is: Examine port binding list, packet source IP, ingress VLAN, IP-source guard counters and expected host subnet.
D:Inspect ARP inspection status, DHCP snooping binding database, source MAC/IP, trusted ports and violation logs. These observations are applicable to Dynamic ARP inspection with DHCP snooping bindings, but would not isolate the main failure first. The decisive evidence is: Examine port binding list, packet source IP, ingress VLAN, IP-source guard counters and expected host subnet.
Question 796
One FortiSwitch reboot causes adjacent units to move between discovered and authorized states. Which diagnostic evidence should the FortiSwitch administrator examine FIRST?
- Check managed topology view, controller switch state, ISL port counters, peer LLDP and suspected link events.
- Inspect FortiLink interface type, split-interface setting, connected peer count, STP state and active management path.
- Compare controller desired VLAN map, current switch running state, configuration synchronization and post-reboot behavior.
- Inspect Discover/Offer/Request/Ack sequence, ARP requests/replies, VLAN tags, DHCP snooping and DAI counters.
Explanation
Correct Answer
A:Check managed topology view, controller switch state, ISL port counters, peer LLDP and suspected link events. A missing switch in a FortiLink managed chain may be caused by the upstream ISL even if its access ports still carry local traffic. The paired action is: Correlate stack and ISL status to identify the failed path instead of reconfiguring all access VLANs.
Incorrect Answers
B:Inspect FortiLink interface type, split-interface setting, connected peer count, STP state and active management path. These observations are applicable to FortiLink split-interface and standby path design, but would not isolate the main failure first. The decisive evidence is: Check managed topology view, controller switch state, ISL port counters, peer LLDP and suspected link events.
C:Compare controller desired VLAN map, current switch running state, configuration synchronization and post-reboot behavior. These observations are applicable to VLAN configuration persistence and drift control, but would not isolate the main failure first. The decisive evidence is: Check managed topology view, controller switch state, ISL port counters, peer LLDP and suspected link events.
D:Inspect Discover/Offer/Request/Ack sequence, ARP requests/replies, VLAN tags, DHCP snooping and DAI counters. These observations are applicable to Capture-based DHCP and ARP path isolation, but would not isolate the main failure first. The decisive evidence is: Check managed topology view, controller switch state, ISL port counters, peer LLDP and suspected link events.
Question 797
A technician disables STP on one interswitch uplink because it shows blocking during normal redundancy. Which FortiSwitch configuration or corrective action BEST addresses the requirement?
- Enable supported BPDU guard only on true edge/client ports, and restore blocked ports after identifying unauthorized switching.
- Repair LACP member settings and physical port errors independently before increasing aggregate traffic.
- Troubleshoot FortiLink discovery from physical and logical interface configuration through LLDP and management addressing.
- Use compatible spanning-tree mode across connected switches and verify per-VLAN root and blocked links.
Explanation
Correct Answer
D:Use compatible spanning-tree mode across connected switches and verify per-VLAN root and blocked links. An STP mode change can change per-VLAN convergence behavior even if existing links remain physically up. Verify the action with: Inspect local mode, per-VLAN bridge ID, peer BPDUs, port state, timers and topology-change history.
Incorrect Answers
A:Enable supported BPDU guard only on true edge/client ports, and restore blocked ports after identifying unauthorized switching. This action is relevant to BPDU guard on endpoint-facing ports, not the controlling requirement in this case. BPDU guard can disable an intended trunk if incorrectly treated as an end-station port. The targeted response is: Use compatible spanning-tree mode across connected switches and verify per-VLAN root and blocked links.
B:Repair LACP member settings and physical port errors independently before increasing aggregate traffic. This action is relevant to Link aggregation and port error recovery, not the controlling requirement in this case. One healthy physical link is not proof an aggregate has balanced traffic or that the peer LACP policy matches. The targeted response is: Use compatible spanning-tree mode across connected switches and verify per-VLAN root and blocked links.
C:Troubleshoot FortiLink discovery from physical and logical interface configuration through LLDP and management addressing. This action is relevant to FortiLink discovery failure and physical uplink path, not the controlling requirement in this case. A green Ethernet link is necessary for many paths but does not prove the FortiLink management protocol or discovery is working. The targeted response is: Use compatible spanning-tree mode across connected switches and verify per-VLAN root and blocked links.
Question 798
A team claims an ACL encrypts traffic instead of recognizing its supported forwarding/filtering actions. Which FortiSwitch configuration or corrective action BEST addresses the requirement?
- Apply a specific restricted VLAN or quarantine mechanism with explicit authorized remediation and monitoring expectations.
- Apply supported switch ACL entries to targeted port or VLAN traffic with documented match, action, and policy sequence.
- Use supported dynamic ARP inspection with valid switch bindings to reject spoofed IP-MAC claims at untrusted edges.
- Assign the intended untagged native VLAN and explicitly permit tagged VLANs on an uplink; compare both ends before cutover.
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:Apply a specific restricted VLAN or quarantine mechanism with explicit authorized remediation and monitoring expectations. This action is relevant to VLAN security policy and quarantine actions, not the controlling requirement in this case. Quarantine must be enforced at the right switch and VLAN path; a security-alert label alone does not remove access. The targeted response is: Apply supported switch ACL entries to targeted port or VLAN traffic with documented match, action, and policy sequence.
C:Use supported dynamic ARP inspection with valid switch bindings to reject spoofed IP-MAC claims at untrusted edges. This action is relevant to Dynamic ARP inspection with DHCP snooping bindings, not the controlling requirement in this case. DAI validation needs a reliable binding or exception policy; enabling it blindly can interrupt static-IP devices. The targeted response is: Apply supported switch ACL entries to targeted port or VLAN traffic with documented match, action, and policy sequence.
D:Assign the intended untagged native VLAN and explicitly permit tagged VLANs on an uplink; compare both ends before cutover. This action is relevant to FortiSwitch native VLAN versus allowed VLANs, not the controlling requirement in this case. Native VLAN handling and tagged VLAN membership are different controls; a working physical link does not validate VLAN carriage. The targeted response is: Apply supported switch ACL entries to targeted port or VLAN traffic with documented match, action, and policy sequence.
Question 799
A port inventory lists a downstream switch whose LLDP entry has expired and no longer reflects current wiring. Which observable result BEST proves the intended FortiSwitch operation or security policy works?
- The current neighboring device and optional endpoint location are visible and match approved cabling documentation.
- The failing physical or logical port is identified through reproducible counters rather than visual LED assumptions.
- Phones and access points receive stable allocated power while redundant PSU and priority policies remain within budget.
- A rogue root candidate is blocked or a looped path remains safely contained without wiping all STP configuration.
Explanation
Correct Answer
A:The current neighboring device and optional endpoint location are visible and match approved cabling documentation. LLDP is an L2 discovery protocol and cannot prove the whole routed service path or phone emergency-location correctness by itself.
Incorrect Answers
B:The failing physical or logical port is identified through reproducible counters rather than visual LED assumptions. This result relates to Managed switch port statistics and counter analysis, not the acceptance condition under test. The relevant result is: The current neighboring device and optional endpoint location are visible and match approved cabling documentation.
C:Phones and access points receive stable allocated power while redundant PSU and priority policies remain within budget. This result relates to PoE and LLDP-MED endpoint power coordination, not the acceptance condition under test. The relevant result is: The current neighboring device and optional endpoint location are visible and match approved cabling documentation.
D:A rogue root candidate is blocked or a looped path remains safely contained without wiping all STP configuration. This result relates to Root guard and loop guard failure response, not the acceptance condition under test. The relevant result is: The current neighboring device and optional endpoint location are visible and match approved cabling documentation.
Question 800
An administrator enables DHCP snooping without checking whether the expected relay path is exempted correctly. Which diagnostic evidence should the FortiSwitch administrator examine FIRST?
- Inspect trusted-port state, Discover/Offer path, DHCP binding table, VLAN and counters for dropped offers.
- Review target VLAN, switch isolation controls, client MAC table, permitted gateway path and peer-to-peer test.
- Inspect FortiLink management state, native/tagged VLANs, port membership, FortiGate interface and active firewall policy.
- Check learned client MAC, RADIUS MAC authentication response, access policy, fallback sequence and effective VLAN.
Explanation
Correct Answer
A:Inspect trusted-port state, Discover/Offer path, DHCP binding table, VLAN and counters for dropped offers. Trusting every port defeats DHCP snooping and wrongly distrusting the server uplink may suppress all leases. The paired action is: Enable supported DHCP snooping on client VLANs and trust only known DHCP-server or relay-facing links.
Incorrect Answers
B:Review target VLAN, switch isolation controls, client MAC table, permitted gateway path and peer-to-peer test. These observations are applicable to Intra-VLAN blocking and isolation boundaries, but would not isolate the main failure first. The decisive evidence is: Inspect trusted-port state, Discover/Offer path, DHCP binding table, VLAN and counters for dropped offers.
C:Inspect FortiLink management state, native/tagged VLANs, port membership, FortiGate interface and active firewall policy. These observations are applicable to FortiLink control and client VLAN transport separation, but would not isolate the main failure first. The decisive evidence is: Inspect trusted-port state, Discover/Offer path, DHCP binding table, VLAN and counters for dropped offers.
D:Check learned client MAC, RADIUS MAC authentication response, access policy, fallback sequence and effective VLAN. These observations are applicable to MAC-based authentication and restricted legacy devices, but would not isolate the main failure first. The decisive evidence is: Inspect trusted-port state, Discover/Offer path, DHCP binding table, VLAN and counters for dropped offers.