Fortinet NSE5_FSW_AD-7.6 Practice Test 71
Question 700
A firmware image is upgraded successfully but the switch does not reconnect to the FortiGate management controller. Which diagnostic evidence should the FortiSwitch administrator examine FIRST?
- Inspect supported topology, FortiLink p2p settings, TPID, transport reachability, discovery frames and switch firmware.
- Review FortiGate/FortiSwitch version matrix, upgrade logs, auto-authorize state, synchronization events, switch restart and rollback image.
- Inspect mirror direction, source and destination ports, speed constraints, physical capture link and switch statistics.
- Review frame error type, CRC/FCS, traffic rates, drops, operational speed, port description and sampled timestamps.
Explanation
Correct Answer
B:Review FortiGate/FortiSwitch version matrix, upgrade logs, auto-authorize state, synchronization events, switch restart and rollback image. Managed switches can be reachable at Layer 2 yet show stale policy after incompatible upgrade or failed controller push. The paired action is: Investigate managed switch offline or configuration mismatch after firmware upgrade or controller resynchronization using both endpoints.
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: Review FortiGate/FortiSwitch version matrix, upgrade logs, auto-authorize state, synchronization events, switch restart and rollback image.
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: Review FortiGate/FortiSwitch version matrix, upgrade logs, auto-authorize state, synchronization events, switch restart and rollback image.
D:Review frame error type, CRC/FCS, traffic rates, drops, operational speed, port description and sampled timestamps. These observations are applicable to Managed switch port statistics and counter analysis, but would not isolate the main failure first. The decisive evidence is: Review FortiGate/FortiSwitch version matrix, upgrade logs, auto-authorize state, synchronization events, switch restart and rollback image.
Question 701
A redundant aggregation port changes from discarding to forwarding before the expected blocked port transitions safely. Which diagnostic evidence should the FortiSwitch administrator examine FIRST?
- Inspect guard role, BPDU reception, root-ID history, STP port role and loop-condition log.
- Review target VLAN, switch isolation controls, client MAC table, permitted gateway path and peer-to-peer test.
- Review spanning-tree topology-change count, MAC instability, BPDU logs, port errors and recent cabling changes.
- Examine BPDU ingress counters, configured edge flag, port-down reason, connected device and recovery policy.
Explanation
Correct Answer
C:Review spanning-tree topology-change count, MAC instability, BPDU logs, port errors and recent cabling changes. Packet loss during a bridging loop can coexist with clean optical counters, so L1-only diagnostics miss the root cause. The paired action is: Use STP state and MAC move evidence to isolate one bad bridging path and change only the proven element.
Incorrect Answers
A:Inspect guard role, BPDU reception, root-ID history, STP port role and loop-condition log. These observations are applicable to Root guard and loop guard failure response, but would not isolate the main failure first. The decisive evidence is: Review spanning-tree topology-change count, MAC instability, BPDU logs, port errors and recent cabling changes.
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: Review spanning-tree topology-change count, MAC instability, BPDU logs, port errors and recent cabling changes.
D:Examine BPDU ingress counters, configured edge flag, port-down reason, connected device and recovery policy. These observations are applicable to BPDU guard on endpoint-facing ports, but would not isolate the main failure first. The decisive evidence is: Review spanning-tree topology-change count, MAC instability, BPDU logs, port errors and recent cabling changes.
Question 702
The configured FortiLink aggregate connects to a single switch but its split-interface setting does not match the topology. Which TWO complementary steps identify the appropriate FortiSwitch response AND the evidence needed to verify it? Select TWO.
- Permit shared FortiSwitch hardware across VDOMs only with verified port and feature support and explicit tenant VLAN tagging.
- Check interface type, FortiLink enablement, discovery setting, IP assignment, switch model support, and management VLAN reachability.
- Check ingress port, assigned VLAN ID, owner VDOM, gateway, firewall session path and cross-tenant deny counters.
- Controller and switch return to supported synchronized software and configuration with test-client services restored.
- Create an appropriate FortiGate FortiLink physical or logical interface with supported addressing and controller capabilities before onboarding a switch.
Explanation
Correct Answers
B:Check interface type, FortiLink enablement, discovery setting, IP assignment, switch model support, and management VLAN reachability. A FortiGate port not configured for FortiLink cannot assume managed-switch ownership from physical connection alone. The paired action is: Create an appropriate FortiGate FortiLink physical or logical interface with supported addressing and controller capabilities before onboarding a switch. This is the diagnostic or verification half of the requested TWO-step pair.
E: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. This is the configuration or remediation half of the requested TWO-step pair.
Incorrect Answers
A:Permit shared FortiSwitch hardware across VDOMs only with verified port and feature support and explicit tenant VLAN tagging. This step concerns Shared port multi-VDOM policy boundaries and is not part of the required paired solution. The correct action and evidence are: Create an appropriate FortiGate FortiLink physical or logical interface with supported addressing and controller capabilities before onboarding a switch. Together with: Check interface type, FortiLink enablement, discovery setting, IP assignment, switch model support, and management VLAN reachability.
C:Check ingress port, assigned VLAN ID, owner VDOM, gateway, firewall session path and cross-tenant deny counters. This step concerns Managed tenant troubleshooting across controller and access layer and is not part of the required paired solution. The correct action and evidence are: Create an appropriate FortiGate FortiLink physical or logical interface with supported addressing and controller capabilities before onboarding a switch. Together with: Check interface type, FortiLink enablement, discovery setting, IP assignment, switch model support, and management VLAN reachability.
D:Controller and switch return to supported synchronized software and configuration with test-client services restored. This step concerns FortiLink synchronization and upgrade troubleshooting and is not part of the required paired solution. The correct action and evidence are: Create an appropriate FortiGate FortiLink physical or logical interface with supported addressing and controller capabilities before onboarding a switch. Together with: Check interface type, FortiLink enablement, discovery setting, IP assignment, switch model support, and management VLAN reachability.
Question 703
A trunk expects double-tagged frames but the upstream switch strips the outer service tag. Which TWO complementary steps identify the appropriate FortiSwitch response AND the evidence needed to verify it? Select TWO.
- Inspect customer VLAN tags, service VLAN outer tag, FortiLink parent VDOM, mapping and interface capability.
- Use supported FortiLink point-to-point L2 or Layer-3 transport configuration and validate discovery and control traffic end to end.
- The suspected failure has a traceable event sequence and a specific evidence-based remediation candidate.
- Plan S-VLAN and C-VLAN mapping with the correct FortiLink VDOM and platform support for tenant-tagged traffic.
- Check managed tree, ISL link health, model compatibility, VLAN carriage, depth limitations and upstream aggregate status.
Explanation
Correct Answers
A:Inspect customer VLAN tags, service VLAN outer tag, FortiLink parent VDOM, mapping and interface capability. QinQ layering and VDOM assignment are separate controls; wrong outer tagging can mix customers even when inner VLAN IDs differ. The paired action is: Plan S-VLAN and C-VLAN mapping with the correct FortiLink VDOM and platform support for tenant-tagged traffic. This is the diagnostic or verification half of the requested TWO-step pair.
D:Plan S-VLAN and C-VLAN mapping with the correct FortiLink VDOM and platform support for tenant-tagged traffic. QinQ layering and VDOM assignment are separate controls; wrong outer tagging can mix customers even when inner VLAN IDs differ. Verify the action with: Inspect customer VLAN tags, service VLAN outer tag, FortiLink parent VDOM, mapping and interface capability. This is the configuration or remediation half of the requested TWO-step pair.
Incorrect Answers
B:Use supported FortiLink point-to-point L2 or Layer-3 transport configuration and validate discovery and control traffic end to end. This step concerns FortiLink transport over nontrivial L2 or L3 paths and is not part of the required paired solution. The correct action and evidence are: Plan S-VLAN and C-VLAN mapping with the correct FortiLink VDOM and platform support for tenant-tagged traffic. Together with: Inspect customer VLAN tags, service VLAN outer tag, FortiLink parent VDOM, mapping and interface capability.
C:The suspected failure has a traceable event sequence and a specific evidence-based remediation candidate. This step concerns FortiSwitch diagnostic commands and logs and is not part of the required paired solution. The correct action and evidence are: Plan S-VLAN and C-VLAN mapping with the correct FortiLink VDOM and platform support for tenant-tagged traffic. Together with: Inspect customer VLAN tags, service VLAN outer tag, FortiLink parent VDOM, mapping and interface capability.
E:Check managed tree, ISL link health, model compatibility, VLAN carriage, depth limitations and upstream aggregate status. This step concerns FortiSwitch multi-tier managed topology and is not part of the required paired solution. The correct action and evidence are: Plan S-VLAN and C-VLAN mapping with the correct FortiLink VDOM and platform support for tenant-tagged traffic. Together with: Inspect customer VLAN tags, service VLAN outer tag, FortiLink parent VDOM, mapping and interface capability.
Question 704
A private customer VLAN unexpectedly appears in another tenant's MAC table after a trunk change. Which observable result BEST proves the intended FortiSwitch operation or security policy works?
- Hosts can reach their intended SVI and authorized routed destinations without overlapping address space.
- The new FortiSwitch discovers the designated controller while unrelated FortiGate interfaces retain their normal function.
- 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.
Explanation
Correct Answer
C:The offending misassignment is corrected with both permitted traffic and forbidden cross-tenant traffic tested. A packet may be correctly switched but rejected by VDOM routing or firewall policy, or incorrectly admitted to another tenant at Layer 2.
Incorrect Answers
A:Hosts can reach their intended SVI and authorized routed destinations without overlapping address space. This result relates to FortiSwitch SVI routing and connected routes, not the acceptance condition under test. The relevant result is: The offending misassignment is corrected with both permitted traffic and forbidden cross-tenant traffic tested.
B: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: The offending misassignment is corrected with both permitted traffic and forbidden cross-tenant traffic tested.
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: The offending misassignment is corrected with both permitted traffic and forbidden cross-tenant traffic tested.
Question 705
A provider configures S-VLAN on a tenant VDOM rather than the VDOM where its FortiLink parent exists. Which FortiSwitch configuration or corrective action BEST addresses the requirement?
- Diagnose multi-VDOM client isolation issues by correlating switch VLAN assignment and FortiGate VDOM routing/policy evidence.
- Plan S-VLAN and C-VLAN mapping with the correct FortiLink VDOM and platform support for tenant-tagged traffic.
- Validate LLDP advertisements, hold timers, peer identity and optional location data before trusting topology or emergency-service records.
- Document tenant-specific impact, current switch state and reversal steps before changing shared FortiLink VLAN/port mappings.
Explanation
Correct Answer
B:Plan S-VLAN and C-VLAN mapping with the correct FortiLink VDOM and platform support for tenant-tagged traffic. QinQ layering and VDOM assignment are separate controls; wrong outer tagging can mix customers even when inner VLAN IDs differ. Verify the action with: Inspect customer VLAN tags, service VLAN outer tag, FortiLink parent VDOM, mapping and interface capability.
Incorrect Answers
A:Diagnose multi-VDOM client isolation issues by correlating switch VLAN assignment and FortiGate VDOM routing/policy evidence. This action is relevant to Managed tenant troubleshooting across controller and access layer, not the controlling requirement in this case. A packet may be correctly switched but rejected by VDOM routing or firewall policy, or incorrectly admitted to another tenant at Layer 2. The targeted response is: Plan S-VLAN and C-VLAN mapping with the correct FortiLink VDOM and platform support for tenant-tagged traffic.
C:Validate LLDP advertisements, hold timers, peer identity and optional location data before trusting topology or emergency-service records. This action is relevant to LLDP neighbor discovery and location information, not the controlling requirement in this case. LLDP is an L2 discovery protocol and cannot prove the whole routed service path or phone emergency-location correctness by itself. The targeted response is: Plan S-VLAN and C-VLAN mapping with the correct FortiLink VDOM and platform support for tenant-tagged traffic.
D:Document tenant-specific impact, current switch state and reversal steps before changing shared FortiLink VLAN/port mappings. This action is relevant to Multi-tenant change verification and rollback, not the controlling requirement in this case. A change on shared physical transport can affect multiple VDOMs, even if each tenant's firewall policy is separate. The targeted response is: Plan S-VLAN and C-VLAN mapping with the correct FortiLink VDOM and platform support for tenant-tagged traffic.
Question 706
An added FortiSwitch uplink remains individual because its peer LACP mode is incompatible. Which TWO complementary steps identify the appropriate FortiSwitch response AND the evidence needed to verify it? Select TWO.
- Repair LACP member settings and physical port errors independently before increasing aggregate traffic.
- Management connectivity is established across the supported intermediate network without losing segmentation or authentication assumptions.
- Check that selected switch series and transceiver support split port or PHY breakout, and plan the related interface remapping.
- Check route table, next-hop ARP, ingress VLAN, egress interface, prefix length and return-route path.
- Check per-member speed, partner identity, state, optical counters, VLAN tags and aggregate distribution.
Explanation
Correct Answers
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. This is the configuration or remediation half of the requested TWO-step pair.
E:Check per-member speed, partner identity, state, optical counters, VLAN tags and aggregate distribution. One healthy physical link is not proof an aggregate has balanced traffic or that the peer LACP policy matches. The paired action is: Repair LACP member settings and physical port errors independently before increasing aggregate traffic. This is the diagnostic or verification half of the requested TWO-step pair.
Incorrect Answers
B:Management connectivity is established across the supported intermediate network without losing segmentation or authentication assumptions. This step concerns FortiLink transport over nontrivial L2 or L3 paths and is not part of the required paired solution. The correct action and evidence are: Repair LACP member settings and physical port errors independently before increasing aggregate traffic. Together with: Check per-member speed, partner identity, state, optical counters, VLAN tags and aggregate distribution.
C:Check that selected switch series and transceiver support split port or PHY breakout, and plan the related interface remapping. This step concerns FortiSwitch split port breakout mode and is not part of the required paired solution. The correct action and evidence are: Repair LACP member settings and physical port errors independently before increasing aggregate traffic. Together with: Check per-member speed, partner identity, state, optical counters, VLAN tags and aggregate distribution.
D:Check route table, next-hop ARP, ingress VLAN, egress interface, prefix length and return-route path. This step concerns Static route and default gateway validation and is not part of the required paired solution. The correct action and evidence are: Repair LACP member settings and physical port errors independently before increasing aggregate traffic. Together with: Check per-member speed, partner identity, state, optical counters, VLAN tags and aggregate distribution.
Question 707
A port inventory lists a downstream switch whose LLDP entry has expired and no longer reflects current wiring. Which diagnostic evidence should the FortiSwitch administrator examine FIRST?
- Inspect local and remote chassis and port IDs, TLV freshness, management address, interval and LLDP-MED location settings.
- Check both peer capabilities, auto-negotiation, administrative speed, cable quality and CRC/FCS counters.
- Check managed tree, ISL link health, model compatibility, VLAN carriage, depth limitations and upstream aggregate status.
- Check route table, next-hop ARP, ingress VLAN, egress interface, prefix length and return-route path.
Explanation
Correct Answer
A:Inspect local and remote chassis and port IDs, TLV freshness, management address, interval and LLDP-MED location settings. LLDP is an L2 discovery protocol and cannot prove the whole routed service path or phone emergency-location correctness by itself. The paired action is: Validate LLDP advertisements, hold timers, peer identity and optional location data before trusting topology or emergency-service records.
Incorrect Answers
B:Check both peer capabilities, auto-negotiation, administrative speed, cable quality and CRC/FCS counters. These observations are applicable to Switch port speed and duplex commissioning, but would not isolate the main failure first. The decisive evidence is: Inspect local and remote chassis and port IDs, TLV freshness, management address, interval and LLDP-MED location settings.
C:Check managed tree, ISL link health, model compatibility, VLAN carriage, depth limitations and upstream aggregate status. These observations are applicable to FortiSwitch multi-tier managed topology, but would not isolate the main failure first. The decisive evidence is: Inspect local and remote chassis and port IDs, TLV freshness, management address, interval and LLDP-MED location settings.
D:Check route table, next-hop ARP, ingress VLAN, egress interface, prefix length and return-route path. These observations are applicable to Static route and default gateway validation, but would not isolate the main failure first. The decisive evidence is: Inspect local and remote chassis and port IDs, TLV freshness, management address, interval and LLDP-MED location settings.
Question 708
A new staff VLAN exists on FortiGate but nobody has assigned it to access ports on the managed switch. Which FortiSwitch configuration or corrective action BEST addresses the requirement?
- Build FortiSwitch VLAN interfaces in the correct FortiLink context and assign ports through the managed switch controller.
- Change managed switch VLAN membership through the FortiGate controller and verify the installed configuration stays consistent.
- Connect FortiSwitch uplinks through supported FortiLink discovery or approved inter-switch link topology, verifying model port roles.
- Use supported FortiLink point-to-point L2 or Layer-3 transport configuration and validate discovery and control traffic end to end.
Explanation
Correct Answer
A:Build FortiSwitch VLAN interfaces in the correct FortiLink context and assign ports through the managed switch controller. A named VLAN in FortiOS is not proof its switch-port membership and L3 policy are correct. Verify the action with: Check FortiLink parent, VLAN ID, VDOM membership, port assignment, subnet and firewall-policy path.
Incorrect Answers
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: Build FortiSwitch VLAN interfaces in the correct FortiLink context and assign ports through the managed switch controller.
C: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: Build FortiSwitch VLAN interfaces in the correct FortiLink context and assign ports through the managed switch controller.
D:Use supported FortiLink point-to-point L2 or Layer-3 transport configuration and validate discovery and control traffic end to end. This action is relevant to FortiLink transport over nontrivial L2 or L3 paths, not the controlling requirement in this case. FortiLink over intermediate networks requires topology-specific settings; ordinary IP reachability alone does not establish FortiLink discovery. The targeted response is: Build FortiSwitch VLAN interfaces in the correct FortiLink context and assign ports through the managed switch controller.
Question 709
A camera is categorized as a general workstation and receives an overly broad VLAN assignment. Which FortiSwitch configuration or corrective action BEST addresses the requirement?
- Configure supported IGMP snooping and querier expectations to forward multicast only where receivers request it.
- Apply a specific restricted VLAN or quarantine mechanism with explicit authorized remediation and monitoring expectations.
- Configure supported IEEE 802.1X port security against an approved RADIUS service with explicit guest/unauthorized behavior.
- Apply authorized device-class rules and dynamic port policies after confirming device detection evidence and fallback outcomes.
Explanation
Correct Answer
D:Apply authorized device-class rules and dynamic port policies after confirming device detection evidence and fallback outcomes. NAC assignment relies on reliable detection and a defined precedence; a class label is not a substitute for switch-port policy. Verify the action with: Inspect device fingerprint, policy rule order, assigned VLAN, security profile, client identity and enforcement state.
Incorrect Answers
A:Configure supported IGMP snooping and querier expectations to forward multicast only where receivers request it. This action is relevant to IGMP snooping and multicast receivers, not the controlling requirement in this case. A multicast VLAN alone does not indicate that IGMP receiver membership or querier operation is healthy. The targeted response is: Apply authorized device-class rules and dynamic port policies after confirming device detection evidence and fallback outcomes.
B: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 authorized device-class rules and dynamic port policies after confirming device detection evidence and fallback outcomes.
C:Configure supported IEEE 802.1X port security against an approved RADIUS service with explicit guest/unauthorized behavior. This action is relevant to FortiSwitch 802.1X port-based authentication, not the controlling requirement in this case. A physical link can be up while 802.1X blocks traffic; the switch is the authenticator, not the authentication server. The targeted response is: Apply authorized device-class rules and dynamic port policies after confirming device detection evidence and fallback outcomes.
Question 710
A school lab asks for device isolation yet only adds a policy between VLANs, leaving same-VLAN peers connected. Which observable result BEST proves the intended FortiSwitch operation or security policy works?
- Runaway flooding is contained without blocking legitimate broadcast-based onboarding or multicast subscribers.
- Authorized endpoints enter only permitted VLANs while failed authentication is denied or restricted according to policy.
- Isolated clients can reach approved gateways while direct lateral traffic within the VLAN is blocked according to policy.
- The failed ISL or switch is isolated and recovered with all unaffected downstream switches remaining correctly managed.
Explanation
Correct Answer
C:Isolated clients can reach approved gateways while direct lateral traffic within the VLAN is blocked according to policy. Routing-level firewall rules may not inspect local Layer-2 forwarding unless intra-VLAN isolation is configured.
Incorrect Answers
A:Runaway flooding is contained without blocking legitimate broadcast-based onboarding or multicast subscribers. This result relates to Storm-control thresholds and broadcast containment, not the acceptance condition under test. The relevant result is: Isolated clients can reach approved gateways while direct lateral traffic within the VLAN is blocked according to policy.
B: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: Isolated clients can reach approved gateways while direct lateral traffic within the VLAN is blocked according to policy.
D:The failed ISL or switch is isolated and recovered with all unaffected downstream switches remaining correctly managed. This result relates to Stack failure isolation and switch-to-switch port roles, not the acceptance condition under test. The relevant result is: Isolated clients can reach approved gateways while direct lateral traffic within the VLAN is blocked according to policy.