Fortinet NSE5_FSW_AD-7.6 Practice Test 67
Question 660
An administrator raises MAC limits on every port instead of diagnosing one device creating random source addresses. Which diagnostic evidence should the FortiSwitch administrator examine FIRST?
- Inspect MAC table usage, configured learning limit, learned device count, port-security event and violation action.
- Inspect supplicant EAP exchange, RADIUS reachability, shared secret, port policy, authentication result and assigned access profile.
- Review RADIUS Access-Accept attributes, CoA path, session identifier, switch port role, DACL installation and packet test.
- Review spanning-tree topology-change count, MAC instability, BPDU logs, port errors and recent cabling changes.
Explanation
Correct Answer
A:Inspect MAC table usage, configured learning limit, learned device count, port-security event and violation action. Dynamic MAC learning limits reduce accidental fan-out but should be tuned for legitimate multi-device access designs. The paired action is: Set model-supported dynamic MAC address learning limits and specific violation action on access-facing switch ports.
Incorrect Answers
B:Inspect supplicant EAP exchange, RADIUS reachability, shared secret, port policy, authentication result and assigned access profile. These observations are applicable to FortiSwitch 802.1X port-based authentication, but would not isolate the main failure first. The decisive evidence is: Inspect MAC table usage, configured learning limit, learned device count, port-security event and violation action.
C: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 MAC table usage, configured learning limit, learned device count, port-security event and violation action.
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 MAC table usage, configured learning limit, learned device count, port-security event and violation action.
Question 661
A guest laptop marks all packets EF and monopolizes a priority queue on a shared access port. Which FortiSwitch configuration or corrective action BEST addresses the requirement?
- Apply supported egress CoS queue policy to reduce latency under congestion without starving other required traffic.
- Define appropriate trusted ingress marking sources and classify untrusted frames before choosing egress queues.
- Create a bounded packet-capture profile on the right switch interface with a narrow filter, then start/stop and inspect frames.
- Determine whether a switch is managed by FortiGate or standalone before setting interfaces, routes or admin policies.
Explanation
Correct Answer
B:Define appropriate trusted ingress marking sources and classify untrusted frames before choosing egress queues. A packet marking has no useful QoS effect until supported classification and scheduling map it consistently. Verify the action with: Inspect incoming 802.1p and DSCP markings, trust mode, QoS map, physical port and classification counters.
Incorrect Answers
A: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: Define appropriate trusted ingress marking sources and classify untrusted frames before choosing egress queues.
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: Define appropriate trusted ingress marking sources and classify untrusted frames before choosing egress queues.
D: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: Define appropriate trusted ingress marking sources and classify untrusted frames before choosing egress queues.
Question 662
A contractor creates an unapproved second ring path, then calls every STP blocked port an outage. Which TWO complementary steps identify the appropriate FortiSwitch response AND the evidence needed to verify it? Select TWO.
- Compare desired switch controller settings, switch synchronization indicators, port VLANs, user roles and post-reboot configuration.
- Check managed tree, ISL link health, model compatibility, VLAN carriage, depth limitations and upstream aggregate status.
- Build a documented supported FortiSwitch daisy chain or multi-tier topology with adequate ISL uplink capacity and safeguards.
- Create an appropriate FortiGate FortiLink physical or logical interface with supported addressing and controller capabilities before onboarding a switch.
- Only intended traffic is accepted or rejected at the switch while allowed application sessions remain functional.
Explanation
Correct Answers
B:Check managed tree, ISL link health, model compatibility, VLAN carriage, depth limitations and upstream aggregate status. A FortiGate controls each FortiSwitch through the managed Layer-2 topology, but downstream reachability depends on upstream FortiLink links. The paired action is: Build a documented supported FortiSwitch daisy chain or multi-tier topology with adequate ISL uplink capacity and safeguards. This is the diagnostic or verification half of the requested TWO-step pair.
C:Build a documented supported FortiSwitch daisy chain or multi-tier topology with adequate ISL uplink capacity and safeguards. A FortiGate controls each FortiSwitch through the managed Layer-2 topology, but downstream reachability depends on upstream FortiLink links. Verify the action with: Check managed tree, ISL link health, model compatibility, VLAN carriage, depth limitations and upstream aggregate status. This is the configuration or remediation half of the requested TWO-step pair.
Incorrect Answers
A:Compare desired switch controller settings, switch synchronization indicators, port VLANs, user roles and post-reboot configuration. This step concerns Managed switch configuration synchronization and is not part of the required paired solution. The correct action and evidence are: Build a documented supported FortiSwitch daisy chain or multi-tier topology with adequate ISL uplink capacity and safeguards. Together with: Check managed tree, ISL link health, model compatibility, VLAN carriage, depth limitations and upstream aggregate status.
D:Create an appropriate FortiGate FortiLink physical or logical interface with supported addressing and controller capabilities before onboarding a switch. This step concerns FortiLink management interface provisioning and is not part of the required paired solution. The correct action and evidence are: Build a documented supported FortiSwitch daisy chain or multi-tier topology with adequate ISL uplink capacity and safeguards. Together with: Check managed tree, ISL link health, model compatibility, VLAN carriage, depth limitations and upstream aggregate status.
E:Only intended traffic is accepted or rejected at the switch while allowed application sessions remain functional. This step concerns Static port ACL forwarding decisions and is not part of the required paired solution. The correct action and evidence are: Build a documented supported FortiSwitch daisy chain or multi-tier topology with adequate ISL uplink capacity and safeguards. Together with: Check managed tree, ISL link health, model compatibility, VLAN carriage, depth limitations and upstream aggregate status.
Question 663
A staff laptop fails EAP-TLS because its certificate chain differs from the identity-server trust store. Which FortiSwitch configuration or corrective action BEST addresses the requirement?
- Identify FortiLink failures caused by split-interface, HA, MCLAG peer or ISL mismatches before changing unrelated ports.
- Configure supported IEEE 802.1X port security against an approved RADIUS service with explicit guest/unauthorized behavior.
- Use supported intra-VLAN traffic controls when clients in the same broadcast domain must not communicate directly.
- Set model-supported dynamic MAC address learning limits and specific violation action on access-facing switch ports.
Explanation
Correct Answer
B:Configure supported IEEE 802.1X port security against an approved RADIUS service with explicit guest/unauthorized behavior. A physical link can be up while 802.1X blocks traffic; the switch is the authenticator, not the authentication server. Verify the action with: Inspect supplicant EAP exchange, RADIUS reachability, shared secret, port policy, authentication result and assigned access profile.
Incorrect Answers
A:Identify FortiLink failures caused by split-interface, HA, MCLAG peer or ISL mismatches before changing unrelated ports. This action is relevant to FortiLink HA and MCLAG topology faults, not the controlling requirement in this case. FortiGate HA, FortiLink split-interface and FortiSwitch MCLAG have distinct failover behaviors that cannot be inferred from link LEDs alone. The targeted response is: Configure supported IEEE 802.1X port security against an approved RADIUS service with explicit guest/unauthorized behavior.
C:Use supported intra-VLAN traffic controls when clients in the same broadcast domain must not communicate directly. This action is relevant to Intra-VLAN blocking and isolation boundaries, not the controlling requirement in this case. Routing-level firewall rules may not inspect local Layer-2 forwarding unless intra-VLAN isolation is configured. The targeted response is: Configure supported IEEE 802.1X port security against an approved RADIUS service with explicit guest/unauthorized behavior.
D: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: Configure supported IEEE 802.1X port security against an approved RADIUS service with explicit guest/unauthorized behavior.
Question 664
A managed FortiSwitch learns an unauthorized DHCP server from a neighboring guest kiosk. Which FortiSwitch configuration or corrective action BEST addresses the requirement?
- Enable supported DHCP snooping on client VLANs and trust only known DHCP-server or relay-facing links.
- Use documented trusted DHCP-server lists or Option 82 information where supported to enforce authorized address assignment.
- Prepare supported provisioning, DHCP, management connectivity and secure bootstrap before assuming a factory-default FortiSwitch will auto-configure.
- Attach an approved port-security or switch-security profile to the correct FortiSwitch access port and verify effective policy precedence.
Explanation
Correct Answer
B:Use documented trusted DHCP-server lists or Option 82 information where supported to enforce authorized address assignment. DHCP server allowlist and Option 82 metadata provide additional context but cannot correct a failed VLAN or missing upstream relay. Verify the action with: Inspect DHCP server permitted list, Option 82 insertion/trust state, relay path, client bindings and lease evidence.
Incorrect Answers
A:Enable supported DHCP snooping on client VLANs and trust only known DHCP-server or relay-facing links. This action is relevant to DHCP snooping trust-boundary enforcement, not the controlling requirement in this case. Trusting every port defeats DHCP snooping and wrongly distrusting the server uplink may suppress all leases. The targeted response is: Use documented trusted DHCP-server lists or Option 82 information where supported to enforce authorized address assignment.
C:Prepare supported provisioning, DHCP, management connectivity and secure bootstrap before assuming a factory-default FortiSwitch will auto-configure. This action is relevant to Zero-touch provisioning and controller dependency checks, not the controlling requirement in this case. Zero-touch deployment works only when the necessary discovery path and identity checks function; a link LED is insufficient. The targeted response is: Use documented trusted DHCP-server lists or Option 82 information where supported to enforce authorized address assignment.
D:Attach an approved port-security or switch-security profile to the correct FortiSwitch access port and verify effective policy precedence. This action is relevant to FortiSwitch security profile application and precedence, not the controlling requirement in this case. A named security profile sitting in configuration is not proof that it was applied to the intended hardware port. The targeted response is: Use documented trusted DHCP-server lists or Option 82 information where supported to enforce authorized address assignment.
Question 665
A team interprets seeing a DHCP Discover at the mirror as proof the server's Offer reached the requesting access port. Which diagnostic evidence should the FortiSwitch administrator examine FIRST?
- Verify mirror connection, FortiGate sniffing interface, capture expression, expected VLAN tags and packet direction.
- Inspect FortiGate FortiLink status, supported discovery port, LLDP frames, interface IP, link errors and switch serial.
- Inspect device fingerprint, policy rule order, assigned VLAN, security profile, client identity and enforcement state.
- Review FortiGate/FortiSwitch version matrix, upgrade logs, auto-authorize state, synchronization events, switch restart and rollback image.
Explanation
Correct Answer
A:Verify mirror connection, FortiGate sniffing interface, capture expression, expected VLAN tags and packet direction. Sniffer placement determines visibility; absence of a packet at one observation point does not prove no packet existed elsewhere. The paired action is: Use a supported FortiGate one-arm sniffer or mirrored ingress path to inspect switch traffic where permitted.
Incorrect Answers
B:Inspect FortiGate FortiLink status, supported discovery port, LLDP frames, interface IP, link errors and switch serial. These observations are applicable to FortiLink discovery failure and physical uplink path, but would not isolate the main failure first. The decisive evidence is: Verify mirror connection, FortiGate sniffing interface, capture expression, expected VLAN tags and packet direction.
C:Inspect device fingerprint, policy rule order, assigned VLAN, security profile, client identity and enforcement state. These observations are applicable to NAC dynamic port policy device classification, but would not isolate the main failure first. The decisive evidence is: Verify mirror connection, FortiGate sniffing interface, capture expression, expected VLAN tags and packet direction.
D: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: Verify mirror connection, FortiGate sniffing interface, capture expression, expected VLAN tags and packet direction.
Question 666
A standalone FortiSwitch has local management access but cannot reach its NTP server off-subnet. 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.
- Legitimate clients lease addresses while rogue DHCP servers connected to untrusted access ports cannot answer.
- The impacted client can communicate on the permitted VLAN while unrelated tenant or guest VLANs remain separated.
- Only intended networks are reachable through the configured route and the return path remains valid.
Explanation
Correct Answer
D:Only intended networks are reachable through the configured route and the return path remains valid. A default route cannot repair local VLAN tagging or a missing neighbor resolution condition.
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: Only intended networks are reachable through the configured route and the return path remains valid.
B: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: Only intended networks are reachable through the configured route and the return path remains valid.
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: Only intended networks are reachable through the configured route and the return path remains valid.
Question 667
An administrator raises MAC limits on every port instead of diagnosing one device creating random source addresses. Which TWO complementary steps identify the appropriate FortiSwitch response AND the evidence needed to verify it? Select TWO.
- Set model-supported dynamic MAC address learning limits and specific violation action on access-facing switch ports.
- Inspect MAC table usage, configured learning limit, learned device count, port-security event and violation action.
- Review ACL direction and attachment, permit/drop rules, hit counters, supported match fields and resulting packet path.
- Configure supported IEEE 802.1X port security against an approved RADIUS service with explicit guest/unauthorized behavior.
- A capable handset reports the expected voice network policy and traffic uses the correct VLAN.
Explanation
Correct Answers
A: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. This is the configuration or remediation half of the requested TWO-step pair.
B:Inspect MAC table usage, configured learning limit, learned device count, port-security event and violation action. Dynamic MAC learning limits reduce accidental fan-out but should be tuned for legitimate multi-device access designs. The paired action is: Set model-supported dynamic MAC address learning limits and specific violation action on access-facing switch ports. This is the diagnostic or verification half of the requested TWO-step pair.
Incorrect Answers
C:Review ACL direction and attachment, permit/drop rules, hit counters, supported match fields and resulting packet path. This step concerns Static port ACL forwarding decisions and is not part of the required paired solution. The correct action and evidence are: Set model-supported dynamic MAC address learning limits and specific violation action on access-facing switch ports. Together with: Inspect MAC table usage, configured learning limit, learned device count, port-security event and violation action.
D:Configure supported IEEE 802.1X port security against an approved RADIUS service with explicit guest/unauthorized behavior. This step concerns FortiSwitch 802.1X port-based authentication and is not part of the required paired solution. The correct action and evidence are: Set model-supported dynamic MAC address learning limits and specific violation action on access-facing switch ports. Together with: Inspect MAC table usage, configured learning limit, learned device count, port-security event and violation action.
E:A capable handset reports the expected voice network policy and traffic uses the correct VLAN. This step concerns LLDP-MED voice network policy advertisements and is not part of the required paired solution. The correct action and evidence are: Set model-supported dynamic MAC address learning limits and specific violation action on access-facing switch ports. Together with: Inspect MAC table usage, configured learning limit, learned device count, port-security event and violation action.
Question 668
A branch's FortiLink interface has no route or reachable controller IP and the managed switch never appears. Which observable result BEST proves the intended FortiSwitch operation or security policy works?
- Exactly the intended serial joins managed inventory and receives approved controller settings after authorization.
- All expected child interfaces enumerate at supported speeds without disrupting unrelated uplinks.
- All subtending managed switches remain discoverable and user service survives expected single-link failures where supported.
- The new FortiSwitch discovers the designated controller while unrelated FortiGate interfaces retain their normal function.
Explanation
Correct Answer
D:The new FortiSwitch discovers the designated controller while unrelated FortiGate interfaces retain their normal function. A FortiGate port not configured for FortiLink cannot assume managed-switch ownership from physical connection alone.
Incorrect Answers
A: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 new FortiSwitch discovers the designated controller while unrelated FortiGate interfaces retain their normal function.
B:All expected child interfaces enumerate at supported speeds without disrupting unrelated uplinks. This result relates to FortiSwitch split port breakout mode, not the acceptance condition under test. The relevant result is: The new FortiSwitch discovers the designated controller while unrelated FortiGate interfaces retain their normal function.
C:All subtending managed switches remain discoverable and user service survives expected single-link failures where supported. This result relates to FortiSwitch multi-tier managed topology, not the acceptance condition under test. The relevant result is: The new FortiSwitch discovers the designated controller while unrelated FortiGate interfaces retain their normal function.
Question 669
Two aggregation switches have two uplinks to an access device but lack a configured FortiSwitch MCLAG pair. Which FortiSwitch configuration or corrective action BEST addresses the requirement?
- Build a documented supported FortiSwitch daisy chain or multi-tier topology with adequate ISL uplink capacity and safeguards.
- Use FortiLink split-interface or standby interfaces only for supported topology and verify active versus backup port behavior.
- Choose supported FortiSwitchOS version and maintenance workflow compatible with the FortiGate version and topology.
- Use documented peer-group and downstream trunk configuration for MCLAG rather than creating ad hoc parallel Ethernet links.
Explanation
Correct Answer
D: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.
Incorrect Answers
A: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 documented peer-group and downstream trunk configuration for MCLAG rather than creating ad hoc parallel Ethernet links.
B: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: Use documented peer-group and downstream trunk configuration for MCLAG rather than creating ad hoc parallel Ethernet links.
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: Use documented peer-group and downstream trunk configuration for MCLAG rather than creating ad hoc parallel Ethernet links.
Question 670
A FortiGate template updates native VLANs but a switch shows an outdated port mapping after synchronization. Which observable result BEST proves the intended FortiSwitch operation or security policy works?
- The handset and attached workstation use the intended separate networks and retain their authorized access.
- The suspect device is restricted without interrupting unrelated tenants and can be restored after review.
- The intended VLAN survives a switch restart without unexpected controller overwrite or unauthorized local change.
- A rogue root candidate is blocked or a looped path remains safely contained without wiping all STP configuration.
Explanation
Correct Answer
C:The intended VLAN survives a switch restart without unexpected controller overwrite or unauthorized local change. Directly editing a FortiLink-managed switch can cause drift because FortiGate remains the controller of record.
Incorrect Answers
A:The handset and attached workstation use the intended separate networks and retain their authorized access. This result relates to Voice and data VLAN separation on shared access ports, not the acceptance condition under test. The relevant result is: The intended VLAN survives a switch restart without unexpected controller overwrite or unauthorized local change.
B: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 intended VLAN survives a switch restart without unexpected controller overwrite or unauthorized local change.
D:A rogue root candidate is blocked or a looped path remains safely contained without wiping all STP configuration. This result relates to Root guard and loop guard failure response, not the acceptance condition under test. The relevant result is: The intended VLAN survives a switch restart without unexpected controller overwrite or unauthorized local change.