Fortinet NSE5_FSW_AD-7.6 Practice Test 34
Question 330
One FortiSwitch reboot causes adjacent units to move between discovered and authorized states. Which observable result BEST proves the intended FortiSwitch operation or security policy works?
- The failed ISL or switch is isolated and recovered with all unaffected downstream switches remaining correctly managed.
- Accidental downstream switches are contained without disabling legitimate uplinks that should exchange BPDUs.
- The managed switch retains the intended controller-pushed policy after a controlled synchronization and restart.
- Hosts can reach their intended SVI and authorized routed destinations without overlapping address space.
Explanation
Correct Answer
A:The failed ISL or switch is isolated and recovered with all unaffected downstream switches remaining correctly managed. A missing switch in a FortiLink managed chain may be caused by the upstream ISL even if its access ports still carry local traffic.
Incorrect Answers
B:Accidental downstream switches are contained without disabling legitimate uplinks that should exchange BPDUs. This result relates to BPDU guard on endpoint-facing ports, not the acceptance condition under test. The relevant result is: The failed ISL or switch is isolated and recovered with all unaffected downstream switches remaining correctly managed.
C:The managed switch retains the intended controller-pushed policy after a controlled synchronization and restart. This result relates to Managed switch configuration synchronization, not the acceptance condition under test. The relevant result is: The failed ISL or switch is isolated and recovered with all unaffected downstream switches remaining correctly managed.
D:Hosts can reach their intended SVI and authorized routed destinations without overlapping address space. This result relates to FortiSwitch SVI routing and connected routes, not the acceptance condition under test. The relevant result is: The failed ISL or switch is isolated and recovered with all unaffected downstream switches remaining correctly managed.
Question 331
A user changes departments and the RADIUS server issues CoA but the switch continues enforcing the old access role. Which TWO complementary steps identify the appropriate FortiSwitch response AND the evidence needed to verify it? Select TWO.
- Review RADIUS Access-Accept attributes, CoA path, session identifier, switch port role, DACL installation and packet test.
- Inspect frame-rate counters by class, threshold configuration, affected VLANs and protocol health under controlled load.
- Latency-sensitive flows improve under representative load while other business services remain functional.
- 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.
Explanation
Correct Answers
A: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.
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. This is the configuration or remediation half of the requested TWO-step pair.
Incorrect Answers
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: 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.
C:Latency-sensitive flows improve under representative load while other business services remain functional. This step concerns Egress priority scheduling and congestion visibility 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:Set model-supported dynamic MAC address learning limits and specific violation action on access-facing switch ports. 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: 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.
Question 332
An MCLAG access uplink fails after a peer link replacement and the team tests only physical LEDs. Which FortiSwitch configuration or corrective action BEST addresses the requirement?
- Use supported native and voice VLAN policies so phones and downstream workstations receive appropriate separate traffic treatment.
- Use supported dynamic ARP inspection with valid switch bindings to reject spoofed IP-MAC claims at untrusted edges.
- Configure supported LLDP-MED voice policy so a compatible handset learns its VLAN and traffic priority.
- Configure supported FortiSwitch MCLAG peer groups and peer links before connecting downstream redundant bundles.
Explanation
Correct Answer
D: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
A:Use supported native and voice VLAN policies so phones and downstream workstations receive appropriate separate traffic treatment. This action is relevant to Voice and data VLAN separation on shared access ports, not the controlling requirement in this case. Voice tagging is not secured merely because its VLAN ID differs from the workstation's native VLAN. The targeted response is: Configure supported FortiSwitch MCLAG peer groups and peer links before connecting downstream redundant bundles.
B:Use supported dynamic ARP inspection with valid switch bindings to reject spoofed IP-MAC claims at untrusted edges. This action is relevant to Dynamic ARP inspection with DHCP snooping bindings, not the controlling requirement in this case. DAI validation needs a reliable binding or exception policy; enabling it blindly can interrupt static-IP devices. The targeted response is: Configure supported FortiSwitch MCLAG peer groups and peer links before connecting downstream redundant bundles.
C:Configure supported LLDP-MED voice policy so a compatible handset learns its VLAN and traffic priority. This action is relevant to LLDP-MED voice network policy advertisements, not the controlling requirement in this case. LLDP-MED exchanges policy hints with compatible endpoints; it does not substitute for port membership and DHCP. The targeted response is: Configure supported FortiSwitch MCLAG peer groups and peer links before connecting downstream redundant bundles.
Question 333
A new replacement is visible in discovery but its ports do not receive policy because it is pending authorization. Which diagnostic evidence should the FortiSwitch administrator examine FIRST?
- Check ingress port, assigned VLAN ID, owner VDOM, gateway, firewall session path and cross-tenant deny counters.
- Review discovered/authorized controller inventory, switch serial, link state, approval method, reboot status and firmware compatibility.
- Inspect MAC table usage, configured learning limit, learned device count, port-security event and violation action.
- Review firmware compatibility, release notes, current image, boot fallback, managed switch inventory and upgrade sequencing.
Explanation
Correct Answer
B:Review discovered/authorized controller inventory, switch serial, link state, approval method, reboot status and firmware compatibility. Switch discovery is not the same as authorization; auto-authorization has governance implications and a managed-mode transition may reboot the device. The paired action is: Authorize only intended discovered FortiSwitch serial numbers and confirm management mode after the expected transition.
Incorrect Answers
A:Check ingress port, assigned VLAN ID, owner VDOM, gateway, firewall session path and cross-tenant deny counters. These observations are applicable to Managed tenant troubleshooting across controller and access layer, but would not isolate the main failure first. The decisive evidence is: Review discovered/authorized controller inventory, switch serial, link state, approval method, reboot status and firmware compatibility.
C:Inspect MAC table usage, configured learning limit, learned device count, port-security event and violation action. These observations are applicable to Port MAC learning-limit and violation controls, but would not isolate the main failure first. The decisive evidence is: Review discovered/authorized controller inventory, switch serial, link state, approval method, reboot status and firmware compatibility.
D:Review firmware compatibility, release notes, current image, boot fallback, managed switch inventory and upgrade sequencing. These observations are applicable to Firmware and lifecycle preparation for FortiSwitch, but would not isolate the main failure first. The decisive evidence is: Review discovered/authorized controller inventory, switch serial, link state, approval method, reboot status and firmware compatibility.
Question 334
A high-power access point boots but shuts down once its additional radio activates. Which FortiSwitch configuration or corrective action BEST addresses the requirement?
- Set only mutually supported Ethernet port rates and verify operational negotiation instead of forcing mismatched speeds.
- Verify model-specific PoE class, total switch power budget and per-port policy before enabling new powered devices.
- Attach an approved port-security or switch-security profile to the correct FortiSwitch access port and verify effective policy precedence.
- Apply appropriate STP root or loop protection to preserve topology while analyzing missing BPDUs and unexpected root claims.
Explanation
Correct Answer
B:Verify model-specific PoE class, total switch power budget and per-port policy before enabling new powered devices. Not every FortiSwitch model or port supports identical PoE allocation or every attached device's peak draw. Verify the action with: Inspect power supply reserve, current draw, negotiated PoE class, priority shedding and port events.
Incorrect Answers
A:Set only mutually supported Ethernet port rates and verify operational negotiation instead of forcing mismatched speeds. This action is relevant to Switch port speed and duplex commissioning, not the controlling requirement in this case. Incorrect forced port speed or duplex can mimic application loss even when the VLAN configuration is valid. The targeted response is: Verify model-specific PoE class, total switch power budget and per-port policy before enabling new powered devices.
C: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: Verify model-specific PoE class, total switch power budget and per-port policy before enabling new powered devices.
D:Apply appropriate STP root or loop protection to preserve topology while analyzing missing BPDUs and unexpected root claims. This action is relevant to Root guard and loop guard failure response, not the controlling requirement in this case. Root guard and loop guard mitigate different failure cases and should not be enabled indiscriminately on every uplink. The targeted response is: Verify model-specific PoE class, total switch power budget and per-port policy before enabling new powered devices.
Question 335
A device dashboard shows an average rate that hides short bursts of dropped voice traffic. Which FortiSwitch configuration or corrective action BEST addresses the requirement?
- Collect supported SNMP or sFlow telemetry securely with appropriate collector authorization, sampling and interface scope.
- 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.
- Retrieve and maintain approved FortiSwitch model, firmware, configuration and authorized-controller records to support incident recovery.
Explanation
Correct Answer
C:Use FortiGate FortiSwitch Ports statistics or supported switch commands to isolate errors, utilization and port status at the right location. A port-up indicator or one successful ping is not proof that a congested or errored uplink is healthy. Verify the action with: Review frame error type, CRC/FCS, traffic rates, drops, operational speed, port description and sampled timestamps.
Incorrect Answers
A:Collect supported SNMP or sFlow telemetry securely with appropriate collector authorization, sampling and interface scope. This action is relevant to SNMP and sFlow monitoring configuration, not the controlling requirement in this case. Flow samples are estimates and counters vary by port; collecting telemetry cannot replace a controlled packet capture when headers are needed. The targeted response is: Use FortiGate FortiSwitch Ports statistics or supported switch commands to isolate errors, utilization and port status at the right location.
B: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: Use FortiGate FortiSwitch Ports statistics or supported switch commands to isolate errors, utilization and port status at the right location.
D:Retrieve and maintain approved FortiSwitch model, firmware, configuration and authorized-controller records to support incident recovery. This action is relevant to Config backup and firmware inventory evidence, not the controlling requirement in this case. Backups require correct model/version and an actual restore procedure; a saved file name is not proof a recovered switch will work. The targeted response is: Use FortiGate FortiSwitch Ports statistics or supported switch commands to isolate errors, utilization and port status at the right location.
Question 336
A user moves between ports and the stale binding on the old port rejects the new legitimate lease. 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.
- Inspect port profile assignment, FortiGate controller policy, client role, enforcement counters and overlapping static controls.
- A failed managed switch can be replaced with supported firmware and restored authorized port/VLAN behavior.
- Enable supported DHCP snooping on client VLANs and trust only known DHCP-server or relay-facing links.
- Examine port binding list, packet source IP, ingress VLAN, IP-source guard counters and expected host subnet.
Explanation
Correct Answers
A:Enable IPv4 source guard on supported switch interfaces only with appropriate DHCP snooping or static bindings. Source guard is an ingress source-binding check, not a full replacement for routed firewall policies or endpoint security. Verify the action with: Examine port binding list, packet source IP, ingress VLAN, IP-source guard counters and expected host subnet. This is the configuration or remediation half of the requested TWO-step pair.
E:Examine port binding list, packet source IP, ingress VLAN, IP-source guard counters and expected host subnet. Source guard is an ingress source-binding check, not a full replacement for routed firewall policies or endpoint security. The paired action is: Enable IPv4 source guard on supported switch interfaces only with appropriate DHCP snooping or static bindings. This is the diagnostic or verification half of the requested TWO-step pair.
Incorrect Answers
B:Inspect port profile assignment, FortiGate controller policy, client role, enforcement counters and overlapping static controls. This step concerns FortiSwitch security profile application and precedence and is not part of the required paired solution. The correct action and evidence are: Enable IPv4 source guard on supported switch interfaces only with appropriate DHCP snooping or static bindings. Together with: Examine port binding list, packet source IP, ingress VLAN, IP-source guard counters and expected host subnet.
C:A failed managed switch can be replaced with supported firmware and restored authorized port/VLAN behavior. This step concerns Config backup and firmware inventory evidence and is not part of the required paired solution. The correct action and evidence are: Enable IPv4 source guard on supported switch interfaces only with appropriate DHCP snooping or static bindings. Together with: Examine port binding list, packet source IP, ingress VLAN, IP-source guard counters and expected host subnet.
D: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: Enable IPv4 source guard on supported switch interfaces only with appropriate DHCP snooping or static bindings. Together with: Examine port binding list, packet source IP, ingress VLAN, IP-source guard counters and expected host subnet.
Question 337
A video stream reaches all desks even though only two phones subscribe to the multicast group. Which observable result BEST proves the intended FortiSwitch operation or security policy works?
- The correct link establishes at expected negotiated rate without recurring loss-of-signal or CRC errors.
- Members receive subscribed streams while unsubscribed access ports are not flooded unnecessarily.
- Hosts can reach their intended SVI and authorized routed destinations without overlapping address space.
- A tenant reaches only its approved VDOM resources and does not inherit another tenant's policies.
Explanation
Correct Answer
B: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
A:The correct link establishes at expected negotiated rate without recurring loss-of-signal or CRC errors. This result relates to Optic compatibility and laser diagnostic evidence, not the acceptance condition under test. The relevant result is: Members receive subscribed streams while unsubscribed access ports are not flooded unnecessarily.
C: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: Members receive subscribed streams while unsubscribed access ports are not flooded unnecessarily.
D:A tenant reaches only its approved VDOM resources and does not inherit another tenant's policies. This result relates to FortiGate VDOM-based FortiSwitch tenant assignment, not the acceptance condition under test. The relevant result is: Members receive subscribed streams while unsubscribed access ports are not flooded unnecessarily.
Question 338
Both ends of a branch trunk are set to passive LACP and none of the physical ports aggregate. Which diagnostic evidence should the FortiSwitch administrator examine FIRST?
- Check route table, next-hop ARP, ingress VLAN, egress interface, prefix length and return-route path.
- Inspect MCLAG peer status, inter-chassis link, negotiated aggregate IDs, VLAN consistency and controller topology.
- Inspect actor partner system IDs, LACP mode, partner synchronization, port speed, VLAN membership and member counters.
- Inspect controller switch list, interface events, authentication logs, current configuration, timestamps and recent change history.
Explanation
Correct Answer
C:Inspect actor partner system IDs, LACP mode, partner synchronization, port speed, VLAN membership and member counters. Passive LACP on both ends may not negotiate an active bundle, and individual green links do not prove aggregation. The paired action is: Choose static, active or passive LACP trunk behavior consistently between peers and verify member aggregation.
Incorrect Answers
A:Check route table, next-hop ARP, ingress VLAN, egress interface, prefix length and return-route path. These observations are applicable to Static route and default gateway validation, but would not isolate the main failure first. The decisive evidence is: Inspect actor partner system IDs, LACP mode, partner synchronization, port speed, VLAN membership and member counters.
B:Inspect MCLAG peer status, inter-chassis link, negotiated aggregate IDs, VLAN consistency and controller topology. These observations are applicable to MCLAG peer-link topology for managed access switches, but would not isolate the main failure first. The decisive evidence is: Inspect actor partner system IDs, LACP mode, partner synchronization, port speed, VLAN membership and member counters.
D:Inspect controller switch list, interface events, authentication logs, current configuration, timestamps and recent change history. These observations are applicable to FortiSwitch diagnostic commands and logs, but would not isolate the main failure first. The decisive evidence is: Inspect actor partner system IDs, LACP mode, partner synchronization, port speed, VLAN membership and member counters.
Question 339
A technician chooses a switch port without auto-discovery support and assumes the FortiGate will still detect it by magic. Which observable result BEST proves the intended FortiSwitch operation or security policy works?
- Managed status remains healthy and user traffic uses only its intended FortiLink-carried VLANs.
- The intended switch appears in discovery after restoring the precise missing interface or transport prerequisite.
- Controller and switch return to supported synchronized software and configuration with test-client services restored.
- Hosts can reach their intended SVI and authorized routed destinations without overlapping address space.
Explanation
Correct Answer
B:The intended switch appears in discovery after restoring the precise missing interface or transport prerequisite. A green Ethernet link is necessary for many paths but does not prove the FortiLink management protocol or discovery is working.
Incorrect Answers
A: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: The intended switch appears in discovery after restoring the precise missing interface or transport prerequisite.
C:Controller and switch return to supported synchronized software and configuration with test-client services restored. This result relates to FortiLink synchronization and upgrade troubleshooting, not the acceptance condition under test. The relevant result is: The intended switch appears in discovery after restoring the precise missing interface or transport prerequisite.
D:Hosts can reach their intended SVI and authorized routed destinations without overlapping address space. This result relates to FortiSwitch SVI routing and connected routes, not the acceptance condition under test. The relevant result is: The intended switch appears in discovery after restoring the precise missing interface or transport prerequisite.
Question 340
A firewall analyst captures only the routed interface while the failure occurs between two hosts in one switch VLAN. Which TWO complementary steps identify the appropriate FortiSwitch response AND the evidence needed to verify it? Select TWO.
- Trace DHCP and ARP exchanges at ingress and uplink to distinguish missing requests from blocked or malformed responses.
- Review filter minimization, capture duration, administrator authorization, sensitive payloads and evidence-sharing restrictions.
- Verify mirror connection, FortiGate sniffing interface, capture expression, expected VLAN tags and packet direction.
- Authorized endpoints enter only permitted VLANs while failed authentication is denied or restricted according to policy.
- Use a supported FortiGate one-arm sniffer or mirrored ingress path to inspect switch traffic where permitted.
Explanation
Correct Answers
C: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. This is the diagnostic or verification half of the requested TWO-step pair.
E:Use a supported FortiGate one-arm sniffer or mirrored ingress path to inspect switch traffic where permitted. Sniffer placement determines visibility; absence of a packet at one observation point does not prove no packet existed elsewhere. Verify the action with: Verify mirror connection, FortiGate sniffing interface, capture expression, expected VLAN tags and packet direction. This is the configuration or remediation half of the requested TWO-step pair.
Incorrect Answers
A:Trace DHCP and ARP exchanges at ingress and uplink to distinguish missing requests from blocked or malformed responses. This step concerns Capture-based DHCP and ARP path isolation and is not part of the required paired solution. The correct action and evidence are: Use a supported FortiGate one-arm sniffer or mirrored ingress path to inspect switch traffic where permitted. Together with: Verify mirror connection, FortiGate sniffing interface, capture expression, expected VLAN tags and packet direction.
B:Review filter minimization, capture duration, administrator authorization, sensitive payloads and evidence-sharing restrictions. This step concerns Capture and confidentiality limits in incident response and is not part of the required paired solution. The correct action and evidence are: Use a supported FortiGate one-arm sniffer or mirrored ingress path to inspect switch traffic where permitted. Together with: Verify mirror connection, FortiGate sniffing interface, capture expression, expected VLAN tags and packet direction.
D:Authorized endpoints enter only permitted VLANs while failed authentication is denied or restricted according to policy. This step concerns FortiSwitch 802.1X port-based authentication and is not part of the required paired solution. The correct action and evidence are: Use a supported FortiGate one-arm sniffer or mirrored ingress path to inspect switch traffic where permitted. Together with: Verify mirror connection, FortiGate sniffing interface, capture expression, expected VLAN tags and packet direction.