Fortinet NSE5_FSW_AD-7.6 Practice Test 36
Question 350
A receiver moved to another port stops getting a stream because its membership reports are not observed. Which FortiSwitch configuration or corrective action BEST addresses the requirement?
- Configure supported FortiSwitch MCLAG peer groups and peer links before connecting downstream redundant bundles.
- Configure supported IGMP snooping and querier expectations to forward multicast only where receivers request it.
- Use STP state and MAC move evidence to isolate one bad bridging path and change only the proven element.
- Prepare supported provisioning, DHCP, management connectivity and secure bootstrap before assuming a factory-default FortiSwitch will auto-configure.
Explanation
Correct Answer
B:Configure supported IGMP snooping and querier expectations to forward multicast only where receivers request it. A multicast VLAN alone does not indicate that IGMP receiver membership or querier operation is healthy. Verify the action with: Check group membership table, querier identity, IGMP report traffic, VLAN and target egress port.
Incorrect Answers
A: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: Configure supported IGMP snooping and querier expectations to forward multicast only where receivers request it.
C: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: Configure supported IGMP snooping and querier expectations to forward multicast only where receivers request it.
D: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: Configure supported IGMP snooping and querier expectations to forward multicast only where receivers request it.
Question 351
A guest laptop marks all packets EF and monopolizes a priority queue on a shared access port. Which TWO complementary steps identify the appropriate FortiSwitch response AND the evidence needed to verify it? Select TWO.
- Configure supported LLDP-MED voice policy so a compatible handset learns its VLAN and traffic priority.
- Define appropriate trusted ingress marking sources and classify untrusted frames before choosing egress queues.
- Inspect incoming 802.1p and DSCP markings, trust mode, QoS map, physical port and classification counters.
- Check switch PoE budget, port class, negotiated allocation, PSU state, LLDP-MED power TLV and port events.
- Only intended traffic is accepted or rejected at the switch while allowed application sessions remain functional.
Explanation
Correct Answers
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. This is the configuration or remediation half of the requested TWO-step pair.
C:Inspect incoming 802.1p and DSCP markings, trust mode, QoS map, physical port and classification counters. A packet marking has no useful QoS effect until supported classification and scheduling map it consistently. The paired action is: Define appropriate trusted ingress marking sources and classify untrusted frames before choosing egress queues. This is the diagnostic or verification half of the requested TWO-step pair.
Incorrect Answers
A:Configure supported LLDP-MED voice policy so a compatible handset learns its VLAN and traffic priority. This step concerns LLDP-MED voice network policy advertisements and is not part of the required paired solution. The correct action and evidence are: Define appropriate trusted ingress marking sources and classify untrusted frames before choosing egress queues. Together with: Inspect incoming 802.1p and DSCP markings, trust mode, QoS map, physical port and classification counters.
D:Check switch PoE budget, port class, negotiated allocation, PSU state, LLDP-MED power TLV and port events. This step concerns PoE and LLDP-MED endpoint power coordination and is not part of the required paired solution. The correct action and evidence are: Define appropriate trusted ingress marking sources and classify untrusted frames before choosing egress queues. Together with: Inspect incoming 802.1p and DSCP markings, trust mode, QoS map, physical port and classification counters.
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: Define appropriate trusted ingress marking sources and classify untrusted frames before choosing egress queues. Together with: Inspect incoming 802.1p and DSCP markings, trust mode, QoS map, physical port and classification counters.
Question 352
A dynamic port-policy rule intended for printers matches all newly connected laptops due to a broad condition. Which diagnostic evidence should the FortiSwitch administrator examine FIRST?
- Inspect supported topology, FortiLink p2p settings, TPID, transport reachability, discovery frames and switch firmware.
- Inspect DHCP server permitted list, Option 82 insertion/trust state, relay path, client bindings and lease evidence.
- Inspect device fingerprint, policy rule order, assigned VLAN, security profile, client identity and enforcement state.
- Inspect trusted-port state, Discover/Offer path, DHCP binding table, VLAN and counters for dropped offers.
Explanation
Correct Answer
C:Inspect device fingerprint, policy rule order, assigned VLAN, security profile, client identity and enforcement state. NAC assignment relies on reliable detection and a defined precedence; a class label is not a substitute for switch-port policy. The paired action is: Apply authorized device-class rules and dynamic port policies after confirming device detection evidence and fallback outcomes.
Incorrect Answers
A:Inspect supported topology, FortiLink p2p settings, TPID, transport reachability, discovery frames and switch firmware. These observations are applicable to FortiLink transport over nontrivial L2 or L3 paths, but would not isolate the main failure first. The decisive evidence is: Inspect device fingerprint, policy rule order, assigned VLAN, security profile, client identity and enforcement state.
B:Inspect DHCP server permitted list, Option 82 insertion/trust state, relay path, client bindings and lease evidence. These observations are applicable to DHCP server allowlist and Option 82 validation, but would not isolate the main failure first. The decisive evidence is: Inspect device fingerprint, policy rule order, assigned VLAN, security profile, client identity and enforcement state.
D:Inspect trusted-port state, Discover/Offer path, DHCP binding table, VLAN and counters for dropped offers. These observations are applicable to DHCP snooping trust-boundary enforcement, but would not isolate the main failure first. The decisive evidence is: Inspect device fingerprint, policy rule order, assigned VLAN, security profile, client identity and enforcement state.
Question 353
An engineer creates a strict policy but never assigns it to the access port hosting sensitive terminals. Which TWO complementary steps identify the appropriate FortiSwitch response AND the evidence needed to verify it? Select TWO.
- Enable supported DHCP snooping on client VLANs and trust only known DHCP-server or relay-facing links.
- Inspect frame-rate counters by class, threshold configuration, affected VLANs and protocol health under controlled load.
- Attach an approved port-security or switch-security profile to the correct FortiSwitch access port and verify effective policy precedence.
- The intended switch appears in discovery after restoring the precise missing interface or transport prerequisite.
- Inspect port profile assignment, FortiGate controller policy, client role, enforcement counters and overlapping static controls.
Explanation
Correct Answers
C:Attach an approved port-security or switch-security profile to the correct FortiSwitch access port and verify effective policy precedence. A named security profile sitting in configuration is not proof that it was applied to the intended hardware port. Verify the action with: Inspect port profile assignment, FortiGate controller policy, client role, enforcement counters and overlapping static controls. This is the configuration or remediation half of the requested TWO-step pair.
E:Inspect port profile assignment, FortiGate controller policy, client role, enforcement counters and overlapping static controls. A named security profile sitting in configuration is not proof that it was applied to the intended hardware port. The paired action is: Attach an approved port-security or switch-security profile to the correct FortiSwitch access port and verify effective policy precedence. This is the diagnostic or verification half of the requested TWO-step pair.
Incorrect Answers
A:Enable supported DHCP snooping on client VLANs and trust only known DHCP-server or relay-facing links. This step concerns DHCP snooping trust-boundary enforcement and is not part of the required paired solution. The correct action and evidence are: Attach an approved port-security or switch-security profile to the correct FortiSwitch access port and verify effective policy precedence. Together with: Inspect port profile assignment, FortiGate controller policy, client role, enforcement counters and overlapping static controls.
B:Inspect frame-rate counters by class, threshold configuration, affected VLANs and protocol health under controlled load. This step concerns Storm-control thresholds and broadcast containment and is not part of the required paired solution. The correct action and evidence are: Attach an approved port-security or switch-security profile to the correct FortiSwitch access port and verify effective policy precedence. Together with: Inspect port profile assignment, FortiGate controller policy, client role, enforcement counters and overlapping static controls.
D:The intended switch appears in discovery after restoring the precise missing interface or transport prerequisite. This step concerns FortiLink discovery failure and physical uplink path and is not part of the required paired solution. The correct action and evidence are: Attach an approved port-security or switch-security profile to the correct FortiSwitch access port and verify effective policy precedence. Together with: Inspect port profile assignment, FortiGate controller policy, client role, enforcement counters and overlapping static controls.
Question 354
A receiver moved to another port stops getting a stream because its membership reports are not observed. Which observable result BEST proves the intended FortiSwitch operation or security policy works?
- Members receive subscribed streams while unsubscribed access ports are not flooded unnecessarily.
- Voice packets receive intended treatment without allowing arbitrary untrusted hosts to claim top priority.
- Critical telephony and wireless endpoints receive continuous intended power without overrunning PSU capacity.
- Known printers and IoT devices enter their restricted VLANs while unknown endpoints have no excessive access.
Explanation
Correct Answer
A:Members receive subscribed streams while unsubscribed access ports are not flooded unnecessarily. A multicast VLAN alone does not indicate that IGMP receiver membership or querier operation is healthy.
Incorrect Answers
B: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: Members receive subscribed streams while unsubscribed access ports are not flooded unnecessarily.
C:Critical telephony and wireless endpoints receive continuous intended power without overrunning PSU capacity. This result relates to Power over Ethernet port controls and budgets, not the acceptance condition under test. The relevant result is: Members receive subscribed streams while unsubscribed access ports are not flooded unnecessarily.
D:Known printers and IoT devices enter their restricted VLANs while unknown endpoints have no excessive access. This result relates to NAC dynamic port policy device classification, not the acceptance condition under test. The relevant result is: Members receive subscribed streams while unsubscribed access ports are not flooded unnecessarily.
Question 355
A team posts complete captures containing authentication tokens into a public support thread. Which diagnostic evidence should the FortiSwitch administrator examine FIRST?
- Inspect hardware SKU, firmware and phy-mode support, breakout cable specification, child port IDs and port restart effect.
- Review filter minimization, capture duration, administrator authorization, sensitive payloads and evidence-sharing restrictions.
- Check switch serial, active software version, current synchronized configuration, backup timestamp, integrity and recovery permissions.
- Inspect FortiGate FortiLink status, supported discovery port, LLDP frames, interface IP, link errors and switch serial.
Explanation
Correct Answer
B:Review filter minimization, capture duration, administrator authorization, sensitive payloads and evidence-sharing restrictions. A packet-capture tool may record payloads and credentials, so evidence handling is part of the network security process. The paired action is: Use narrow capture windows, least-privilege access and approved storage/retention when collecting packet data for diagnostics.
Incorrect Answers
A:Inspect hardware SKU, firmware and phy-mode support, breakout cable specification, child port IDs and port restart effect. These observations are applicable to FortiSwitch split port breakout mode, but would not isolate the main failure first. The decisive evidence is: Review filter minimization, capture duration, administrator authorization, sensitive payloads and evidence-sharing restrictions.
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: Review filter minimization, capture duration, administrator authorization, sensitive payloads and evidence-sharing restrictions.
D: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: Review filter minimization, capture duration, administrator authorization, sensitive payloads and evidence-sharing restrictions.
Question 356
An engineer enables point-to-point FortiLink on one side of a bridge but not on the peer. Which TWO complementary steps identify the appropriate FortiSwitch response AND the evidence needed to verify it? Select TWO.
- Inspect supported topology, FortiLink p2p settings, TPID, transport reachability, discovery frames and switch firmware.
- Use supported FortiLink point-to-point L2 or Layer-3 transport configuration and validate discovery and control traffic end to end.
- Assign FortiSwitch VLANs and ports to the intended FortiGate VDOM with explicit isolation and governed shared infrastructure.
- Inspect customer VLAN tags, service VLAN outer tag, FortiLink parent VDOM, mapping and interface capability.
- Routes and interfaces are configured at the appropriate control plane and persist after synchronization or reboot.
Explanation
Correct Answers
A:Inspect supported topology, FortiLink p2p settings, TPID, transport reachability, discovery frames and switch firmware. FortiLink over intermediate networks requires topology-specific settings; ordinary IP reachability alone does not establish FortiLink discovery. The paired action is: Use supported FortiLink point-to-point L2 or Layer-3 transport configuration and validate discovery and control traffic end to end. This is the diagnostic or verification half of the requested TWO-step pair.
B:Use supported FortiLink point-to-point L2 or Layer-3 transport configuration and validate discovery and control traffic end to end. FortiLink over intermediate networks requires topology-specific settings; ordinary IP reachability alone does not establish FortiLink discovery. Verify the action with: Inspect supported topology, FortiLink p2p settings, TPID, transport reachability, discovery frames and switch firmware. This is the configuration or remediation half of the requested TWO-step pair.
Incorrect Answers
C:Assign FortiSwitch VLANs and ports to the intended FortiGate VDOM with explicit isolation and governed shared infrastructure. This step concerns FortiGate VDOM-based FortiSwitch tenant assignment and is not part of the required paired solution. The correct action and evidence are: Use supported FortiLink point-to-point L2 or Layer-3 transport configuration and validate discovery and control traffic end to end. Together with: Inspect supported topology, FortiLink p2p settings, TPID, transport reachability, discovery frames and switch firmware.
D:Inspect customer VLAN tags, service VLAN outer tag, FortiLink parent VDOM, mapping and interface capability. This step concerns QinQ outer and inner VLAN tenant mapping and is not part of the required paired solution. The correct action and evidence are: Use supported FortiLink point-to-point L2 or Layer-3 transport configuration and validate discovery and control traffic end to end. Together with: Inspect supported topology, FortiLink p2p settings, TPID, transport reachability, discovery frames and switch firmware.
E:Routes and interfaces are configured at the appropriate control plane and persist after synchronization or reboot. This step concerns FortiSwitch standalone versus FortiLink managed L3 ownership and is not part of the required paired solution. The correct action and evidence are: Use supported FortiLink point-to-point L2 or Layer-3 transport configuration and validate discovery and control traffic end to end. Together with: Inspect supported topology, FortiLink p2p settings, TPID, transport reachability, discovery frames and switch firmware.
Question 357
A pair of distribution FortiSwitch units has dual client uplinks but never formed an MCLAG peer group. Which FortiSwitch configuration or corrective action BEST addresses the requirement?
- Configure supported FortiSwitch MCLAG peer groups and peer links before connecting downstream redundant bundles.
- Correlate stack and ISL status to identify the failed path instead of reconfiguring all access VLANs.
- Apply supported egress CoS queue policy to reduce latency under congestion without starving other required traffic.
- Authorize only intended discovered FortiSwitch serial numbers and confirm management mode after the expected transition.
Explanation
Correct Answer
A:Configure supported FortiSwitch MCLAG peer groups and peer links before connecting downstream redundant bundles. MCLAG redundancy depends on supported peer-link and aggregate design; two cables alone do not constitute working multichassis aggregation. Verify the action with: Inspect MCLAG peer status, inter-chassis link, negotiated aggregate IDs, VLAN consistency and controller topology.
Incorrect Answers
B: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: Configure supported FortiSwitch MCLAG peer groups and peer links before connecting downstream redundant bundles.
C: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: Configure supported FortiSwitch MCLAG peer groups and peer links before connecting downstream redundant bundles.
D:Authorize only intended discovered FortiSwitch serial numbers and confirm management mode after the expected transition. This action is relevant to Discovered versus authorized FortiSwitch state, not the controlling requirement in this case. Switch discovery is not the same as authorization; auto-authorization has governance implications and a managed-mode transition may reboot the device. The targeted response is: Configure supported FortiSwitch MCLAG peer groups and peer links before connecting downstream redundant bundles.
Question 358
Two distribution switches have different MST region revisions and flood after a redundant connection is added. Which observable result BEST proves the intended FortiSwitch operation or security policy works?
- The current neighboring device and optional endpoint location are visible and match approved cabling documentation.
- Managed status remains healthy and user traffic uses only its intended FortiLink-carried VLANs.
- A planned alternate link remains blocked and takes over predictably without a broadcast storm.
- Every relevant VLAN converges without loops and redundant paths unblock only when needed.
Explanation
Correct Answer
C: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:The current neighboring device and optional endpoint location are visible and match approved cabling documentation. This result relates to LLDP neighbor discovery and location information, not the acceptance condition under test. The relevant result is: A planned alternate link remains blocked and takes over predictably without a broadcast storm.
B:Managed status remains healthy and user traffic uses only its intended FortiLink-carried VLANs. This result relates to FortiLink control and client VLAN transport separation, 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 359
An organization attempts to push an IPv6 DACL policy even though the supported FortiSwitch release documents only IPv4 DACL support. Which FortiSwitch configuration or corrective action BEST addresses the requirement?
- Use supported intra-VLAN traffic controls when clients in the same broadcast domain must not communicate directly.
- Verify dynamic ACL assignment from RADIUS after successful 802.1X and account for platform rule and IPv4 support constraints.
- Apply a specific restricted VLAN or quarantine mechanism with explicit authorized remediation and monitoring expectations.
- Use FortiGate FortiSwitch Ports statistics or supported switch commands to isolate errors, utilization and port status at the right location.
Explanation
Correct Answer
B:Verify dynamic ACL assignment from RADIUS after successful 802.1X and account for platform rule and IPv4 support constraints. DACLs install after successful authorization and documented release limits apply; a RADIUS response alone is not proof of forwarding enforcement. Verify the action with: Inspect RADIUS Filter-Id or downloadable ACL attribute, authenticated session state, installed hardware entries and ACL counters.
Incorrect Answers
A: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: Verify dynamic ACL assignment from RADIUS after successful 802.1X and account for platform rule and IPv4 support constraints.
C: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: Verify dynamic ACL assignment from RADIUS after successful 802.1X and account for platform rule and IPv4 support constraints.
D:Use FortiGate FortiSwitch Ports statistics or supported switch commands to isolate errors, utilization and port status at the right location. This action is relevant to Managed switch port statistics and counter analysis, not the controlling requirement in this case. A port-up indicator or one successful ping is not proof that a congested or errored uplink is healthy. The targeted response is: Verify dynamic ACL assignment from RADIUS after successful 802.1X and account for platform rule and IPv4 support constraints.
Question 360
A voice client obtains an address yet keeps receiving ARP replies for the wrong gateway MAC. 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.
- Define appropriate trusted ingress marking sources and classify untrusted frames before choosing egress queues.
- Mirror only the relevant source ports or VLAN traffic to a dedicated analyzer destination using supported SPAN settings.
- Trace DHCP and ARP exchanges at ingress and uplink to distinguish missing requests from blocked or malformed responses.
Explanation
Correct Answer
D:Trace DHCP and ARP exchanges at ingress and uplink to distinguish missing requests from blocked or malformed responses. A DHCP lease failure can originate at the client, switch, relay or server; capturing at one side alone is not always conclusive. Verify the action with: Inspect Discover/Offer/Request/Ack sequence, ARP requests/replies, VLAN tags, DHCP snooping and DAI counters.
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: Trace DHCP and ARP exchanges at ingress and uplink to distinguish missing requests from blocked or malformed responses.
B:Define appropriate trusted ingress marking sources and classify untrusted frames before choosing egress queues. This action is relevant to QoS ingress classification and trust boundaries, not the controlling requirement in this case. A packet marking has no useful QoS effect until supported classification and scheduling map it consistently. The targeted response is: Trace DHCP and ARP exchanges at ingress and uplink to distinguish missing requests from blocked or malformed responses.
C: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: Trace DHCP and ARP exchanges at ingress and uplink to distinguish missing requests from blocked or malformed responses.