Fortinet NSE5_FSW_AD-7.6 Practice Test 19
Question 180
A contractor requests a full week of unfiltered packet data from a production finance VLAN to diagnose one DHCP issue. Which FortiSwitch configuration or corrective action BEST addresses the requirement?
- Correlate LLDP neighbor inventory and VLAN-specific MAC entries to reconstruct actual endpoint and uplink paths.
- Use narrow capture windows, least-privilege access and approved storage/retention when collecting packet data for diagnostics.
- Retrieve and maintain approved FortiSwitch model, firmware, configuration and authorized-controller records to support incident recovery.
- 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 narrow capture windows, least-privilege access and approved storage/retention when collecting packet data for diagnostics. A packet-capture tool may record payloads and credentials, so evidence handling is part of the network security process. Verify the action with: Review filter minimization, capture duration, administrator authorization, sensitive payloads and evidence-sharing restrictions.
Incorrect Answers
A:Correlate LLDP neighbor inventory and VLAN-specific MAC entries to reconstruct actual endpoint and uplink paths. This action is relevant to LLDP and MAC forwarding table extraction, not the controlling requirement in this case. LLDP provides adjacent-device identity, while MAC learning maps forwarding; neither is a full routed trace by itself. The targeted response is: Use narrow capture windows, least-privilege access and approved storage/retention when collecting packet data for diagnostics.
C: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 narrow capture windows, least-privilege access and approved storage/retention when collecting packet data for diagnostics.
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 narrow capture windows, least-privilege access and approved storage/retention when collecting packet data for diagnostics.
Question 181
A handset supports LLDP-MED but the access switch is configured only to receive LLDP and not advertise local policy. Which TWO complementary steps identify the appropriate FortiSwitch response AND the evidence needed to verify it? Select TWO.
- Use STP state and MAC move evidence to isolate one bad bridging path and change only the proven element.
- Configure supported LLDP-MED voice policy so a compatible handset learns its VLAN and traffic priority.
- Inspect transceiver SKU, supported compatibility table, Tx/Rx optical power, interface alarms and cable plant type.
- A controlled FortiGate HA failover leaves managed switches authorized and required client access functioning.
- Examine LLDP transmit state, port profile, neighbor TLVs, advertised VLAN and DSCP or 802.1p settings.
Explanation
Correct Answers
B:Configure supported LLDP-MED voice policy so a compatible handset learns its VLAN and traffic priority. LLDP-MED exchanges policy hints with compatible endpoints; it does not substitute for port membership and DHCP. Verify the action with: Examine LLDP transmit state, port profile, neighbor TLVs, advertised VLAN and DSCP or 802.1p settings. This is the configuration or remediation half of the requested TWO-step pair.
E:Examine LLDP transmit state, port profile, neighbor TLVs, advertised VLAN and DSCP or 802.1p settings. LLDP-MED exchanges policy hints with compatible endpoints; it does not substitute for port membership and DHCP. The paired action is: Configure supported LLDP-MED voice policy so a compatible handset learns its VLAN and traffic priority. This is the diagnostic or verification half of the requested TWO-step pair.
Incorrect Answers
A:Use STP state and MAC move evidence to isolate one bad bridging path and change only the proven element. This step concerns STP incident recovery with MAC flap evidence and is not part of the required paired solution. The correct action and evidence are: Configure supported LLDP-MED voice policy so a compatible handset learns its VLAN and traffic priority. Together with: Examine LLDP transmit state, port profile, neighbor TLVs, advertised VLAN and DSCP or 802.1p settings.
C:Inspect transceiver SKU, supported compatibility table, Tx/Rx optical power, interface alarms and cable plant type. This step concerns Optic compatibility and laser diagnostic evidence and is not part of the required paired solution. The correct action and evidence are: Configure supported LLDP-MED voice policy so a compatible handset learns its VLAN and traffic priority. Together with: Examine LLDP transmit state, port profile, neighbor TLVs, advertised VLAN and DSCP or 802.1p settings.
D:A controlled FortiGate HA failover leaves managed switches authorized and required client access functioning. This step concerns HA FortiGate pair managing switch topology and is not part of the required paired solution. The correct action and evidence are: Configure supported LLDP-MED voice policy so a compatible handset learns its VLAN and traffic priority. Together with: Examine LLDP transmit state, port profile, neighbor TLVs, advertised VLAN and DSCP or 802.1p settings.
Question 182
Voice packets show the correct DSCP but the uplink queues them as ordinary best-effort traffic. 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.
- The exact dropped direction or incorrect address binding is evidenced before changing a security feature.
- Each intended managed switch appears with valid upstream connectivity and no unintended layer-2 loop.
- Voice packets receive intended treatment without allowing arbitrary untrusted hosts to claim top priority.
Explanation
Correct Answer
D:Voice packets receive intended treatment without allowing arbitrary untrusted hosts to claim top priority. A packet marking has no useful QoS effect until supported classification and scheduling map it consistently.
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: Voice packets receive intended treatment without allowing arbitrary untrusted hosts to claim top priority.
B: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: Voice packets receive intended treatment without allowing arbitrary untrusted hosts to claim top priority.
C:Each intended managed switch appears with valid upstream connectivity and no unintended layer-2 loop. This result relates to FortiLink ISL auto-discovery and stack cabling, not the acceptance condition under test. The relevant result is: Voice packets receive intended treatment without allowing arbitrary untrusted hosts to claim top priority.
Question 183
A gigabit analyzer drops mirrored frames from multiple saturated 10G sources and the engineer misreads the capture as true link loss. Which FortiSwitch configuration or corrective action BEST addresses the requirement?
- Retrieve and maintain approved FortiSwitch model, firmware, configuration and authorized-controller records to support incident recovery.
- Verify model-specific PoE class, total switch power budget and per-port policy before enabling new powered devices.
- Mirror only the relevant source ports or VLAN traffic to a dedicated analyzer destination using supported SPAN settings.
- Collect supported SNMP or sFlow telemetry securely with appropriate collector authorization, sampling and interface scope.
Explanation
Correct Answer
C:Mirror only the relevant source ports or VLAN traffic to a dedicated analyzer destination using supported SPAN settings. A mirrored stream is passive evidence and can be incomplete if analyzer bandwidth is lower than the observed traffic. Verify the action with: Inspect mirror direction, source and destination ports, speed constraints, physical capture link and switch statistics.
Incorrect Answers
A: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: Mirror only the relevant source ports or VLAN traffic to a dedicated analyzer destination using supported SPAN settings.
B:Verify model-specific PoE class, total switch power budget and per-port policy before enabling new powered devices. This action is relevant to Power over Ethernet port controls and budgets, not the controlling requirement in this case. Not every FortiSwitch model or port supports identical PoE allocation or every attached device's peak draw. The targeted response is: Mirror only the relevant source ports or VLAN traffic to a dedicated analyzer destination using supported SPAN settings.
D: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: Mirror only the relevant source ports or VLAN traffic to a dedicated analyzer destination using supported SPAN settings.
Question 184
A broad profile overrides a more specific guest device rule and grants a larger VLAN scope than planned. Which observable result BEST proves the intended FortiSwitch operation or security policy works?
- A controlled peer or member failure maintains approved client VLAN access without a Layer-2 loop.
- Known printers and IoT devices enter their restricted VLANs while unknown endpoints have no excessive access.
- Isolated clients can reach approved gateways while direct lateral traffic within the VLAN is blocked according to policy.
- Port traffic follows the assigned access security requirement without arbitrary drift after controller synchronization.
Explanation
Correct Answer
D:Port traffic follows the assigned access security requirement without arbitrary drift after controller synchronization. A named security profile sitting in configuration is not proof that it was applied to the intended hardware port.
Incorrect Answers
A:A controlled peer or member failure maintains approved client VLAN access without a Layer-2 loop. This result relates to MCLAG multichassis access redundancy, not the acceptance condition under test. The relevant result is: Port traffic follows the assigned access security requirement without arbitrary drift after controller synchronization.
B: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: Port traffic follows the assigned access security requirement without arbitrary drift after controller synchronization.
C:Isolated clients can reach approved gateways while direct lateral traffic within the VLAN is blocked according to policy. This result relates to Intra-VLAN blocking and isolation boundaries, not the acceptance condition under test. The relevant result is: Port traffic follows the assigned access security requirement without arbitrary drift after controller synchronization.
Question 185
An operator puts a VLAN under a WAN interface instead of the FortiLink interface used by the branch switches. Which diagnostic evidence should the FortiSwitch administrator examine FIRST?
- Examine LLDP transmit state, port profile, neighbor TLVs, advertised VLAN and DSCP or 802.1p settings.
- Compare controller desired VLAN map, current switch running state, configuration synchronization and post-reboot behavior.
- Check FortiLink parent, VLAN ID, VDOM membership, port assignment, subnet and firewall-policy path.
- Check managed tree, ISL link health, model compatibility, VLAN carriage, depth limitations and upstream aggregate status.
Explanation
Correct Answer
C:Check FortiLink parent, VLAN ID, VDOM membership, port assignment, subnet and firewall-policy path. A named VLAN in FortiOS is not proof its switch-port membership and L3 policy are correct. The paired action is: Build FortiSwitch VLAN interfaces in the correct FortiLink context and assign ports through the managed switch controller.
Incorrect Answers
A:Examine LLDP transmit state, port profile, neighbor TLVs, advertised VLAN and DSCP or 802.1p settings. These observations are applicable to LLDP-MED voice network policy advertisements, but would not isolate the main failure first. The decisive evidence is: Check FortiLink parent, VLAN ID, VDOM membership, port assignment, subnet and firewall-policy path.
B:Compare controller desired VLAN map, current switch running state, configuration synchronization and post-reboot behavior. These observations are applicable to VLAN configuration persistence and drift control, but would not isolate the main failure first. The decisive evidence is: Check FortiLink parent, VLAN ID, VDOM membership, port assignment, subnet and firewall-policy path.
D:Check managed tree, ISL link health, model compatibility, VLAN carriage, depth limitations and upstream aggregate status. These observations are applicable to FortiSwitch multi-tier managed topology, but would not isolate the main failure first. The decisive evidence is: Check FortiLink parent, VLAN ID, VDOM membership, port assignment, subnet and firewall-policy path.
Question 186
An untrusted edge switch discards a valid server Offer and the fault is blamed on DHCP service uptime. Which TWO complementary steps identify the appropriate FortiSwitch response AND the evidence needed to verify it? Select TWO.
- Review frame error type, CRC/FCS, traffic rates, drops, operational speed, port description and sampled timestamps.
- Mirror only the relevant source ports or VLAN traffic to a dedicated analyzer destination using supported SPAN settings.
- Every relevant VLAN converges without loops and redundant paths unblock only when needed.
- Inspect Discover/Offer/Request/Ack sequence, ARP requests/replies, VLAN tags, DHCP snooping and DAI counters.
- Trace DHCP and ARP exchanges at ingress and uplink to distinguish missing requests from blocked or malformed responses.
Explanation
Correct Answers
D: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. This is the diagnostic or verification half of the requested TWO-step pair.
E: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. This is the configuration or remediation half of the requested TWO-step pair.
Incorrect Answers
A:Review frame error type, CRC/FCS, traffic rates, drops, operational speed, port description and sampled timestamps. 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: Trace DHCP and ARP exchanges at ingress and uplink to distinguish missing requests from blocked or malformed responses. Together with: Inspect Discover/Offer/Request/Ack sequence, ARP requests/replies, VLAN tags, DHCP snooping and DAI counters.
B:Mirror only the relevant source ports or VLAN traffic to a dedicated analyzer destination using supported SPAN settings. This step concerns FortiSwitch port mirroring to network analyzer and is not part of the required paired solution. The correct action and evidence are: Trace DHCP and ARP exchanges at ingress and uplink to distinguish missing requests from blocked or malformed responses. Together with: Inspect Discover/Offer/Request/Ack sequence, ARP requests/replies, VLAN tags, DHCP snooping and DAI counters.
C:Every relevant VLAN converges without loops and redundant paths unblock only when needed. This step concerns RPVST and supported STP mode interoperability and is not part of the required paired solution. The correct action and evidence are: Trace DHCP and ARP exchanges at ingress and uplink to distinguish missing requests from blocked or malformed responses. Together with: Inspect Discover/Offer/Request/Ack sequence, ARP requests/replies, VLAN tags, DHCP snooping and DAI counters.
Question 187
A pair of distribution FortiSwitch units has dual client uplinks but never formed an MCLAG peer group. Which observable result BEST proves the intended FortiSwitch operation or security policy works?
- Known printers and IoT devices enter their restricted VLANs while unknown endpoints have no excessive access.
- A redundant topology recovers after a link failure without simultaneous independent forwarding paths causing loops.
- Hosts can reach their intended SVI and authorized routed destinations without overlapping address space.
- A downstream dual-homed switch retains service on one peer failure without duplicate independent forwarding loops.
Explanation
Correct Answer
D:A downstream dual-homed switch retains service on one peer failure without duplicate independent forwarding loops. MCLAG redundancy depends on supported peer-link and aggregate design; two cables alone do not constitute working multichassis aggregation.
Incorrect Answers
A: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: A downstream dual-homed switch retains service on one peer failure without duplicate independent forwarding loops.
B:A redundant topology recovers after a link failure without simultaneous independent forwarding paths causing loops. This result relates to FortiLink split-interface and standby path design, not the acceptance condition under test. The relevant result is: A downstream dual-homed switch retains service on one peer failure without duplicate independent forwarding loops.
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: A downstream dual-homed switch retains service on one peer failure without duplicate independent forwarding loops.
Question 188
When a distribution uplink fails, three downstream switches disappear from the FortiGate controller together. Which TWO complementary steps identify the appropriate FortiSwitch response AND the evidence needed to verify it? Select TWO.
- Exactly the intended serial joins managed inventory and receives approved controller settings after authorization.
- Configure supported FortiSwitch MCLAG peer groups and peer links before connecting downstream redundant bundles.
- Review queue maps, output drops, interface rate, strict versus weighted servicing and application latency.
- Correlate stack and ISL status to identify the failed path instead of reconfiguring all access VLANs.
- Check managed topology view, controller switch state, ISL port counters, peer LLDP and suspected link events.
Explanation
Correct Answers
D:Correlate stack and ISL status to identify the failed path instead of reconfiguring all access VLANs. A missing switch in a FortiLink managed chain may be caused by the upstream ISL even if its access ports still carry local traffic. Verify the action with: Check managed topology view, controller switch state, ISL port counters, peer LLDP and suspected link events. This is the configuration or remediation half of the requested TWO-step pair.
E:Check managed topology view, controller switch state, ISL port counters, peer LLDP and suspected link events. 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 paired action is: Correlate stack and ISL status to identify the failed path instead of reconfiguring all access VLANs. This is the diagnostic or verification half of the requested TWO-step pair.
Incorrect Answers
A: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: Correlate stack and ISL status to identify the failed path instead of reconfiguring all access VLANs. Together with: Check managed topology view, controller switch state, ISL port counters, peer LLDP and suspected link events.
B:Configure supported FortiSwitch MCLAG peer groups and peer links before connecting downstream redundant bundles. This step concerns MCLAG peer-link topology for managed access switches and is not part of the required paired solution. The correct action and evidence are: Correlate stack and ISL status to identify the failed path instead of reconfiguring all access VLANs. Together with: Check managed topology view, controller switch state, ISL port counters, peer LLDP and suspected link events.
C:Review queue maps, output drops, interface rate, strict versus weighted servicing and application latency. This step concerns Egress priority scheduling and congestion visibility and is not part of the required paired solution. The correct action and evidence are: Correlate stack and ISL status to identify the failed path instead of reconfiguring all access VLANs. Together with: Check managed topology view, controller switch state, ISL port counters, peer LLDP and suspected link events.
Question 189
An administrator gives every traffic class strict priority and then cannot explain which queue is actually served. Which FortiSwitch configuration or corrective action BEST addresses the requirement?
- Authorize only intended discovered FortiSwitch serial numbers and confirm management mode after the expected transition.
- Validate the supported PoE budget and LLDP-MED endpoint power negotiation rather than equating link up with adequate wattage.
- Enable supported BPDU guard only on true edge/client ports, and restore blocked ports after identifying unauthorized switching.
- Apply supported egress CoS queue policy to reduce latency under congestion without starving other required traffic.
Explanation
Correct Answer
D:Apply supported egress CoS queue policy to reduce latency under congestion without starving other required traffic. QoS prioritizes scarce link capacity but cannot create bandwidth beyond the physical egress rate. Verify the action with: Review queue maps, output drops, interface rate, strict versus weighted servicing and application latency.
Incorrect Answers
A: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: Apply supported egress CoS queue policy to reduce latency under congestion without starving other required traffic.
B:Validate the supported PoE budget and LLDP-MED endpoint power negotiation rather than equating link up with adequate wattage. This action is relevant to PoE and LLDP-MED endpoint power coordination, not the controlling requirement in this case. Port count and Ethernet link state do not guarantee sufficient power for high-draw endpoints. The targeted response is: Apply supported egress CoS queue policy to reduce latency under congestion without starving other required traffic.
C:Enable supported BPDU guard only on true edge/client ports, and restore blocked ports after identifying unauthorized switching. This action is relevant to BPDU guard on endpoint-facing ports, not the controlling requirement in this case. BPDU guard can disable an intended trunk if incorrectly treated as an end-station port. The targeted response is: Apply supported egress CoS queue policy to reduce latency under congestion without starving other required traffic.
Question 190
An administrator assumes a new FortiSwitch model accepts the same firmware image as an older campus model. Which diagnostic evidence should the FortiSwitch administrator examine FIRST?
- Review discovered/authorized controller inventory, switch serial, link state, approval method, reboot status and firmware compatibility.
- Check interface type, FortiLink enablement, discovery setting, IP assignment, switch model support, and management VLAN reachability.
- Review firmware compatibility, release notes, current image, boot fallback, managed switch inventory and upgrade sequencing.
- Inspect local and neighbor port IDs, timestamp, learned MAC per VLAN, trunk member and expected cabling map.
Explanation
Correct Answer
C:Review firmware compatibility, release notes, current image, boot fallback, managed switch inventory and upgrade sequencing. A successful image upload does not prove switch operation or controller compatibility after reboot. The paired action is: Choose supported FortiSwitchOS version and maintenance workflow compatible with the FortiGate version and topology.
Incorrect Answers
A:Review discovered/authorized controller inventory, switch serial, link state, approval method, reboot status and firmware compatibility. These observations are applicable to Discovered versus authorized FortiSwitch state, but would not isolate the main failure first. The decisive evidence is: Review firmware compatibility, release notes, current image, boot fallback, managed switch inventory and upgrade sequencing.
B:Check interface type, FortiLink enablement, discovery setting, IP assignment, switch model support, and management VLAN reachability. These observations are applicable to FortiLink management interface provisioning, but would not isolate the main failure first. The decisive evidence is: Review firmware compatibility, release notes, current image, boot fallback, managed switch inventory and upgrade sequencing.
D:Inspect local and neighbor port IDs, timestamp, learned MAC per VLAN, trunk member and expected cabling map. These observations are applicable to LLDP and MAC forwarding table extraction, but would not isolate the main failure first. The decisive evidence is: Review firmware compatibility, release notes, current image, boot fallback, managed switch inventory and upgrade sequencing.