Fortinet NSE5_FSW_AD-7.6 Practice Test 43
Question 420
Two distribution switches report an unexpected LLDP neighbor after a contractor reroutes patch cables. 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.
- Validate LLDP advertisements, hold timers, peer identity and optional location data before trusting topology or emergency-service records.
- Determine whether a switch is managed by FortiGate or standalone before setting interfaces, routes or admin policies.
- Apply supported egress CoS queue policy to reduce latency under congestion without starving other required traffic.
Explanation
Correct Answer
B:Validate LLDP advertisements, hold timers, peer identity and optional location data before trusting topology or emergency-service records. LLDP is an L2 discovery protocol and cannot prove the whole routed service path or phone emergency-location correctness by itself. Verify the action with: Inspect local and remote chassis and port IDs, TLV freshness, management address, interval and LLDP-MED location settings.
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: Validate LLDP advertisements, hold timers, peer identity and optional location data before trusting topology or emergency-service records.
C:Determine whether a switch is managed by FortiGate or standalone before setting interfaces, routes or admin policies. This action is relevant to FortiSwitch standalone versus FortiLink managed L3 ownership, not the controlling requirement in this case. Direct edits on a managed switch can be overridden; standalone configuration must be maintained and backed up independently. The targeted response is: Validate LLDP advertisements, hold timers, peer identity and optional location data before trusting topology or emergency-service records.
D: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: Validate LLDP advertisements, hold timers, peer identity and optional location data before trusting topology or emergency-service records.
Question 421
A switch shows repeated FortiLink disconnects after a configuration push and the team reads only client DHCP logs. Which FortiSwitch configuration or corrective action BEST addresses the requirement?
- Collect supported SNMP or sFlow telemetry securely with appropriate collector authorization, sampling and interface scope.
- Collect relevant FortiSwitch controller diagnostics, switch system events and targeted status output before making configuration changes.
- Create a bounded packet-capture profile on the right switch interface with a narrow filter, then start/stop and inspect frames.
- Use supported FortiLink point-to-point L2 or Layer-3 transport configuration and validate discovery and control traffic end to end.
Explanation
Correct Answer
B:Collect relevant FortiSwitch controller diagnostics, switch system events and targeted status output before making configuration changes. A log message without source device, time and relevant state is not adequate to prove root cause. Verify the action with: Inspect controller switch list, interface events, authentication logs, current configuration, timestamps and recent change history.
Incorrect Answers
A:Collect supported SNMP or sFlow telemetry securely with appropriate collector authorization, sampling and interface scope. This action is relevant to SNMP and sFlow monitoring configuration, not the controlling requirement in this case. Flow samples are estimates and counters vary by port; collecting telemetry cannot replace a controlled packet capture when headers are needed. The targeted response is: Collect relevant FortiSwitch controller diagnostics, switch system events and targeted status output before making configuration changes.
C:Create a bounded packet-capture profile on the right switch interface with a narrow filter, then start/stop and inspect frames. This action is relevant to FortiSwitch local packet-capture profile and filters, not the controlling requirement in this case. 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. The targeted response is: Collect relevant FortiSwitch controller diagnostics, switch system events and targeted status output before making configuration changes.
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: Collect relevant FortiSwitch controller diagnostics, switch system events and targeted status output before making configuration changes.
Question 422
An engineer accidentally configures the laptop's analyzer port as a production access uplink rather than the monitor destination. Which observable result BEST proves the intended FortiSwitch operation or security policy works?
- The analyzer receives the intended copies while production forwarding remains unchanged.
- A controlled failure test restores approved management and access connectivity through the designed redundant path.
- The managed switch retains the intended controller-pushed policy after a controlled synchronization and restart.
- A moved device is traced to its current approved port and incorrect cross-connection is identified.
Explanation
Correct Answer
A:The analyzer receives the intended copies while production forwarding remains unchanged. A mirrored stream is passive evidence and can be incomplete if analyzer bandwidth is lower than the observed traffic.
Incorrect Answers
B:A controlled failure test restores approved management and access connectivity through the designed redundant path. This result relates to FortiLink HA and MCLAG topology faults, not the acceptance condition under test. The relevant result is: The analyzer receives the intended copies while production forwarding remains unchanged.
C:The managed switch retains the intended controller-pushed policy after a controlled synchronization and restart. This result relates to Managed switch configuration synchronization, not the acceptance condition under test. The relevant result is: The analyzer receives the intended copies while production forwarding remains unchanged.
D: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 analyzer receives the intended copies while production forwarding remains unchanged.
Question 423
A switch CLI patch fixes a VLAN temporarily but disappears after controller synchronization. Which observable result BEST proves the intended FortiSwitch operation or security policy works?
- The new FortiSwitch discovers the designated controller while unrelated FortiGate interfaces retain their normal function.
- Hosts can reach their intended SVI and authorized routed destinations without overlapping address space.
- The managed switch retains the intended controller-pushed policy after a controlled synchronization and restart.
- Switches reconnect to FortiLink and preserve approved VLAN/role configuration after the planned upgrade.
Explanation
Correct Answer
C:The managed switch retains the intended controller-pushed policy after a controlled synchronization and restart. Local changes on a FortiLink-managed switch can be discarded when the FortiGate controller reapplies its known configuration.
Incorrect Answers
A: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 managed switch retains the intended controller-pushed policy after a controlled synchronization and restart.
B: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 managed switch retains the intended controller-pushed policy after a controlled synchronization and restart.
D:Switches reconnect to FortiLink and preserve approved VLAN/role configuration after the planned upgrade. This result relates to Firmware and lifecycle preparation for FortiSwitch, not the acceptance condition under test. The relevant result is: The managed switch retains the intended controller-pushed policy after a controlled synchronization and restart.
Question 424
A conference room allows one phone and one PC but an overstrict MAC learning limit blocks the PC. Which FortiSwitch configuration or corrective action BEST addresses the requirement?
- Validate LLDP advertisements, hold timers, peer identity and optional location data before trusting topology or emergency-service records.
- Verify that supported CoA or dynamic user security profiles are enforced on authenticated sessions under the deployed topology.
- Apply authorized device-class rules and dynamic port policies after confirming device detection evidence and fallback outcomes.
- Set model-supported dynamic MAC address learning limits and specific violation action on access-facing switch ports.
Explanation
Correct Answer
D:Set model-supported dynamic MAC address learning limits and specific violation action on access-facing switch ports. Dynamic MAC learning limits reduce accidental fan-out but should be tuned for legitimate multi-device access designs. Verify the action with: Inspect MAC table usage, configured learning limit, learned device count, port-security event and violation action.
Incorrect Answers
A: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: Set model-supported dynamic MAC address learning limits and specific violation action on access-facing switch ports.
B:Verify that supported CoA or dynamic user security profiles are enforced on authenticated sessions under the deployed topology. This action is relevant to RADIUS change of authorization and applied session policy, not the controlling requirement in this case. RADIUS authentication success is not proof that a downloadable ACL or CoA update was enforced; some modes have documented conditions. The targeted response is: Set model-supported dynamic MAC address learning limits and specific violation action on access-facing switch ports.
C:Apply authorized device-class rules and dynamic port policies after confirming device detection evidence and fallback outcomes. This action is relevant to NAC dynamic port policy device classification, not the controlling requirement in this case. NAC assignment relies on reliable detection and a defined precedence; a class label is not a substitute for switch-port policy. The targeted response is: Set model-supported dynamic MAC address learning limits and specific violation action on access-facing switch ports.
Question 425
A new tenant's DHCP VLAN is permitted but an old customer unexpectedly loses service due to a broad template overwrite. Which observable result BEST proves the intended FortiSwitch operation or security policy works?
- A downstream dual-homed switch retains service on one peer failure without duplicate independent forwarding loops.
- The new FortiSwitch discovers the designated controller while unrelated FortiGate interfaces retain their normal function.
- 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.
Explanation
Correct Answer
D:The intended tenant configuration changes while other tenants retain their segmentation and service. A change on shared physical transport can affect multiple VDOMs, even if each tenant's firewall policy is separate.
Incorrect Answers
A:A downstream dual-homed switch retains service on one peer failure without duplicate independent forwarding loops. This result relates to MCLAG peer-link topology for managed access switches, not the acceptance condition under test. The relevant result is: The intended tenant configuration changes while other tenants retain their segmentation and service.
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 intended tenant configuration changes while other tenants retain their segmentation and service.
C:A tenant reaches only its approved VDOM resources and does not inherit another tenant's policies. This result relates to FortiGate VDOM-based FortiSwitch tenant assignment, not the acceptance condition under test. The relevant result is: The intended tenant configuration changes while other tenants retain their segmentation and service.
Question 426
A new FortiSwitch is connected to a port that was not enabled as FortiLink on FortiGate. Which FortiSwitch configuration or corrective action BEST addresses the requirement?
- Distinguish FortiSwitch discovery from authorization, and restore the correct controller ownership without automatically trusting unknown devices.
- Configure supported switch virtual interfaces and routed gateway addresses with correct VLAN, subnet and management context.
- Troubleshoot FortiLink discovery from physical and logical interface configuration through LLDP and management addressing.
- Collect relevant FortiSwitch controller diagnostics, switch system events and targeted status output before making configuration changes.
Explanation
Correct Answer
C:Troubleshoot FortiLink discovery from physical and logical interface configuration through LLDP and management addressing. A green Ethernet link is necessary for many paths but does not prove the FortiLink management protocol or discovery is working. Verify the action with: Inspect FortiGate FortiLink status, supported discovery port, LLDP frames, interface IP, link errors and switch serial.
Incorrect Answers
A:Distinguish FortiSwitch discovery from authorization, and restore the correct controller ownership without automatically trusting unknown devices. This action is relevant to Controller authorization and pending-switch state, not the controlling requirement in this case. Authorizing a switch is an administrative trust step; pending switch state is not evidence of a routing failure. The targeted response is: Troubleshoot FortiLink discovery from physical and logical interface configuration through LLDP and management addressing.
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: Troubleshoot FortiLink discovery from physical and logical interface configuration through LLDP and management addressing.
D:Collect relevant FortiSwitch controller diagnostics, switch system events and targeted status output before making configuration changes. This action is relevant to FortiSwitch diagnostic commands and logs, not the controlling requirement in this case. A log message without source device, time and relevant state is not adequate to prove root cause. The targeted response is: Troubleshoot FortiLink discovery from physical and logical interface configuration through LLDP and management addressing.
Question 427
A core upgrade reelects root for one VLAN but not others, disrupting a downstream aggregation path. Which TWO complementary steps identify the appropriate FortiSwitch response AND the evidence needed to verify it? Select TWO.
- Set only mutually supported Ethernet port rates and verify operational negotiation instead of forcing mismatched speeds.
- Use compatible spanning-tree mode across connected switches and verify per-VLAN root and blocked links.
- Inspect local mode, per-VLAN bridge ID, peer BPDUs, port state, timers and topology-change history.
- Inspect transceiver SKU, supported compatibility table, Tx/Rx optical power, interface alarms and cable plant type.
- Controller and switch return to supported synchronized software and configuration with test-client services restored.
Explanation
Correct Answers
B: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. This is the configuration or remediation half of the requested TWO-step pair.
C:Inspect local mode, per-VLAN bridge ID, peer BPDUs, port state, timers and topology-change history. An STP mode change can change per-VLAN convergence behavior even if existing links remain physically up. The paired action is: Use compatible spanning-tree mode across connected switches and verify per-VLAN root and blocked links. This is the diagnostic or verification half of the requested TWO-step pair.
Incorrect Answers
A:Set only mutually supported Ethernet port rates and verify operational negotiation instead of forcing mismatched speeds. This step concerns Switch port speed and duplex commissioning and is not part of the required paired solution. The correct action and evidence are: Use compatible spanning-tree mode across connected switches and verify per-VLAN root and blocked links. Together with: Inspect local mode, per-VLAN bridge ID, peer BPDUs, port state, timers and topology-change history.
D:Inspect transceiver SKU, supported compatibility table, Tx/Rx optical power, interface alarms and cable plant type. This step concerns Optic compatibility and laser diagnostic evidence and is not part of the required paired solution. The correct action and evidence are: Use compatible spanning-tree mode across connected switches and verify per-VLAN root and blocked links. Together with: Inspect local mode, per-VLAN bridge ID, peer BPDUs, port state, timers and topology-change history.
E: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: Use compatible spanning-tree mode across connected switches and verify per-VLAN root and blocked links. Together with: Inspect local mode, per-VLAN bridge ID, peer BPDUs, port state, timers and topology-change history.
Question 428
A managed FortiSwitch loses VLAN policy after reboot because prior local CLI edits never entered FortiGate configuration. Which observable result BEST proves the intended FortiSwitch operation or security policy works?
- The intended switch appears in discovery after restoring the precise missing interface or transport prerequisite.
- Routes and interfaces are configured at the appropriate control plane and persist after synchronization or reboot.
- Controller and switch return to supported synchronized software and configuration with test-client services restored.
- A controlled failure test restores approved management and access connectivity through the designed redundant path.
Explanation
Correct Answer
C:Controller and switch return to supported synchronized software and configuration with test-client services restored. Managed switches can be reachable at Layer 2 yet show stale policy after incompatible upgrade or failed controller push.
Incorrect Answers
A:The intended switch appears in discovery after restoring the precise missing interface or transport prerequisite. This result relates to FortiLink discovery failure and physical uplink path, not the acceptance condition under test. The relevant result is: Controller and switch return to supported synchronized software and configuration with test-client services restored.
B:Routes and interfaces are configured at the appropriate control plane and persist after synchronization or reboot. This result relates to FortiSwitch standalone versus FortiLink managed L3 ownership, not the acceptance condition under test. The relevant result is: Controller and switch return to supported synchronized software and configuration with test-client services restored.
D:A controlled failure test restores approved management and access connectivity through the designed redundant path. This result relates to FortiLink HA and MCLAG topology faults, not the acceptance condition under test. The relevant result is: Controller and switch return to supported synchronized software and configuration with test-client services restored.
Question 429
A technician chooses a switch port without auto-discovery support and assumes the FortiGate will still detect it by magic. Which FortiSwitch configuration or corrective action BEST addresses the requirement?
- Enable IPv4 source guard on supported switch interfaces only with appropriate DHCP snooping or static bindings.
- Mirror only the relevant source ports or VLAN traffic to a dedicated analyzer destination using supported SPAN settings.
- Troubleshoot FortiLink discovery from physical and logical interface configuration through LLDP and management addressing.
- Correlate LLDP neighbor inventory and VLAN-specific MAC entries to reconstruct actual endpoint and uplink paths.
Explanation
Correct Answer
C:Troubleshoot FortiLink discovery from physical and logical interface configuration through LLDP and management addressing. A green Ethernet link is necessary for many paths but does not prove the FortiLink management protocol or discovery is working. Verify the action with: Inspect FortiGate FortiLink status, supported discovery port, LLDP frames, interface IP, link errors and switch serial.
Incorrect Answers
A:Enable IPv4 source guard on supported switch interfaces only with appropriate DHCP snooping or static bindings. This action is relevant to IPv4 source guard and binding-based packet filtering, not the controlling requirement in this case. Source guard is an ingress source-binding check, not a full replacement for routed firewall policies or endpoint security. The targeted response is: Troubleshoot FortiLink discovery from physical and logical interface configuration through LLDP and management addressing.
B: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: Troubleshoot FortiLink discovery from physical and logical interface configuration through LLDP and management addressing.
D: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: Troubleshoot FortiLink discovery from physical and logical interface configuration through LLDP and management addressing.
Question 430
A provider configures S-VLAN on a tenant VDOM rather than the VDOM where its FortiLink parent exists. Which diagnostic evidence should the FortiSwitch administrator examine FIRST?
- Review RADIUS Access-Accept attributes, CoA path, session identifier, switch port role, DACL installation and packet test.
- Inspect shared-port VLAN diff, tenant inventory, VDOM policy, change approval and representative positive/negative access tests.
- Inspect primary/secondary FortiGate roles, HA health, FortiLink uplinks, downstream switch topology and session continuity.
- Inspect customer VLAN tags, service VLAN outer tag, FortiLink parent VDOM, mapping and interface capability.
Explanation
Correct Answer
D: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.
Incorrect Answers
A:Review RADIUS Access-Accept attributes, CoA path, session identifier, switch port role, DACL installation and packet test. These observations are applicable to RADIUS change of authorization and applied session policy, but would not isolate the main failure first. The decisive evidence is: Inspect customer VLAN tags, service VLAN outer tag, FortiLink parent VDOM, mapping and interface capability.
B:Inspect shared-port VLAN diff, tenant inventory, VDOM policy, change approval and representative positive/negative access tests. These observations are applicable to Multi-tenant change verification and rollback, but would not isolate the main failure first. The decisive evidence is: Inspect customer VLAN tags, service VLAN outer tag, FortiLink parent VDOM, mapping and interface capability.
C:Inspect primary/secondary FortiGate roles, HA health, FortiLink uplinks, downstream switch topology and session continuity. These observations are applicable to HA FortiGate pair managing switch topology, but would not isolate the main failure first. The decisive evidence is: Inspect customer VLAN tags, service VLAN outer tag, FortiLink parent VDOM, mapping and interface capability.