Fortinet NSE5_FSW_AD-7.6 Practice Test 29
Question 280
A phone and computer share one access port but the policy authenticates only the first observed MAC address. Which observable result BEST proves the intended FortiSwitch operation or security policy works?
- Authorized endpoints enter only permitted VLANs while failed authentication is denied or restricted according to policy.
- All subtending managed switches remain discoverable and user service survives expected single-link failures where supported.
- Legitimate clients lease addresses while rogue DHCP servers connected to untrusted access ports cannot answer.
- Approved legacy devices gain only restricted services while unknown or spoofed MAC addresses remain constrained.
Explanation
Correct Answer
D:Approved legacy devices gain only restricted services while unknown or spoofed MAC addresses remain constrained. A MAC address can be cloned; MAC authentication must be combined with appropriate segmentation and monitoring.
Incorrect Answers
A: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: Approved legacy devices gain only restricted services while unknown or spoofed MAC addresses remain constrained.
B: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: Approved legacy devices gain only restricted services while unknown or spoofed MAC addresses remain constrained.
C:Legitimate clients lease addresses while rogue DHCP servers connected to untrusted access ports cannot answer. This result relates to DHCP snooping trust-boundary enforcement, not the acceptance condition under test. The relevant result is: Approved legacy devices gain only restricted services while unknown or spoofed MAC addresses remain constrained.
Question 281
Both ends of a branch trunk are set to passive LACP and none of the physical ports aggregate. Which FortiSwitch configuration or corrective action BEST addresses the requirement?
- Set measured storm-control thresholds for broadcast, multicast or unknown unicast as supported and validate needed discovery protocols.
- Configure supported FortiSwitch MCLAG peer groups and peer links before connecting downstream redundant bundles.
- Choose static, active or passive LACP trunk behavior consistently between peers and verify member aggregation.
- Use FortiLink split-interface or standby interfaces only for supported topology and verify active versus backup port behavior.
Explanation
Correct Answer
C:Choose static, active or passive LACP trunk behavior consistently between peers and verify member aggregation. Passive LACP on both ends may not negotiate an active bundle, and individual green links do not prove aggregation. Verify the action with: Inspect actor partner system IDs, LACP mode, partner synchronization, port speed, VLAN membership and member counters.
Incorrect Answers
A:Set measured storm-control thresholds for broadcast, multicast or unknown unicast as supported and validate needed discovery protocols. This action is relevant to Storm-control thresholds and broadcast containment, not the controlling requirement in this case. Overaggressive storm control can break DHCP, ARP or group discovery even when physical links remain healthy. The targeted response is: Choose static, active or passive LACP trunk behavior consistently between peers and verify member aggregation.
B: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: Choose static, active or passive LACP trunk behavior consistently between peers and verify member aggregation.
D:Use FortiLink split-interface or standby interfaces only for supported topology and verify active versus backup port behavior. This action is relevant to FortiLink split-interface and standby path design, not the controlling requirement in this case. FortiLink split-interface behavior depends on topology; enabling it blindly for same-peer LAG links can break intended aggregation. The targeted response is: Choose static, active or passive LACP trunk behavior consistently between peers and verify member aggregation.
Question 282
An office printer sends DHCP Discover repeatedly but never sees an Offer after a trust-boundary change. Which diagnostic evidence should the FortiSwitch administrator examine FIRST?
- Inspect Discover/Offer/Request/Ack sequence, ARP requests/replies, VLAN tags, DHCP snooping and DAI counters.
- Review filter minimization, capture duration, administrator authorization, sensitive payloads and evidence-sharing restrictions.
- Inspect SVI admin state, VLAN membership, address and mask, connected route, ARP and intended upstream gateway.
- Verify mirror connection, FortiGate sniffing interface, capture expression, expected VLAN tags and packet direction.
Explanation
Correct Answer
A:Inspect Discover/Offer/Request/Ack sequence, ARP requests/replies, VLAN tags, DHCP snooping and DAI counters. A DHCP lease failure can originate at the client, switch, relay or server; capturing at one side alone is not always conclusive. The paired action is: Trace DHCP and ARP exchanges at ingress and uplink to distinguish missing requests from blocked or malformed responses.
Incorrect Answers
B:Review filter minimization, capture duration, administrator authorization, sensitive payloads and evidence-sharing restrictions. These observations are applicable to Capture and confidentiality limits in incident response, but would not isolate the main failure first. The decisive evidence is: Inspect Discover/Offer/Request/Ack sequence, ARP requests/replies, VLAN tags, DHCP snooping and DAI counters.
C: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 Discover/Offer/Request/Ack sequence, ARP requests/replies, VLAN tags, DHCP snooping and DAI counters.
D: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: Inspect Discover/Offer/Request/Ack sequence, ARP requests/replies, VLAN tags, DHCP snooping and DAI counters.
Question 283
A school lab asks for device isolation yet only adds a policy between VLANs, leaving same-VLAN peers connected. Which TWO complementary steps identify the appropriate FortiSwitch response AND the evidence needed to verify it? Select TWO.
- Use supported intra-VLAN traffic controls when clients in the same broadcast domain must not communicate directly.
- Inspect MAC table usage, configured learning limit, learned device count, port-security event and violation action.
- Exactly the intended serial joins managed inventory and receives approved controller settings after authorization.
- Attach an approved port-security or switch-security profile to the correct FortiSwitch access port and verify effective policy precedence.
- Review target VLAN, switch isolation controls, client MAC table, permitted gateway path and peer-to-peer test.
Explanation
Correct Answers
A: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. This is the configuration or remediation half of the requested TWO-step pair.
E:Review target VLAN, switch isolation controls, client MAC table, permitted gateway path and peer-to-peer test. Routing-level firewall rules may not inspect local Layer-2 forwarding unless intra-VLAN isolation is configured. The paired action is: Use supported intra-VLAN traffic controls when clients in the same broadcast domain must not communicate directly. This is the diagnostic or verification half of the requested TWO-step pair.
Incorrect Answers
B:Inspect MAC table usage, configured learning limit, learned device count, port-security event and violation action. This step concerns Port MAC learning-limit and violation controls and is not part of the required paired solution. The correct action and evidence are: Use supported intra-VLAN traffic controls when clients in the same broadcast domain must not communicate directly. Together with: Review target VLAN, switch isolation controls, client MAC table, permitted gateway path and peer-to-peer test.
C:Exactly the intended serial joins managed inventory and receives approved controller settings after authorization. This step concerns Discovered versus authorized FortiSwitch state and is not part of the required paired solution. The correct action and evidence are: Use supported intra-VLAN traffic controls when clients in the same broadcast domain must not communicate directly. Together with: Review target VLAN, switch isolation controls, client MAC table, permitted gateway path and peer-to-peer test.
D:Attach an approved port-security or switch-security profile to the correct FortiSwitch access port and verify effective policy precedence. This step concerns FortiSwitch security profile application and precedence and is not part of the required paired solution. The correct action and evidence are: Use supported intra-VLAN traffic controls when clients in the same broadcast domain must not communicate directly. Together with: Review target VLAN, switch isolation controls, client MAC table, permitted gateway path and peer-to-peer test.
Question 284
MAC addresses oscillate between two uplinks after a newly installed unmanaged bridge creates a loop. Which FortiSwitch configuration or corrective action BEST addresses the requirement?
- Check MAC-learning table and flooding behavior before replacing a switch or changing its IP routing.
- Use STP state and MAC move evidence to isolate one bad bridging path and change only the proven element.
- Configure supported FortiSwitch MCLAG peer groups and peer links before connecting downstream redundant bundles.
- Document tenant-specific impact, current switch state and reversal steps before changing shared FortiLink VLAN/port mappings.
Explanation
Correct Answer
A:Check MAC-learning table and flooding behavior before replacing a switch or changing its IP routing. An L2 switch uses MAC destination and VLAN state for forwarding; a healthy SVI is not proof a host is on the proper port. Verify the action with: Inspect source MAC entries by VLAN, ingress/egress port, address aging, LAG membership and broadcast counters.
Incorrect Answers
B:Use STP state and MAC move evidence to isolate one bad bridging path and change only the proven element. This action is relevant to STP incident recovery with MAC flap evidence, not the controlling requirement in this case. Packet loss during a bridging loop can coexist with clean optical counters, so L1-only diagnostics miss the root cause. The targeted response is: Check MAC-learning table and flooding behavior before replacing a switch or changing its IP routing.
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: Check MAC-learning table and flooding behavior before replacing a switch or changing its IP routing.
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: Check MAC-learning table and flooding behavior before replacing a switch or changing its IP routing.
Question 285
An access switch accidentally becomes root because its bridge priority is lower than planned core devices. Which observable result BEST proves the intended FortiSwitch operation or security policy works?
- Only approved DHCP servers issue leases and the assigned endpoint identity or location remains traceable.
- A planned alternate link remains blocked and takes over predictably without a broadcast storm.
- The impacted client can communicate on the permitted VLAN while unrelated tenant or guest VLANs remain separated.
- Every relevant VLAN converges without loops and redundant paths unblock only when needed.
Explanation
Correct Answer
B:A planned alternate link remains blocked and takes over predictably without a broadcast storm. Different MST configuration identifiers split regions even if switch ports are physically connected.
Incorrect Answers
A:Only approved DHCP servers issue leases and the assigned endpoint identity or location remains traceable. This result relates to DHCP server allowlist and Option 82 validation, not the acceptance condition under test. The relevant result is: A planned alternate link remains blocked and takes over predictably without a broadcast storm.
C:The impacted client can communicate on the permitted VLAN while unrelated tenant or guest VLANs remain separated. This result relates to VLAN access isolation and troubleshooting of membership, not the acceptance condition under test. The relevant result is: A planned alternate link remains blocked and takes over predictably without a broadcast storm.
D:Every relevant VLAN converges without loops and redundant paths unblock only when needed. This result relates to RPVST and supported STP mode interoperability, not the acceptance condition under test. The relevant result is: A planned alternate link remains blocked and takes over predictably without a broadcast storm.
Question 286
A security role policy rejects sessions after a RADIUS change but no one examines switch authentication events. Which diagnostic evidence should the FortiSwitch administrator examine FIRST?
- Inspect controller switch list, interface events, authentication logs, current configuration, timestamps and recent change history.
- Review FortiGate/FortiSwitch version matrix, upgrade logs, auto-authorize state, synchronization events, switch restart and rollback image.
- Check switch serial, active software version, current synchronized configuration, backup timestamp, integrity and recovery permissions.
- Review spanning-tree topology-change count, MAC instability, BPDU logs, port errors and recent cabling changes.
Explanation
Correct Answer
A:Inspect controller switch list, interface events, authentication logs, current configuration, timestamps and recent change history. A log message without source device, time and relevant state is not adequate to prove root cause. The paired action is: Collect relevant FortiSwitch controller diagnostics, switch system events and targeted status output before making configuration changes.
Incorrect Answers
B:Review FortiGate/FortiSwitch version matrix, upgrade logs, auto-authorize state, synchronization events, switch restart and rollback image. These observations are applicable to FortiLink synchronization and upgrade troubleshooting, but would not isolate the main failure first. The decisive evidence is: Inspect controller switch list, interface events, authentication logs, current configuration, timestamps and recent change history.
C:Check switch serial, active software version, current synchronized configuration, backup timestamp, integrity and recovery permissions. These observations are applicable to Config backup and firmware inventory evidence, but would not isolate the main failure first. The decisive evidence is: Inspect controller switch list, interface events, authentication logs, current configuration, timestamps and recent change history.
D:Review spanning-tree topology-change count, MAC instability, BPDU logs, port errors and recent cabling changes. These observations are applicable to STP incident recovery with MAC flap evidence, but would not isolate the main failure first. The decisive evidence is: Inspect controller switch list, interface events, authentication logs, current configuration, timestamps and recent change history.
Question 287
The receive optical power is below specification and the team keeps modifying VLANs instead of fixing fiber attenuation. Which observable result BEST proves the intended FortiSwitch operation or security policy works?
- Rapid MAC moves stop and normal forwarding returns with a verified alternate redundant path.
- The correct link establishes at expected negotiated rate without recurring loss-of-signal or CRC errors.
- The exact dropped direction or incorrect address binding is evidenced before changing a security feature.
- Voice packets receive intended treatment without allowing arbitrary untrusted hosts to claim top priority.
Explanation
Correct Answer
B:The correct link establishes at expected negotiated rate without recurring loss-of-signal or CRC errors. This is a measurable client, control-plane, or security outcome rather than a claim that configuration was entered. Matching a mechanical optic cage is insufficient to prove optical or firmware compatibility.
Incorrect Answers
A:Rapid MAC moves stop and normal forwarding returns with a verified alternate redundant path. This result relates to STP incident recovery with MAC flap evidence, not the acceptance condition under test. The relevant result is: The correct link establishes at expected negotiated rate without recurring loss-of-signal or CRC errors.
C:The exact dropped direction or incorrect address binding is evidenced before changing a security feature. This result relates to Capture-based DHCP and ARP path isolation, not the acceptance condition under test. The relevant result is: The correct link establishes at expected negotiated rate without recurring loss-of-signal or CRC errors.
D:Voice packets receive intended treatment without allowing arbitrary untrusted hosts to claim top priority. This result relates to QoS ingress classification and trust boundaries, not the acceptance condition under test. The relevant result is: The correct link establishes at expected negotiated rate without recurring loss-of-signal or CRC errors.
Question 288
A new staff VLAN exists on FortiGate but nobody has assigned it to access ports on the managed switch. Which observable result BEST proves the intended FortiSwitch operation or security policy works?
- An access host receives the right subnet while only approved tagged VLANs traverse the uplink.
- The handset and attached workstation use the intended separate networks and retain their authorized access.
- The user VLAN reaches the authorized gateway without being placed on an unrelated physical FortiGate interface.
- The suspect device is restricted without interrupting unrelated tenants and can be restored after review.
Explanation
Correct Answer
C:The user VLAN reaches the authorized gateway without being placed on an unrelated physical FortiGate interface. A named VLAN in FortiOS is not proof its switch-port membership and L3 policy are correct.
Incorrect Answers
A: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: The user VLAN reaches the authorized gateway without being placed on an unrelated physical FortiGate interface.
B: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: The user VLAN reaches the authorized gateway without being placed on an unrelated physical FortiGate interface.
D:The suspect device is restricted without interrupting unrelated tenants and can be restored after review. This result relates to VLAN security policy and quarantine actions, not the acceptance condition under test. The relevant result is: The user VLAN reaches the authorized gateway without being placed on an unrelated physical FortiGate interface.
Question 289
Two remote sites share overlapping prefixes and a broad static route inadvertently sends traffic to the wrong location. Which TWO complementary steps identify the appropriate FortiSwitch response AND the evidence needed to verify it? Select TWO.
- Inspect local mode, per-VLAN bridge ID, peer BPDUs, port state, timers and topology-change history.
- The analyzer receives the intended copies while production forwarding remains unchanged.
- Set a supported default route or precise static prefix toward a reachable next hop and validate return traffic.
- Check route table, next-hop ARP, ingress VLAN, egress interface, prefix length and return-route path.
- Configure supported switch virtual interfaces and routed gateway addresses with correct VLAN, subnet and management context.
Explanation
Correct Answers
C:Set a supported default route or precise static prefix toward a reachable next hop and validate return traffic. A default route cannot repair local VLAN tagging or a missing neighbor resolution condition. Verify the action with: Check route table, next-hop ARP, ingress VLAN, egress interface, prefix length and return-route path. This is the configuration or remediation half of the requested TWO-step pair.
D: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. This is the diagnostic or verification half of the requested TWO-step pair.
Incorrect Answers
A:Inspect local mode, per-VLAN bridge ID, peer BPDUs, port state, timers and topology-change history. This step concerns RPVST and supported STP mode interoperability and is not part of the required paired solution. The correct action and evidence are: Set a supported default route or precise static prefix toward a reachable next hop and validate return traffic. Together with: Check route table, next-hop ARP, ingress VLAN, egress interface, prefix length and return-route path.
B:The analyzer receives the intended copies while production forwarding remains unchanged. This step concerns FortiSwitch port mirroring to network analyzer and is not part of the required paired solution. The correct action and evidence are: Set a supported default route or precise static prefix toward a reachable next hop and validate return traffic. Together with: Check route table, next-hop ARP, ingress VLAN, egress interface, prefix length and return-route path.
E:Configure supported switch virtual interfaces and routed gateway addresses with correct VLAN, subnet and management context. This step concerns FortiSwitch SVI routing and connected routes and is not part of the required paired solution. The correct action and evidence are: Set a supported default route or precise static prefix toward a reachable next hop and validate return traffic. Together with: Check route table, next-hop ARP, ingress VLAN, egress interface, prefix length and return-route path.
Question 290
A security team sends a DACL for an unauthenticated session and assumes the switch applied its hardware entries. Which TWO complementary steps identify the appropriate FortiSwitch response AND the evidence needed to verify it? Select TWO.
- Enable IPv4 source guard on supported switch interfaces only with appropriate DHCP snooping or static bindings.
- The failing physical or logical port is identified through reproducible counters rather than visual LED assumptions.
- Verify that supported CoA or dynamic user security profiles are enforced on authenticated sessions under the deployed topology.
- Review RADIUS Access-Accept attributes, CoA path, session identifier, switch port role, DACL installation and packet test.
- Inspect trusted-port state, Discover/Offer path, DHCP binding table, VLAN and counters for dropped offers.
Explanation
Correct Answers
C: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. This is the configuration or remediation half of the requested TWO-step pair.
D:Review RADIUS Access-Accept attributes, CoA path, session identifier, switch port role, DACL installation and packet test. RADIUS authentication success is not proof that a downloadable ACL or CoA update was enforced; some modes have documented conditions. The paired action is: Verify that supported CoA or dynamic user security profiles are enforced on authenticated sessions under the deployed topology. This is the diagnostic or verification half of the requested TWO-step pair.
Incorrect Answers
A:Enable IPv4 source guard on supported switch interfaces only with appropriate DHCP snooping or static bindings. This step concerns IPv4 source guard and binding-based packet filtering and is not part of the required paired solution. The correct action and evidence are: Verify that supported CoA or dynamic user security profiles are enforced on authenticated sessions under the deployed topology. Together with: Review RADIUS Access-Accept attributes, CoA path, session identifier, switch port role, DACL installation and packet test.
B:The failing physical or logical port is identified through reproducible counters rather than visual LED assumptions. This step concerns Managed switch port statistics and counter analysis and is not part of the required paired solution. The correct action and evidence are: Verify that supported CoA or dynamic user security profiles are enforced on authenticated sessions under the deployed topology. Together with: Review RADIUS Access-Accept attributes, CoA path, session identifier, switch port role, DACL installation and packet test.
E:Inspect trusted-port state, Discover/Offer path, DHCP binding table, VLAN and counters for dropped offers. This step concerns DHCP snooping trust-boundary enforcement and is not part of the required paired solution. The correct action and evidence are: Verify that supported CoA or dynamic user security profiles are enforced on authenticated sessions under the deployed topology. Together with: Review RADIUS Access-Accept attributes, CoA path, session identifier, switch port role, DACL installation and packet test.