Fortinet NSE5_FSW_AD-7.6 Practice Test 27
Question 260
A server sends untagged frames but its switch port expects only tagged frames and never learns the MAC in the intended VLAN. Which diagnostic evidence should the FortiSwitch administrator examine FIRST?
- Inspect source MAC entries by VLAN, ingress/egress port, address aging, LAG membership and broadcast counters.
- Check captured port, protocol/MAC/IP filter, platform buffer capacity, capture timestamps and exported packet headers.
- Check group membership table, querier identity, IGMP report traffic, VLAN and target egress port.
- Inspect SVI admin state, VLAN membership, address and mask, connected route, ARP and intended upstream gateway.
Explanation
Correct Answer
A:Inspect source MAC entries by VLAN, ingress/egress port, address aging, LAG membership and broadcast counters. An L2 switch uses MAC destination and VLAN state for forwarding; a healthy SVI is not proof a host is on the proper port. The paired action is: Check MAC-learning table and flooding behavior before replacing a switch or changing its IP routing.
Incorrect Answers
B:Check captured port, protocol/MAC/IP filter, platform buffer capacity, capture timestamps and exported packet headers. These observations are applicable to FortiSwitch local packet-capture profile and filters, but would not isolate the main failure first. The decisive evidence is: Inspect source MAC entries by VLAN, ingress/egress port, address aging, LAG membership and broadcast counters.
C:Check group membership table, querier identity, IGMP report traffic, VLAN and target egress port. These observations are applicable to IGMP snooping and multicast receivers, but would not isolate the main failure first. The decisive evidence is: Inspect source MAC entries by VLAN, ingress/egress port, address aging, LAG membership and broadcast counters.
D:Inspect SVI admin state, VLAN membership, address and mask, connected route, ARP and intended upstream gateway. These observations are applicable to FortiSwitch SVI routing and connected routes, but would not isolate the main failure first. The decisive evidence is: Inspect source MAC entries by VLAN, ingress/egress port, address aging, LAG membership and broadcast counters.
Question 261
An IP phone connects at 100M after a port configuration was mistakenly forced to that rate. Which FortiSwitch configuration or corrective action BEST addresses the requirement?
- Prepare supported provisioning, DHCP, management connectivity and secure bootstrap before assuming a factory-default FortiSwitch will auto-configure.
- Change managed switch VLAN membership through the FortiGate controller and verify the installed configuration stays consistent.
- Set only mutually supported Ethernet port rates and verify operational negotiation instead of forcing mismatched speeds.
- Choose supported Fortinet transceivers and link media based on switch capability, optical reach and wavelength.
Explanation
Correct Answer
C:Set only mutually supported Ethernet port rates and verify operational negotiation instead of forcing mismatched speeds. Incorrect forced port speed or duplex can mimic application loss even when the VLAN configuration is valid. Verify the action with: Check both peer capabilities, auto-negotiation, administrative speed, cable quality and CRC/FCS counters.
Incorrect Answers
A:Prepare supported provisioning, DHCP, management connectivity and secure bootstrap before assuming a factory-default FortiSwitch will auto-configure. This action is relevant to Zero-touch provisioning and controller dependency checks, not the controlling requirement in this case. Zero-touch deployment works only when the necessary discovery path and identity checks function; a link LED is insufficient. The targeted response is: Set only mutually supported Ethernet port rates and verify operational negotiation instead of forcing mismatched speeds.
B:Change managed switch VLAN membership through the FortiGate controller and verify the installed configuration stays consistent. This action is relevant to VLAN configuration persistence and drift control, not the controlling requirement in this case. Directly editing a FortiLink-managed switch can cause drift because FortiGate remains the controller of record. The targeted response is: Set only mutually supported Ethernet port rates and verify operational negotiation instead of forcing mismatched speeds.
D:Choose supported Fortinet transceivers and link media based on switch capability, optical reach and wavelength. This action is relevant to Optic compatibility and laser diagnostic evidence, not the controlling requirement in this case. Matching a mechanical optic cage is insufficient to prove optical or firmware compatibility. The targeted response is: Set only mutually supported Ethernet port rates and verify operational negotiation instead of forcing mismatched speeds.
Question 262
A private customer VLAN unexpectedly appears in another tenant's MAC table after a trunk change. Which FortiSwitch configuration or corrective action BEST addresses the requirement?
- Prepare supported provisioning, DHCP, management connectivity and secure bootstrap before assuming a factory-default FortiSwitch will auto-configure.
- Configure supported switch virtual interfaces and routed gateway addresses with correct VLAN, subnet and management context.
- Diagnose multi-VDOM client isolation issues by correlating switch VLAN assignment and FortiGate VDOM routing/policy evidence.
- Create an appropriate FortiGate FortiLink physical or logical interface with supported addressing and controller capabilities before onboarding a switch.
Explanation
Correct Answer
C:Diagnose multi-VDOM client isolation issues by correlating switch VLAN assignment and FortiGate VDOM routing/policy evidence. A packet may be correctly switched but rejected by VDOM routing or firewall policy, or incorrectly admitted to another tenant at Layer 2. Verify the action with: Check ingress port, assigned VLAN ID, owner VDOM, gateway, firewall session path and cross-tenant deny counters.
Incorrect Answers
A:Prepare supported provisioning, DHCP, management connectivity and secure bootstrap before assuming a factory-default FortiSwitch will auto-configure. This action is relevant to Zero-touch provisioning and controller dependency checks, not the controlling requirement in this case. Zero-touch deployment works only when the necessary discovery path and identity checks function; a link LED is insufficient. The targeted response is: Diagnose multi-VDOM client isolation issues by correlating switch VLAN assignment and FortiGate VDOM routing/policy evidence.
B:Configure supported switch virtual interfaces and routed gateway addresses with correct VLAN, subnet and management context. This action is relevant to FortiSwitch SVI routing and connected routes, not the controlling requirement in this case. Layer-3 SVI configuration and actual usable forwarding are separate from having a named Layer-2 VLAN. The targeted response is: Diagnose multi-VDOM client isolation issues by correlating switch VLAN assignment and FortiGate VDOM routing/policy evidence.
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: Diagnose multi-VDOM client isolation issues by correlating switch VLAN assignment and FortiGate VDOM routing/policy evidence.
Question 263
A phone and computer share one access port but the policy authenticates only the first observed MAC address. Which diagnostic evidence should the FortiSwitch administrator examine FIRST?
- Inspect device fingerprint, policy rule order, assigned VLAN, security profile, client identity and enforcement state.
- Inspect port profile assignment, FortiGate controller policy, client role, enforcement counters and overlapping static controls.
- Inspect mirror direction, source and destination ports, speed constraints, physical capture link and switch statistics.
- Check learned client MAC, RADIUS MAC authentication response, access policy, fallback sequence and effective VLAN.
Explanation
Correct Answer
D:Check learned client MAC, RADIUS MAC authentication response, access policy, fallback sequence and effective VLAN. A MAC address can be cloned; MAC authentication must be combined with appropriate segmentation and monitoring. The paired action is: Use supported MAC-based access controls with narrow authorized device roles and avoid treating MAC addresses as strong identity proof.
Incorrect Answers
A:Inspect device fingerprint, policy rule order, assigned VLAN, security profile, client identity and enforcement state. These observations are applicable to NAC dynamic port policy device classification, but would not isolate the main failure first. The decisive evidence is: Check learned client MAC, RADIUS MAC authentication response, access policy, fallback sequence and effective VLAN.
B: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: Check learned client MAC, RADIUS MAC authentication response, access policy, fallback sequence and effective VLAN.
C:Inspect mirror direction, source and destination ports, speed constraints, physical capture link and switch statistics. These observations are applicable to FortiSwitch port mirroring to network analyzer, but would not isolate the main failure first. The decisive evidence is: Check learned client MAC, RADIUS MAC authentication response, access policy, fallback sequence and effective VLAN.
Question 264
A user plugs a small unmanaged switch into a protected desk outlet and the access port shuts down. Which TWO complementary steps identify the appropriate FortiSwitch response AND the evidence needed to verify it? Select TWO.
- Two tenants can use the supported shared port without accidental cross-tenant broadcasts or privilege escalation.
- Select a consistent supported MSTP region and intentional root-bridge placement for loop-free L2 redundancy.
- Examine BPDU ingress counters, configured edge flag, port-down reason, connected device and recovery policy.
- Check uplink neighbors, discovered-switch serials, FortiLink eligible ports, ISL cables, topology and controller authorization.
- Enable supported BPDU guard only on true edge/client ports, and restore blocked ports after identifying unauthorized switching.
Explanation
Correct Answers
C:Examine BPDU ingress counters, configured edge flag, port-down reason, connected device and recovery policy. BPDU guard can disable an intended trunk if incorrectly treated as an end-station port. The paired action is: Enable supported BPDU guard only on true edge/client ports, and restore blocked ports after identifying unauthorized switching. This is the diagnostic or verification half of the requested TWO-step pair.
E:Enable supported BPDU guard only on true edge/client ports, and restore blocked ports after identifying unauthorized switching. BPDU guard can disable an intended trunk if incorrectly treated as an end-station port. Verify the action with: Examine BPDU ingress counters, configured edge flag, port-down reason, connected device and recovery policy. This is the configuration or remediation half of the requested TWO-step pair.
Incorrect Answers
A:Two tenants can use the supported shared port without accidental cross-tenant broadcasts or privilege escalation. This step concerns Shared port multi-VDOM policy boundaries and is not part of the required paired solution. The correct action and evidence are: Enable supported BPDU guard only on true edge/client ports, and restore blocked ports after identifying unauthorized switching. Together with: Examine BPDU ingress counters, configured edge flag, port-down reason, connected device and recovery policy.
B:Select a consistent supported MSTP region and intentional root-bridge placement for loop-free L2 redundancy. This step concerns MSTP region consistency and designated root and is not part of the required paired solution. The correct action and evidence are: Enable supported BPDU guard only on true edge/client ports, and restore blocked ports after identifying unauthorized switching. Together with: Examine BPDU ingress counters, configured edge flag, port-down reason, connected device and recovery policy.
D:Check uplink neighbors, discovered-switch serials, FortiLink eligible ports, ISL cables, topology and controller authorization. This step concerns FortiLink ISL auto-discovery and stack cabling and is not part of the required paired solution. The correct action and evidence are: Enable supported BPDU guard only on true edge/client ports, and restore blocked ports after identifying unauthorized switching. Together with: Examine BPDU ingress counters, configured edge flag, port-down reason, connected device and recovery policy.
Question 265
A branch's FortiLink interface has no route or reachable controller IP and the managed switch never appears. Which FortiSwitch configuration or corrective action BEST addresses the requirement?
- Apply changes on the FortiGate controller and verify installed FortiSwitch state and reconciliation before rebooting.
- Use a supported direct FortiLink connection and confirm controller traffic and client forwarding on the intended interfaces.
- Create an appropriate FortiGate FortiLink physical or logical interface with supported addressing and controller capabilities before onboarding a switch.
- Connect FortiSwitch uplinks through supported FortiLink discovery or approved inter-switch link topology, verifying model port roles.
Explanation
Correct Answer
C:Create an appropriate FortiGate FortiLink physical or logical interface with supported addressing and controller capabilities before onboarding a switch. A FortiGate port not configured for FortiLink cannot assume managed-switch ownership from physical connection alone. Verify the action with: Check interface type, FortiLink enablement, discovery setting, IP assignment, switch model support, and management VLAN reachability.
Incorrect Answers
A: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: Create an appropriate FortiGate FortiLink physical or logical interface with supported addressing and controller capabilities before onboarding a switch.
B:Use a supported direct FortiLink connection and confirm controller traffic and client forwarding on the intended interfaces. This action is relevant to Single FortiGate and single FortiSwitch topology, not the controlling requirement in this case. FortiLink carries management and data traffic; a valid management handshake does not prove every user VLAN is forwarded. The targeted response is: Create an appropriate FortiGate FortiLink physical or logical interface with supported addressing and controller capabilities before onboarding a switch.
D:Connect FortiSwitch uplinks through supported FortiLink discovery or approved inter-switch link topology, verifying model port roles. This action is relevant to FortiLink ISL auto-discovery and stack cabling, not the controlling requirement in this case. The FortiGate-managed FortiSwitch stack is a managed L2 topology, not automatically a single chassis or universal VSF-like control plane. The targeted response is: Create an appropriate FortiGate FortiLink physical or logical interface with supported addressing and controller capabilities before onboarding a switch.
Question 266
An engineer blames firmware for a restart without inspecting system-event history or power loss indications. Which observable result BEST proves the intended FortiSwitch operation or security policy works?
- All subtending managed switches remain discoverable and user service survives expected single-link failures where supported.
- A failed managed switch can be replaced with supported firmware and restored authorized port/VLAN behavior.
- A moved device is traced to its current approved port and incorrect cross-connection is identified.
- The suspected failure has a traceable event sequence and a specific evidence-based remediation candidate.
Explanation
Correct Answer
D:The suspected failure has a traceable event sequence and a specific evidence-based remediation candidate. A log message without source device, time and relevant state is not adequate to prove root cause.
Incorrect Answers
A: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 suspected failure has a traceable event sequence and a specific evidence-based remediation candidate.
B:A failed managed switch can be replaced with supported firmware and restored authorized port/VLAN behavior. This result relates to Config backup and firmware inventory evidence, not the acceptance condition under test. The relevant result is: The suspected failure has a traceable event sequence and a specific evidence-based remediation candidate.
C:A moved device is traced to its current approved port and incorrect cross-connection is identified. This result relates to LLDP and MAC forwarding table extraction, not the acceptance condition under test. The relevant result is: The suspected failure has a traceable event sequence and a specific evidence-based remediation candidate.
Question 267
A client cannot reach DHCP and an analyst captures a trunk that does not carry that client VLAN. Which FortiSwitch configuration or corrective action BEST addresses the requirement?
- Correlate LLDP neighbor inventory and VLAN-specific MAC entries to reconstruct actual endpoint and uplink paths.
- Use FortiGate FortiSwitch Ports statistics or supported switch commands to isolate errors, utilization and port status at the right location.
- Configure supported FortiSwitch MCLAG peer groups and peer links before connecting downstream redundant bundles.
- Create a bounded packet-capture profile on the right switch interface with a narrow filter, then start/stop and inspect frames.
Explanation
Correct Answer
D:Create a bounded packet-capture profile on the right switch interface with a narrow filter, then start/stop and inspect frames. Packet captures are interface and filter scoped, and platform buffer limits differ; a capture file is not proof of all traffic on every switch port. Verify the action with: Check captured port, protocol/MAC/IP filter, platform buffer capacity, capture timestamps and exported packet headers.
Incorrect Answers
A:Correlate LLDP neighbor inventory and VLAN-specific MAC entries to reconstruct actual endpoint and uplink paths. This action is relevant to LLDP and MAC forwarding table extraction, not the controlling requirement in this case. LLDP provides adjacent-device identity, while MAC learning maps forwarding; neither is a full routed trace by itself. The targeted response is: Create a bounded packet-capture profile on the right switch interface with a narrow filter, then start/stop and inspect frames.
B:Use FortiGate FortiSwitch Ports statistics or supported switch commands to isolate errors, utilization and port status at the right location. This action is relevant to Managed switch port statistics and counter analysis, not the controlling requirement in this case. A port-up indicator or one successful ping is not proof that a congested or errored uplink is healthy. The targeted response is: Create a bounded packet-capture profile on the right switch interface with a narrow filter, then start/stop and inspect frames.
C:Configure supported FortiSwitch MCLAG peer groups and peer links before connecting downstream redundant bundles. This action is relevant to MCLAG peer-link topology for managed access switches, not the controlling requirement in this case. MCLAG redundancy depends on supported peer-link and aggregate design; two cables alone do not constitute working multichassis aggregation. The targeted response is: Create a bounded packet-capture profile on the right switch interface with a narrow filter, then start/stop and inspect frames.
Question 268
An engineer enables point-to-point FortiLink on one side of a bridge but not on the peer. Which diagnostic evidence should the FortiSwitch administrator examine FIRST?
- Inspect supported topology, FortiLink p2p settings, TPID, transport reachability, discovery frames and switch firmware.
- Review discovered/authorized controller inventory, switch serial, link state, approval method, reboot status and firmware compatibility.
- Inspect the port native VLAN, allowed VLAN list, peer tags, learned MACs and relevant FortiGate VLAN interface.
- Check interface type, FortiLink enablement, discovery setting, IP assignment, switch model support, and management VLAN reachability.
Explanation
Correct Answer
A:Inspect supported topology, FortiLink p2p settings, TPID, transport reachability, discovery frames and switch firmware. FortiLink over intermediate networks requires topology-specific settings; ordinary IP reachability alone does not establish FortiLink discovery. The paired action is: Use supported FortiLink point-to-point L2 or Layer-3 transport configuration and validate discovery and control traffic end to end.
Incorrect Answers
B:Review discovered/authorized controller inventory, switch serial, link state, approval method, reboot status and firmware compatibility. These observations are applicable to Discovered versus authorized FortiSwitch state, but would not isolate the main failure first. The decisive evidence is: Inspect supported topology, FortiLink p2p settings, TPID, transport reachability, discovery frames and switch firmware.
C:Inspect the port native VLAN, allowed VLAN list, peer tags, learned MACs and relevant FortiGate VLAN interface. These observations are applicable to FortiSwitch native VLAN versus allowed VLANs, but would not isolate the main failure first. The decisive evidence is: Inspect supported topology, FortiLink p2p settings, TPID, transport reachability, discovery frames and switch firmware.
D: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: Inspect supported topology, FortiLink p2p settings, TPID, transport reachability, discovery frames and switch firmware.
Question 269
A user plugs a small unmanaged switch into a protected desk outlet and the access port shuts down. 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.
- An access host receives the right subnet while only approved tagged VLANs traverse the uplink.
- Accidental downstream switches are contained without disabling legitimate uplinks that should exchange BPDUs.
- Spoofed ARP replies are dropped while legitimate endpoints maintain gateway ARP resolution.
Explanation
Correct Answer
C:Accidental downstream switches are contained without disabling legitimate uplinks that should exchange BPDUs. BPDU guard can disable an intended trunk if incorrectly treated as an end-station port.
Incorrect Answers
A:The handset and attached workstation use the intended separate networks and retain their authorized access. This result relates to Voice and data VLAN separation on shared access ports, not the acceptance condition under test. The relevant result is: Accidental downstream switches are contained without disabling legitimate uplinks that should exchange BPDUs.
B:An access host receives the right subnet while only approved tagged VLANs traverse the uplink. This result relates to FortiSwitch native VLAN versus allowed VLANs, not the acceptance condition under test. The relevant result is: Accidental downstream switches are contained without disabling legitimate uplinks that should exchange BPDUs.
D:Spoofed ARP replies are dropped while legitimate endpoints maintain gateway ARP resolution. This result relates to Dynamic ARP inspection with DHCP snooping bindings, not the acceptance condition under test. The relevant result is: Accidental downstream switches are contained without disabling legitimate uplinks that should exchange BPDUs.
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.