Fortinet NSE5_FSW_AD-7.6 Practice Test 62
Question 610
An operations platform sees no FortiSwitch traffic samples because the configured sFlow collector address is wrong. Which FortiSwitch configuration or corrective action BEST addresses the requirement?
- Verify FortiLink management status and user VLAN reachability independently when a switch is authorized but clients fail.
- Build a documented supported FortiSwitch daisy chain or multi-tier topology with adequate ISL uplink capacity and safeguards.
- Collect supported SNMP or sFlow telemetry securely with appropriate collector authorization, sampling and interface scope.
- Collect relevant FortiSwitch controller diagnostics, switch system events and targeted status output before making configuration changes.
Explanation
Correct Answer
C:Collect supported SNMP or sFlow telemetry securely with appropriate collector authorization, sampling and interface scope. Flow samples are estimates and counters vary by port; collecting telemetry cannot replace a controlled packet capture when headers are needed. Verify the action with: Inspect monitoring credentials, SNMP version, sFlow export destination, sample rate, counter freshness and access policy.
Incorrect Answers
A:Verify FortiLink management status and user VLAN reachability independently when a switch is authorized but clients fail. This action is relevant to FortiLink control and client VLAN transport separation, not the controlling requirement in this case. FortiLink transports management and data; a successful controller heartbeat does not guarantee a user VLAN or firewall session is permitted. The targeted response is: Collect supported SNMP or sFlow telemetry securely with appropriate collector authorization, sampling and interface scope.
B: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: Collect supported SNMP or sFlow telemetry securely with appropriate collector authorization, sampling and interface scope.
D:Collect relevant FortiSwitch controller diagnostics, switch system events and targeted status output before making configuration changes. This action is relevant to FortiSwitch diagnostic commands and logs, not the controlling requirement in this case. A log message without source device, time and relevant state is not adequate to prove root cause. The targeted response is: Collect supported SNMP or sFlow telemetry securely with appropriate collector authorization, sampling and interface scope.
Question 611
One 100G interface is split into smaller links but the automation still targets the original parent port name. Which observable result BEST proves the intended FortiSwitch operation or security policy works?
- All expected child interfaces enumerate at supported speeds without disrupting unrelated uplinks.
- The offending misassignment is corrected with both permitted traffic and forbidden cross-tenant traffic tested.
- The correct link establishes at expected negotiated rate without recurring loss-of-signal or CRC errors.
- Both ends connect at compatible rates with stable errors and required throughput.
Explanation
Correct Answer
A:All expected child interfaces enumerate at supported speeds without disrupting unrelated uplinks. A physical QSFP cage does not guarantee that four independent Ethernet child ports can be enabled on every model.
Incorrect Answers
B:The offending misassignment is corrected with both permitted traffic and forbidden cross-tenant traffic tested. This result relates to Managed tenant troubleshooting across controller and access layer, not the acceptance condition under test. The relevant result is: All expected child interfaces enumerate at supported speeds without disrupting unrelated uplinks.
C: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: All expected child interfaces enumerate at supported speeds without disrupting unrelated uplinks.
D:Both ends connect at compatible rates with stable errors and required throughput. This result relates to Switch port speed and duplex commissioning, not the acceptance condition under test. The relevant result is: All expected child interfaces enumerate at supported speeds without disrupting unrelated uplinks.
Question 612
A new VLAN is mapped into a different MST instance on one switch and topology behavior diverges. Which FortiSwitch configuration or corrective action BEST addresses the requirement?
- Use supported MAC-based access controls with narrow authorized device roles and avoid treating MAC addresses as strong identity proof.
- Repair LACP member settings and physical port errors independently before increasing aggregate traffic.
- Use STP state and MAC move evidence to isolate one bad bridging path and change only the proven element.
- Select a consistent supported MSTP region and intentional root-bridge placement for loop-free L2 redundancy.
Explanation
Correct Answer
D:Select a consistent supported MSTP region and intentional root-bridge placement for loop-free L2 redundancy. Different MST configuration identifiers split regions even if switch ports are physically connected. Verify the action with: Review MST region name, revision, VLAN instance map, bridge priorities, root ID and topology-change counters.
Incorrect Answers
A:Use supported MAC-based access controls with narrow authorized device roles and avoid treating MAC addresses as strong identity proof. This action is relevant to MAC-based authentication and restricted legacy devices, not the controlling requirement in this case. A MAC address can be cloned; MAC authentication must be combined with appropriate segmentation and monitoring. The targeted response is: Select a consistent supported MSTP region and intentional root-bridge placement for loop-free L2 redundancy.
B:Repair LACP member settings and physical port errors independently before increasing aggregate traffic. This action is relevant to Link aggregation and port error recovery, not the controlling requirement in this case. One healthy physical link is not proof an aggregate has balanced traffic or that the peer LACP policy matches. The targeted response is: Select a consistent supported MSTP region and intentional root-bridge placement for loop-free L2 redundancy.
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: Select a consistent supported MSTP region and intentional root-bridge placement for loop-free L2 redundancy.
Question 613
A field engineer uses standalone CLI instructions on a FortiGate-managed switch and its interface settings revert. Which diagnostic evidence should the FortiSwitch administrator examine FIRST?
- Inspect shared-port VLAN diff, tenant inventory, VDOM policy, change approval and representative positive/negative access tests.
- Inspect source MAC entries by VLAN, ingress/egress port, address aging, LAG membership and broadcast counters.
- Check route table, next-hop ARP, ingress VLAN, egress interface, prefix length and return-route path.
- Inspect FortiLink operational mode, controller ownership, current management address, VDOM and switch model support.
Explanation
Correct Answer
D:Inspect FortiLink operational mode, controller ownership, current management address, VDOM and switch model support. Direct edits on a managed switch can be overridden; standalone configuration must be maintained and backed up independently. The paired action is: Determine whether a switch is managed by FortiGate or standalone before setting interfaces, routes or admin policies.
Incorrect Answers
A:Inspect shared-port VLAN diff, tenant inventory, VDOM policy, change approval and representative positive/negative access tests. These observations are applicable to Multi-tenant change verification and rollback, but would not isolate the main failure first. The decisive evidence is: Inspect FortiLink operational mode, controller ownership, current management address, VDOM and switch model support.
B:Inspect source MAC entries by VLAN, ingress/egress port, address aging, LAG membership and broadcast counters. These observations are applicable to Layer 2 MAC-learning and forwarding decisions, but would not isolate the main failure first. The decisive evidence is: Inspect FortiLink operational mode, controller ownership, current management address, VDOM and switch model support.
C: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 FortiLink operational mode, controller ownership, current management address, VDOM and switch model support.
Question 614
After an unmanaged bridge is added, the same endpoint MAC repeatedly moves between ports and the team checks only DHCP leases. Which TWO complementary steps identify the appropriate FortiSwitch response AND the evidence needed to verify it? Select TWO.
- Correlate LLDP neighbor inventory and VLAN-specific MAC entries to reconstruct actual endpoint and uplink paths.
- Review filter minimization, capture duration, administrator authorization, sensitive payloads and evidence-sharing restrictions.
- Inspect local and neighbor port IDs, timestamp, learned MAC per VLAN, trunk member and expected cabling map.
- Collect relevant FortiSwitch controller diagnostics, switch system events and targeted status output before making configuration changes.
- The correct link establishes at expected negotiated rate without recurring loss-of-signal or CRC errors.
Explanation
Correct Answers
A:Correlate LLDP neighbor inventory and VLAN-specific MAC entries to reconstruct actual endpoint and uplink paths. LLDP provides adjacent-device identity, while MAC learning maps forwarding; neither is a full routed trace by itself. Verify the action with: Inspect local and neighbor port IDs, timestamp, learned MAC per VLAN, trunk member and expected cabling map. This is the configuration or remediation half of the requested TWO-step pair.
C:Inspect local and neighbor port IDs, timestamp, learned MAC per VLAN, trunk member and expected cabling map. LLDP provides adjacent-device identity, while MAC learning maps forwarding; neither is a full routed trace by itself. The paired action is: Correlate LLDP neighbor inventory and VLAN-specific MAC entries to reconstruct actual endpoint and uplink paths. This is the diagnostic or verification half of the requested TWO-step pair.
Incorrect Answers
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: Correlate LLDP neighbor inventory and VLAN-specific MAC entries to reconstruct actual endpoint and uplink paths. Together with: Inspect local and neighbor port IDs, timestamp, learned MAC per VLAN, trunk member and expected cabling map.
D:Collect relevant FortiSwitch controller diagnostics, switch system events and targeted status output before making configuration changes. This step concerns FortiSwitch diagnostic commands and logs and is not part of the required paired solution. The correct action and evidence are: Correlate LLDP neighbor inventory and VLAN-specific MAC entries to reconstruct actual endpoint and uplink paths. Together with: Inspect local and neighbor port IDs, timestamp, learned MAC per VLAN, trunk member and expected cabling map.
E:The correct link establishes at expected negotiated rate without recurring loss-of-signal or CRC errors. This step concerns Optic compatibility and laser diagnostic evidence and is not part of the required paired solution. The correct action and evidence are: Correlate LLDP neighbor inventory and VLAN-specific MAC entries to reconstruct actual endpoint and uplink paths. Together with: Inspect local and neighbor port IDs, timestamp, learned MAC per VLAN, trunk member and expected cabling map.
Question 615
A security role policy rejects sessions after a RADIUS change but no one examines switch authentication events. Which observable result BEST proves the intended FortiSwitch operation or security policy works?
- The suspected failure has a traceable event sequence and a specific evidence-based remediation candidate.
- A moved device is traced to its current approved port and incorrect cross-connection is identified.
- The failing physical or logical port is identified through reproducible counters rather than visual LED assumptions.
- The handset and attached workstation use the intended separate networks and retain their authorized access.
Explanation
Correct Answer
A:The suspected failure has a traceable event sequence and a specific evidence-based remediation candidate. A log message without source device, time and relevant state is not adequate to prove root cause.
Incorrect Answers
B:A moved device is traced to its current approved port and incorrect cross-connection is identified. This result relates to LLDP and MAC forwarding table extraction, not the acceptance condition under test. The relevant result is: The suspected failure has a traceable event sequence and a specific evidence-based remediation candidate.
C:The failing physical or logical port is identified through reproducible counters rather than visual LED assumptions. This result relates to Managed switch port statistics and counter analysis, not the acceptance condition under test. The relevant result is: The suspected failure has a traceable event sequence and a specific evidence-based remediation candidate.
D: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 suspected failure has a traceable event sequence and a specific evidence-based remediation candidate.
Question 616
An engineer moves a port into a different security group without verifying the FortiGate controller template. Which diagnostic evidence should the FortiSwitch administrator examine FIRST?
- Review firmware compatibility, release notes, current image, boot fallback, managed switch inventory and upgrade sequencing.
- Compare desired switch controller settings, switch synchronization indicators, port VLANs, user roles and post-reboot configuration.
- Review discovered/authorized controller inventory, switch serial, link state, approval method, reboot status and firmware compatibility.
- Inspect mirror direction, source and destination ports, speed constraints, physical capture link and switch statistics.
Explanation
Correct Answer
B:Compare desired switch controller settings, switch synchronization indicators, port VLANs, user roles and post-reboot configuration. Local changes on a FortiLink-managed switch can be discarded when the FortiGate controller reapplies its known configuration. The paired action is: Apply changes on the FortiGate controller and verify installed FortiSwitch state and reconciliation before rebooting.
Incorrect Answers
A: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: Compare desired switch controller settings, switch synchronization indicators, port VLANs, user roles and post-reboot configuration.
C: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: Compare desired switch controller settings, switch synchronization indicators, port VLANs, user roles and post-reboot configuration.
D:Inspect mirror direction, source and destination ports, speed constraints, physical capture link and switch statistics. These observations are applicable to FortiSwitch port mirroring to network analyzer, but would not isolate the main failure first. The decisive evidence is: Compare desired switch controller settings, switch synchronization indicators, port VLANs, user roles and post-reboot configuration.
Question 617
An access switch accidentally becomes root because its bridge priority is lower than planned core devices. Which FortiSwitch configuration or corrective action BEST addresses the requirement?
- Apply authorized device-class rules and dynamic port policies after confirming device detection evidence and fallback outcomes.
- Select a consistent supported MSTP region and intentional root-bridge placement for loop-free L2 redundancy.
- Use supported native and voice VLAN policies so phones and downstream workstations receive appropriate separate traffic treatment.
- Use compatible spanning-tree mode across connected switches and verify per-VLAN root and blocked links.
Explanation
Correct Answer
B:Select a consistent supported MSTP region and intentional root-bridge placement for loop-free L2 redundancy. Different MST configuration identifiers split regions even if switch ports are physically connected. Verify the action with: Review MST region name, revision, VLAN instance map, bridge priorities, root ID and topology-change counters.
Incorrect Answers
A:Apply authorized device-class rules and dynamic port policies after confirming device detection evidence and fallback outcomes. This action is relevant to NAC dynamic port policy device classification, not the controlling requirement in this case. NAC assignment relies on reliable detection and a defined precedence; a class label is not a substitute for switch-port policy. The targeted response is: Select a consistent supported MSTP region and intentional root-bridge placement for loop-free L2 redundancy.
C: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: Select a consistent supported MSTP region and intentional root-bridge placement for loop-free L2 redundancy.
D:Use compatible spanning-tree mode across connected switches and verify per-VLAN root and blocked links. This action is relevant to RPVST and supported STP mode interoperability, not the controlling requirement in this case. An STP mode change can change per-VLAN convergence behavior even if existing links remain physically up. The targeted response is: Select a consistent supported MSTP region and intentional root-bridge placement for loop-free L2 redundancy.
Question 618
An office switch is online in FortiGate but every new employee receives the wrong VLAN. 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 failed ISL or switch is isolated and recovered with all unaffected downstream switches remaining correctly managed.
- Authorized monitoring receives timely, interpretable switch evidence without exposing community strings or overwhelming CPU.
- A controlled failure test restores approved management and access connectivity through the designed redundant path.
Explanation
Correct Answer
A:Managed status remains healthy and user traffic uses only its intended FortiLink-carried VLANs. FortiLink transports management and data; a successful controller heartbeat does not guarantee a user VLAN or firewall session is permitted.
Incorrect Answers
B:The failed ISL or switch is isolated and recovered with all unaffected downstream switches remaining correctly managed. This result relates to Stack failure isolation and switch-to-switch port roles, not the acceptance condition under test. The relevant result is: Managed status remains healthy and user traffic uses only its intended FortiLink-carried VLANs.
C:Authorized monitoring receives timely, interpretable switch evidence without exposing community strings or overwhelming CPU. This result relates to SNMP and sFlow monitoring configuration, not the acceptance condition under test. The relevant result is: Managed status remains healthy and user traffic uses only its intended FortiLink-carried VLANs.
D:A controlled failure test restores approved management and access connectivity through the designed redundant path. This result relates to FortiLink HA and MCLAG topology faults, not the acceptance condition under test. The relevant result is: Managed status remains healthy and user traffic uses only its intended FortiLink-carried VLANs.
Question 619
The active FortiGate is restarted before the team verifies how managed-switch authorization behaves on the peer. Which diagnostic evidence should the FortiSwitch administrator examine FIRST?
- Inspect primary/secondary FortiGate roles, HA health, FortiLink uplinks, downstream switch topology and session continuity.
- Inspect supported topology, FortiLink p2p settings, TPID, transport reachability, discovery frames and switch firmware.
- Check switch PoE budget, port class, negotiated allocation, PSU state, LLDP-MED power TLV and port events.
- Check interface type, FortiLink enablement, discovery setting, IP assignment, switch model support, and management VLAN reachability.
Explanation
Correct Answer
A:Inspect primary/secondary FortiGate roles, HA health, FortiLink uplinks, downstream switch topology and session continuity. FortiGate HA design and FortiSwitch stacking/MCLAG are separate mechanisms; their failure paths must both be evaluated. The paired action is: Plan FortiLink management under FortiGate HA with supported links, peer roles and deterministic failover tests.
Incorrect Answers
B: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 primary/secondary FortiGate roles, HA health, FortiLink uplinks, downstream switch topology and session continuity.
C:Check switch PoE budget, port class, negotiated allocation, PSU state, LLDP-MED power TLV and port events. These observations are applicable to PoE and LLDP-MED endpoint power coordination, but would not isolate the main failure first. The decisive evidence is: Inspect primary/secondary FortiGate roles, HA health, FortiLink uplinks, downstream switch topology and session continuity.
D: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: Inspect primary/secondary FortiGate roles, HA health, FortiLink uplinks, downstream switch topology and session continuity.
Question 620
A shared FortiSwitch port carries two tenants but the controller creates both VLANs inside the wrong VDOM. Which FortiSwitch configuration or corrective action BEST addresses the requirement?
- Assign FortiSwitch VLANs and ports to the intended FortiGate VDOM with explicit isolation and governed shared infrastructure.
- Use supported FortiLink point-to-point L2 or Layer-3 transport configuration and validate discovery and control traffic end to end.
- Build a documented supported FortiSwitch daisy chain or multi-tier topology with adequate ISL uplink capacity and safeguards.
- Assign the intended untagged native VLAN and explicitly permit tagged VLANs on an uplink; compare both ends before cutover.
Explanation
Correct Answer
A:Assign FortiSwitch VLANs and ports to the intended FortiGate VDOM with explicit isolation and governed shared infrastructure. A VDOM creates a separate policy and routing context; it does not by itself make a shared physical switch port safe for all tenants. Verify the action with: Inspect controller VDOM ownership, VLAN interface parent, port mapping, session policy and IP/routing separation.
Incorrect Answers
B:Use supported FortiLink point-to-point L2 or Layer-3 transport configuration and validate discovery and control traffic end to end. This action is relevant to FortiLink transport over nontrivial L2 or L3 paths, not the controlling requirement in this case. FortiLink over intermediate networks requires topology-specific settings; ordinary IP reachability alone does not establish FortiLink discovery. The targeted response is: Assign FortiSwitch VLANs and ports to the intended FortiGate VDOM with explicit isolation and governed shared infrastructure.
C: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: Assign FortiSwitch VLANs and ports to the intended FortiGate VDOM with explicit isolation and governed shared infrastructure.
D:Assign the intended untagged native VLAN and explicitly permit tagged VLANs on an uplink; compare both ends before cutover. This action is relevant to FortiSwitch native VLAN versus allowed VLANs, not the controlling requirement in this case. Native VLAN handling and tagged VLAN membership are different controls; a working physical link does not validate VLAN carriage. The targeted response is: Assign FortiSwitch VLANs and ports to the intended FortiGate VDOM with explicit isolation and governed shared infrastructure.