Fortinet NSE5_FSW_AD-7.6 Practice Test 58
Question 570
Two remote sites share overlapping prefixes and a broad static route inadvertently sends traffic to the wrong location. 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.
- Verify mirror connection, FortiGate sniffing interface, capture expression, expected VLAN tags and packet direction.
- Check route table, next-hop ARP, ingress VLAN, egress interface, prefix length and return-route path.
- Inspect guard role, BPDU reception, root-ID history, STP port role and loop-condition log.
Explanation
Correct Answer
C:Check route table, next-hop ARP, ingress VLAN, egress interface, prefix length and return-route path. A default route cannot repair local VLAN tagging or a missing neighbor resolution condition. The paired action is: Set a supported default route or precise static prefix toward a reachable next hop and validate return traffic.
Incorrect Answers
A:Inspect source MAC entries by VLAN, ingress/egress port, address aging, LAG membership and broadcast counters. These observations are applicable to Layer 2 MAC-learning and forwarding decisions, but would not isolate the main failure first. The decisive evidence is: Check route table, next-hop ARP, ingress VLAN, egress interface, prefix length and return-route path.
B:Verify mirror connection, FortiGate sniffing interface, capture expression, expected VLAN tags and packet direction. These observations are applicable to FortiGate one-arm sniffer across managed switching, but would not isolate the main failure first. The decisive evidence is: Check route table, next-hop ARP, ingress VLAN, egress interface, prefix length and return-route path.
D: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: Check route table, next-hop ARP, ingress VLAN, egress interface, prefix length and return-route path.
Question 571
A printer is moved to a new patch panel but its MAC keeps appearing on an old trunk member. 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.
- Inspect FortiLink management state, native/tagged VLANs, port membership, FortiGate interface and active firewall policy.
- Check group membership table, querier identity, IGMP report traffic, VLAN and target egress port.
- Inspect FortiLink operational mode, controller ownership, current management address, VDOM and switch model support.
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: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 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 FortiLink operational mode, controller ownership, current management address, VDOM and switch model support. These observations are applicable to FortiSwitch standalone versus FortiLink managed L3 ownership, but would not isolate the main failure first. The decisive evidence is: Inspect source MAC entries by VLAN, ingress/egress port, address aging, LAG membership and broadcast counters.
Question 572
A core maintenance event disconnects one MCLAG peer link and the operator checks only client ping. Which TWO complementary steps identify the appropriate FortiSwitch response AND the evidence needed to verify it? Select TWO.
- Inspect MCLAG peer group, peer-link status, LACP members, VLAN consistency and split-brain safeguards.
- The suspect device is restricted without interrupting unrelated tenants and can be restored after review.
- Plan FortiLink management under FortiGate HA with supported links, peer roles and deterministic failover tests.
- Review firmware compatibility, release notes, current image, boot fallback, managed switch inventory and upgrade sequencing.
- Use documented peer-group and downstream trunk configuration for MCLAG rather than creating ad hoc parallel Ethernet links.
Explanation
Correct Answers
A: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. This is the diagnostic or verification half of the requested TWO-step pair.
E:Use documented peer-group and downstream trunk configuration for MCLAG rather than creating ad hoc parallel Ethernet links. MCLAG requires peer coordination and correct downstream aggregation; it is not equivalent to connecting independent switches in parallel. Verify the action with: Inspect MCLAG peer group, peer-link status, LACP members, VLAN consistency and split-brain safeguards. This is the configuration or remediation half of the requested TWO-step pair.
Incorrect Answers
B:The suspect device is restricted without interrupting unrelated tenants and can be restored after review. This step concerns VLAN security policy and quarantine actions and is not part of the required paired solution. The correct action and evidence are: Use documented peer-group and downstream trunk configuration for MCLAG rather than creating ad hoc parallel Ethernet links. Together with: Inspect MCLAG peer group, peer-link status, LACP members, VLAN consistency and split-brain safeguards.
C:Plan FortiLink management under FortiGate HA with supported links, peer roles and deterministic failover tests. This step concerns HA FortiGate pair managing switch topology and is not part of the required paired solution. The correct action and evidence are: Use documented peer-group and downstream trunk configuration for MCLAG rather than creating ad hoc parallel Ethernet links. Together with: Inspect MCLAG peer group, peer-link status, LACP members, VLAN consistency and split-brain safeguards.
D:Review firmware compatibility, release notes, current image, boot fallback, managed switch inventory and upgrade sequencing. This step concerns Firmware and lifecycle preparation for FortiSwitch and is not part of the required paired solution. The correct action and evidence are: Use documented peer-group and downstream trunk configuration for MCLAG rather than creating ad hoc parallel Ethernet links. Together with: Inspect MCLAG peer group, peer-link status, LACP members, VLAN consistency and split-brain safeguards.
Question 573
A tenant laptop obtains a valid lease but cannot reach services because its gateway interface belongs to another VDOM. Which FortiSwitch configuration or corrective action BEST addresses the requirement?
- Use a supported direct FortiLink connection and confirm controller traffic and client forwarding on the intended interfaces.
- Validate the supported PoE budget and LLDP-MED endpoint power negotiation rather than equating link up with adequate wattage.
- Choose supported FortiSwitchOS version and maintenance workflow compatible with the FortiGate version and topology.
- Diagnose multi-VDOM client isolation issues by correlating switch VLAN assignment and FortiGate VDOM routing/policy evidence.
Explanation
Correct Answer
D: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: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: Diagnose multi-VDOM client isolation issues by correlating switch VLAN assignment and FortiGate VDOM routing/policy evidence.
B:Validate the supported PoE budget and LLDP-MED endpoint power negotiation rather than equating link up with adequate wattage. This action is relevant to PoE and LLDP-MED endpoint power coordination, not the controlling requirement in this case. Port count and Ethernet link state do not guarantee sufficient power for high-draw endpoints. The targeted response is: Diagnose multi-VDOM client isolation issues by correlating switch VLAN assignment and FortiGate VDOM routing/policy evidence.
C:Choose supported FortiSwitchOS version and maintenance workflow compatible with the FortiGate version and topology. This action is relevant to Firmware and lifecycle preparation for FortiSwitch, not the controlling requirement in this case. A successful image upload does not prove switch operation or controller compatibility after reboot. The targeted response is: Diagnose multi-VDOM client isolation issues by correlating switch VLAN assignment and FortiGate VDOM routing/policy evidence.
Question 574
A port inventory lists a downstream switch whose LLDP entry has expired and no longer reflects current wiring. 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.
- Check MAC-learning table and flooding behavior before replacing a switch or changing its IP routing.
- Verify FortiLink management status and user VLAN reachability independently when a switch is authorized but clients fail.
- Correlate stack and ISL status to identify the failed path instead of reconfiguring all access VLANs.
Explanation
Correct Answer
A: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
B:Check MAC-learning table and flooding behavior before replacing a switch or changing its IP routing. This action is relevant to Layer 2 MAC-learning and forwarding decisions, not the controlling requirement in this case. 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 targeted response is: Validate LLDP advertisements, hold timers, peer identity and optional location data before trusting topology or emergency-service records.
C:Verify FortiLink management status and user VLAN reachability independently when a switch is authorized but clients fail. This action is relevant to FortiLink control and client VLAN transport separation, not the controlling requirement in this case. FortiLink transports management and data; a successful controller heartbeat does not guarantee a user VLAN or firewall session is permitted. The targeted response is: Validate LLDP advertisements, hold timers, peer identity and optional location data before trusting topology or emergency-service records.
D:Correlate stack and ISL status to identify the failed path instead of reconfiguring all access VLANs. This action is relevant to Stack failure isolation and switch-to-switch port roles, not the controlling requirement in this case. 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 targeted response is: Validate LLDP advertisements, hold timers, peer identity and optional location data before trusting topology or emergency-service records.
Question 575
A replacement switch is installed without checking whether its old firmware supports the current FortiLink controller. Which observable result BEST proves the intended FortiSwitch operation or security policy works?
- Both ends connect at compatible rates with stable errors and required throughput.
- A moved device is traced to its current approved port and incorrect cross-connection is identified.
- A trace shows the expected ingress/egress control packets without collecting unrelated sensitive network traffic.
- A failed managed switch can be replaced with supported firmware and restored authorized port/VLAN behavior.
Explanation
Correct Answer
D:A failed managed switch can be replaced with supported firmware and restored authorized port/VLAN behavior. Backups require correct model/version and an actual restore procedure; a saved file name is not proof a recovered switch will work.
Incorrect Answers
A: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: A failed managed switch can be replaced with supported firmware and restored authorized port/VLAN behavior.
B: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: A failed managed switch can be replaced with supported firmware and restored authorized port/VLAN behavior.
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: A failed managed switch can be replaced with supported firmware and restored authorized port/VLAN behavior.
Question 576
A security team sends a DACL for an unauthenticated session and assumes the switch applied its hardware entries. Which FortiSwitch configuration or corrective action BEST addresses the requirement?
- Set model-supported dynamic MAC address learning limits and specific violation action on access-facing switch ports.
- Verify dynamic ACL assignment from RADIUS after successful 802.1X and account for platform rule and IPv4 support constraints.
- Trace MAC-learning and forwarding across the precise VLAN and repair only missing approved membership.
- Verify that supported CoA or dynamic user security profiles are enforced on authenticated sessions under the deployed topology.
Explanation
Correct Answer
D:Verify that supported CoA or dynamic user security profiles are enforced on authenticated sessions under the deployed topology. RADIUS authentication success is not proof that a downloadable ACL or CoA update was enforced; some modes have documented conditions. Verify the action with: Review RADIUS Access-Accept attributes, CoA path, session identifier, switch port role, DACL installation and packet test.
Incorrect Answers
A:Set model-supported dynamic MAC address learning limits and specific violation action on access-facing switch ports. This action is relevant to Port MAC learning-limit and violation controls, not the controlling requirement in this case. Dynamic MAC learning limits reduce accidental fan-out but should be tuned for legitimate multi-device access designs. The targeted response is: Verify that supported CoA or dynamic user security profiles are enforced on authenticated sessions under the deployed topology.
B:Verify dynamic ACL assignment from RADIUS after successful 802.1X and account for platform rule and IPv4 support constraints. This action is relevant to DACL RADIUS attribute and per-session enforcement, not the controlling requirement in this case. DACLs install after successful authorization and documented release limits apply; a RADIUS response alone is not proof of forwarding enforcement. The targeted response is: Verify that supported CoA or dynamic user security profiles are enforced on authenticated sessions under the deployed topology.
C:Trace MAC-learning and forwarding across the precise VLAN and repair only missing approved membership. This action is relevant to VLAN access isolation and troubleshooting of membership, not the controlling requirement in this case. Link up and successful traffic in one VLAN do not prove every VLAN is correctly provisioned on the path. The targeted response is: Verify that supported CoA or dynamic user security profiles are enforced on authenticated sessions under the deployed topology.
Question 577
A school lab asks for device isolation yet only adds a policy between VLANs, leaving same-VLAN peers connected. Which FortiSwitch configuration or corrective action BEST addresses the requirement?
- Verify that supported CoA or dynamic user security profiles are enforced on authenticated sessions under the deployed topology.
- Set model-supported dynamic MAC address learning limits and specific violation action on access-facing switch ports.
- Use supported intra-VLAN traffic controls when clients in the same broadcast domain must not communicate directly.
- Build a documented supported FortiSwitch daisy chain or multi-tier topology with adequate ISL uplink capacity and safeguards.
Explanation
Correct Answer
C:Use supported intra-VLAN traffic controls when clients in the same broadcast domain must not communicate directly. Routing-level firewall rules may not inspect local Layer-2 forwarding unless intra-VLAN isolation is configured. Verify the action with: Review target VLAN, switch isolation controls, client MAC table, permitted gateway path and peer-to-peer test.
Incorrect Answers
A: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: Use supported intra-VLAN traffic controls when clients in the same broadcast domain must not communicate directly.
B:Set model-supported dynamic MAC address learning limits and specific violation action on access-facing switch ports. This action is relevant to Port MAC learning-limit and violation controls, not the controlling requirement in this case. Dynamic MAC learning limits reduce accidental fan-out but should be tuned for legitimate multi-device access designs. The targeted response is: Use supported intra-VLAN traffic controls when clients in the same broadcast domain must not communicate directly.
D:Build a documented supported FortiSwitch daisy chain or multi-tier topology with adequate ISL uplink capacity and safeguards. This action is relevant to FortiSwitch multi-tier managed topology, not the controlling requirement in this case. A FortiGate controls each FortiSwitch through the managed Layer-2 topology, but downstream reachability depends on upstream FortiLink links. The targeted response is: Use supported intra-VLAN traffic controls when clients in the same broadcast domain must not communicate directly.
Question 578
An engineer enables legacy public read-write SNMP community strings to save time and exposes management data. Which FortiSwitch configuration or corrective action BEST addresses the requirement?
- Mirror only the relevant source ports or VLAN traffic to a dedicated analyzer destination using supported SPAN settings.
- Set model-supported dynamic MAC address learning limits and specific violation action on access-facing switch ports.
- Collect supported SNMP or sFlow telemetry securely with appropriate collector authorization, sampling and interface scope.
- Trace DHCP and ARP exchanges at ingress and uplink to distinguish missing requests from blocked or malformed responses.
Explanation
Correct Answer
C:Collect supported SNMP or sFlow telemetry securely with appropriate collector authorization, sampling and interface scope. Flow samples are estimates and counters vary by port; collecting telemetry cannot replace a controlled packet capture when headers are needed. Verify the action with: Inspect monitoring credentials, SNMP version, sFlow export destination, sample rate, counter freshness and access policy.
Incorrect Answers
A:Mirror only the relevant source ports or VLAN traffic to a dedicated analyzer destination using supported SPAN settings. This action is relevant to FortiSwitch port mirroring to network analyzer, not the controlling requirement in this case. A mirrored stream is passive evidence and can be incomplete if analyzer bandwidth is lower than the observed traffic. The targeted response is: Collect supported SNMP or sFlow telemetry securely with appropriate collector authorization, sampling and interface scope.
B:Set model-supported dynamic MAC address learning limits and specific violation action on access-facing switch ports. This action is relevant to Port MAC learning-limit and violation controls, not the controlling requirement in this case. Dynamic MAC learning limits reduce accidental fan-out but should be tuned for legitimate multi-device access designs. The targeted response is: Collect supported SNMP or sFlow telemetry securely with appropriate collector authorization, sampling and interface scope.
D:Trace DHCP and ARP exchanges at ingress and uplink to distinguish missing requests from blocked or malformed responses. This action is relevant to Capture-based DHCP and ARP path isolation, not the controlling requirement in this case. A DHCP lease failure can originate at the client, switch, relay or server; capturing at one side alone is not always conclusive. The targeted response is: Collect supported SNMP or sFlow telemetry securely with appropriate collector authorization, sampling and interface scope.
Question 579
A new staff VLAN exists on FortiGate but nobody has assigned it to access ports on the managed switch. Which diagnostic evidence should the FortiSwitch administrator examine FIRST?
- Inspect FortiLink operational mode, controller ownership, current management address, VDOM and switch model support.
- Check FortiLink parent, VLAN ID, VDOM membership, port assignment, subnet and firewall-policy path.
- Inspect shared-port VLAN diff, tenant inventory, VDOM policy, change approval and representative positive/negative access tests.
- Inspect transceiver SKU, supported compatibility table, Tx/Rx optical power, interface alarms and cable plant type.
Explanation
Correct Answer
B:Check FortiLink parent, VLAN ID, VDOM membership, port assignment, subnet and firewall-policy path. A named VLAN in FortiOS is not proof its switch-port membership and L3 policy are correct. The paired action is: Build FortiSwitch VLAN interfaces in the correct FortiLink context and assign ports through the managed switch controller.
Incorrect Answers
A:Inspect FortiLink operational mode, controller ownership, current management address, VDOM and switch model support. These observations are applicable to FortiSwitch standalone versus FortiLink managed L3 ownership, but would not isolate the main failure first. The decisive evidence is: Check FortiLink parent, VLAN ID, VDOM membership, port assignment, subnet and firewall-policy path.
C: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: Check FortiLink parent, VLAN ID, VDOM membership, port assignment, subnet and firewall-policy path.
D:Inspect transceiver SKU, supported compatibility table, Tx/Rx optical power, interface alarms and cable plant type. These observations are applicable to Optic compatibility and laser diagnostic evidence, but would not isolate the main failure first. The decisive evidence is: Check FortiLink parent, VLAN ID, VDOM membership, port assignment, subnet and firewall-policy path.
Question 580
The only switch backup was taken before a year of VLAN changes and restore loses critical networks. Which diagnostic evidence should the FortiSwitch administrator examine FIRST?
- Inspect FortiGate HA active member, FortiLink aggregate state, ISL, MCLAG peer link, standby path and STP roles.
- Check switch serial, active software version, current synchronized configuration, backup timestamp, integrity and recovery permissions.
- Inspect port profile assignment, FortiGate controller policy, client role, enforcement counters and overlapping static controls.
- Inspect switch serial, discovered state, pending approval, controller permissions, post-authorize reboot and managed mode.
Explanation
Correct Answer
B:Check switch serial, active software version, current synchronized configuration, backup timestamp, integrity and recovery permissions. Backups require correct model/version and an actual restore procedure; a saved file name is not proof a recovered switch will work. The paired action is: Retrieve and maintain approved FortiSwitch model, firmware, configuration and authorized-controller records to support incident recovery.
Incorrect Answers
A:Inspect FortiGate HA active member, FortiLink aggregate state, ISL, MCLAG peer link, standby path and STP roles. These observations are applicable to FortiLink HA and MCLAG topology faults, but would not isolate the main failure first. The decisive evidence is: Check switch serial, active software version, current synchronized configuration, backup timestamp, integrity and recovery permissions.
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: Check switch serial, active software version, current synchronized configuration, backup timestamp, integrity and recovery permissions.
D:Inspect switch serial, discovered state, pending approval, controller permissions, post-authorize reboot and managed mode. These observations are applicable to Controller authorization and pending-switch state, but would not isolate the main failure first. The decisive evidence is: Check switch serial, active software version, current synchronized configuration, backup timestamp, integrity and recovery permissions.