cert
cert-1
cert-2

Pass Fortinet NSE5_FSW_AD-7.6 Exam in First Attempt Guaranteed!

Get 100% Latest Exam Questions, Accurate & Verified Answers to Pass the Actual Exam!
30 Days Free Updates, Instant Download!

cert-5
cert-6
NSE5_FSW_AD-7.6 Exam - Verified By Experts
NSE5_FSW_AD-7.6 Premium File

NSE5_FSW_AD-7.6 Premium File

$69.99
$76.99
  • Premium File 64 Questions & Answers. Last Update: Nov 15, 2026

Whats Included:

  • Latest Questions
  • 100% Accurate Answers
  • Fast Exam Updates
 
$76.99
$69.99
accept 42 downloads in the last 7 days
block-screenshots
Fortinet NSE5_FSW_AD-7.6 Practice Test 13

Question 120

An engineer enables legacy public read-write SNMP community strings to save time and exposes management data. Which TWO complementary steps identify the appropriate FortiSwitch response AND the evidence needed to verify it? Select TWO.

  1. Collect relevant FortiSwitch controller diagnostics, switch system events and targeted status output before making configuration changes.
  2. Inspect FortiGate HA active member, FortiLink aggregate state, ISL, MCLAG peer link, standby path and STP roles.
  3. Inspect monitoring credentials, SNMP version, sFlow export destination, sample rate, counter freshness and access policy.
  4. Critical telephony and wireless endpoints receive continuous intended power without overrunning PSU capacity.
  5. Collect supported SNMP or sFlow telemetry securely with appropriate collector authorization, sampling and interface scope.

Explanation

Correct Answers

C:

Inspect monitoring credentials, SNMP version, sFlow export destination, sample rate, counter freshness and access policy. Flow samples are estimates and counters vary by port; collecting telemetry cannot replace a controlled packet capture when headers are needed. The paired action is: Collect supported SNMP or sFlow telemetry securely with appropriate collector authorization, sampling and interface scope. This is the diagnostic or verification half of the requested TWO-step pair.

E:

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. This is the configuration or remediation half of the requested TWO-step pair.

Incorrect Answers

A:

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: Collect supported SNMP or sFlow telemetry securely with appropriate collector authorization, sampling and interface scope. Together with: Inspect monitoring credentials, SNMP version, sFlow export destination, sample rate, counter freshness and access policy.

B:

Inspect FortiGate HA active member, FortiLink aggregate state, ISL, MCLAG peer link, standby path and STP roles. This step concerns FortiLink HA and MCLAG topology faults and is not part of the required paired solution. The correct action and evidence are: Collect supported SNMP or sFlow telemetry securely with appropriate collector authorization, sampling and interface scope. Together with: Inspect monitoring credentials, SNMP version, sFlow export destination, sample rate, counter freshness and access policy.

D:

Critical telephony and wireless endpoints receive continuous intended power without overrunning PSU capacity. This step concerns Power over Ethernet port controls and budgets and is not part of the required paired solution. The correct action and evidence are: Collect supported SNMP or sFlow telemetry securely with appropriate collector authorization, sampling and interface scope. Together with: Inspect monitoring credentials, SNMP version, sFlow export destination, sample rate, counter freshness and access policy.

Question 121

A capture filter excludes ARP and the team incorrectly concludes the gateway has no address resolution activity. Which observable result BEST proves the intended FortiSwitch operation or security policy works?

  1. The failing physical or logical port is identified through reproducible counters rather than visual LED assumptions.
  2. A trace shows the expected ingress/egress control packets without collecting unrelated sensitive network traffic.
  3. FortiGate captures the suspected frames at the chosen observation point without altering the user traffic policy.
  4. Hosts can reach their intended SVI and authorized routed destinations without overlapping address space.

Explanation

Correct Answer

B:

A trace shows the expected ingress/egress control packets without collecting unrelated sensitive network traffic. Packet captures are interface and filter scoped, and platform buffer limits differ; a capture file is not proof of all traffic on every switch port.

Incorrect Answers

A:

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: A trace shows the expected ingress/egress control packets without collecting unrelated sensitive network traffic.

C:

FortiGate captures the suspected frames at the chosen observation point without altering the user traffic policy. This result relates to FortiGate one-arm sniffer across managed switching, not the acceptance condition under test. The relevant result is: A trace shows the expected ingress/egress control packets without collecting unrelated sensitive network traffic.

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: A trace shows the expected ingress/egress control packets without collecting unrelated sensitive network traffic.

Question 122

An administrator installs an ACL on the wrong ingress switch port and sees no change in affected traffic. Which FortiSwitch configuration or corrective action BEST addresses the requirement?

  1. Apply a specific restricted VLAN or quarantine mechanism with explicit authorized remediation and monitoring expectations.
  2. Apply supported switch ACL entries to targeted port or VLAN traffic with documented match, action, and policy sequence.
  3. Apply authorized device-class rules and dynamic port policies after confirming device detection evidence and fallback outcomes.
  4. Trace DHCP and ARP exchanges at ingress and uplink to distinguish missing requests from blocked or malformed responses.

Explanation

Correct Answer

B:

Apply supported switch ACL entries to targeted port or VLAN traffic with documented match, action, and policy sequence. Switch ACLs and FortiGate firewall policies operate at different enforcement points; a deny on one does not prove the other applied. Verify the action with: Review ACL direction and attachment, permit/drop rules, hit counters, supported match fields and resulting packet path.

Incorrect Answers

A:

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: Apply supported switch ACL entries to targeted port or VLAN traffic with documented match, action, and policy sequence.

C:

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: Apply supported switch ACL entries to targeted port or VLAN traffic with documented match, action, and policy sequence.

D:

Trace DHCP and ARP exchanges at ingress and uplink to distinguish missing requests from blocked or malformed responses. This action is relevant to Capture-based DHCP and ARP path isolation, not the controlling requirement in this case. A DHCP lease failure can originate at the client, switch, relay or server; capturing at one side alone is not always conclusive. The targeted response is: Apply supported switch ACL entries to targeted port or VLAN traffic with documented match, action, and policy sequence.

Question 123

A camera on VLAN 120 works locally but cannot reach its video recorder through an aggregation switch. Which TWO complementary steps identify the appropriate FortiSwitch response AND the evidence needed to verify it? Select TWO.

  1. Runaway flooding is contained without blocking legitimate broadcast-based onboarding or multicast subscribers.
  2. Trace MAC-learning and forwarding across the precise VLAN and repair only missing approved membership.
  3. Change managed switch VLAN membership through the FortiGate controller and verify the installed configuration stays consistent.
  4. Check managed topology view, controller switch state, ISL port counters, peer LLDP and suspected link events.
  5. Check client MAC learning, VLAN database, switch uplink tags, gateway ARP and port assignment on every hop.

Explanation

Correct Answers

B:

Trace MAC-learning and forwarding across the precise VLAN and repair only missing approved membership. Link up and successful traffic in one VLAN do not prove every VLAN is correctly provisioned on the path. Verify the action with: Check client MAC learning, VLAN database, switch uplink tags, gateway ARP and port assignment on every hop. This is the configuration or remediation half of the requested TWO-step pair.

E:

Check client MAC learning, VLAN database, switch uplink tags, gateway ARP and port assignment on every hop. Link up and successful traffic in one VLAN do not prove every VLAN is correctly provisioned on the path. The paired action is: Trace MAC-learning and forwarding across the precise VLAN and repair only missing approved membership. This is the diagnostic or verification half of the requested TWO-step pair.

Incorrect Answers

A:

Runaway flooding is contained without blocking legitimate broadcast-based onboarding or multicast subscribers. This step concerns Storm-control thresholds and broadcast containment and is not part of the required paired solution. The correct action and evidence are: Trace MAC-learning and forwarding across the precise VLAN and repair only missing approved membership. Together with: Check client MAC learning, VLAN database, switch uplink tags, gateway ARP and port assignment on every hop.

C:

Change managed switch VLAN membership through the FortiGate controller and verify the installed configuration stays consistent. This step concerns VLAN configuration persistence and drift control and is not part of the required paired solution. The correct action and evidence are: Trace MAC-learning and forwarding across the precise VLAN and repair only missing approved membership. Together with: Check client MAC learning, VLAN database, switch uplink tags, gateway ARP and port assignment on every hop.

D:

Check managed topology view, controller switch state, ISL port counters, peer LLDP and suspected link events. This step concerns Stack failure isolation and switch-to-switch port roles and is not part of the required paired solution. The correct action and evidence are: Trace MAC-learning and forwarding across the precise VLAN and repair only missing approved membership. Together with: Check client MAC learning, VLAN database, switch uplink tags, gateway ARP and port assignment on every hop.

Question 124

A staff laptop fails EAP-TLS because its certificate chain differs from the identity-server trust store. Which TWO complementary steps identify the appropriate FortiSwitch response AND the evidence needed to verify it? Select TWO.

  1. Inspect supplicant EAP exchange, RADIUS reachability, shared secret, port policy, authentication result and assigned access profile.
  2. Review target VLAN, switch isolation controls, client MAC table, permitted gateway path and peer-to-peer test.
  3. Configure supported IEEE 802.1X port security against an approved RADIUS service with explicit guest/unauthorized behavior.
  4. Enable IPv4 source guard on supported switch interfaces only with appropriate DHCP snooping or static bindings.
  5. The offending misassignment is corrected with both permitted traffic and forbidden cross-tenant traffic tested.

Explanation

Correct Answers

A:

Inspect supplicant EAP exchange, RADIUS reachability, shared secret, port policy, authentication result and assigned access profile. A physical link can be up while 802.1X blocks traffic; the switch is the authenticator, not the authentication server. The paired action is: Configure supported IEEE 802.1X port security against an approved RADIUS service with explicit guest/unauthorized behavior. This is the diagnostic or verification half of the requested TWO-step pair.

C:

Configure supported IEEE 802.1X port security against an approved RADIUS service with explicit guest/unauthorized behavior. A physical link can be up while 802.1X blocks traffic; the switch is the authenticator, not the authentication server. Verify the action with: Inspect supplicant EAP exchange, RADIUS reachability, shared secret, port policy, authentication result and assigned access profile. This is the configuration or remediation half of the requested TWO-step pair.

Incorrect Answers

B:

Review target VLAN, switch isolation controls, client MAC table, permitted gateway path and peer-to-peer test. This step concerns Intra-VLAN blocking and isolation boundaries and is not part of the required paired solution. The correct action and evidence are: Configure supported IEEE 802.1X port security against an approved RADIUS service with explicit guest/unauthorized behavior. Together with: Inspect supplicant EAP exchange, RADIUS reachability, shared secret, port policy, authentication result and assigned access profile.

D:

Enable IPv4 source guard on supported switch interfaces only with appropriate DHCP snooping or static bindings. This step concerns IPv4 source guard and binding-based packet filtering and is not part of the required paired solution. The correct action and evidence are: Configure supported IEEE 802.1X port security against an approved RADIUS service with explicit guest/unauthorized behavior. Together with: Inspect supplicant EAP exchange, RADIUS reachability, shared secret, port policy, authentication result and assigned access profile.

E:

The offending misassignment is corrected with both permitted traffic and forbidden cross-tenant traffic tested. This step concerns Managed tenant troubleshooting across controller and access layer and is not part of the required paired solution. The correct action and evidence are: Configure supported IEEE 802.1X port security against an approved RADIUS service with explicit guest/unauthorized behavior. Together with: Inspect supplicant EAP exchange, RADIUS reachability, shared secret, port policy, authentication result and assigned access profile.

Question 125

A long full-packet trace fills the device RAM disk and discards the earliest evidence during an incident. Which observable result BEST proves the intended FortiSwitch operation or security policy works?

  1. A trace shows the expected ingress/egress control packets without collecting unrelated sensitive network traffic.
  2. Troubleshooting evidence is sufficient to establish the fault without exporting unnecessary private communications.
  3. The intended tenant configuration changes while other tenants retain their segmentation and service.
  4. FortiGate captures the suspected frames at the chosen observation point without altering the user traffic policy.

Explanation

Correct Answer

A:

A trace shows the expected ingress/egress control packets without collecting unrelated sensitive network traffic. Packet captures are interface and filter scoped, and platform buffer limits differ; a capture file is not proof of all traffic on every switch port.

Incorrect Answers

B:

Troubleshooting evidence is sufficient to establish the fault without exporting unnecessary private communications. This result relates to Capture and confidentiality limits in incident response, not the acceptance condition under test. The relevant result is: A trace shows the expected ingress/egress control packets without collecting unrelated sensitive network traffic.

C:

The intended tenant configuration changes while other tenants retain their segmentation and service. This result relates to Multi-tenant change verification and rollback, not the acceptance condition under test. The relevant result is: A trace shows the expected ingress/egress control packets without collecting unrelated sensitive network traffic.

D:

FortiGate captures the suspected frames at the chosen observation point without altering the user traffic policy. This result relates to FortiGate one-arm sniffer across managed switching, not the acceptance condition under test. The relevant result is: A trace shows the expected ingress/egress control packets without collecting unrelated sensitive network traffic.

Question 126

A technician disables STP on one interswitch uplink because it shows blocking during normal redundancy. Which observable result BEST proves the intended FortiSwitch operation or security policy works?

  1. Every relevant VLAN converges without loops and redundant paths unblock only when needed.
  2. Each intended managed switch appears with valid upstream connectivity and no unintended layer-2 loop.
  3. The new FortiSwitch discovers the designated controller while unrelated FortiGate interfaces retain their normal function.
  4. An access host receives the right subnet while only approved tagged VLANs traverse the uplink.

Explanation

Correct Answer

A:

Every relevant VLAN converges without loops and redundant paths unblock only when needed. An STP mode change can change per-VLAN convergence behavior even if existing links remain physically up.

Incorrect Answers

B:

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: Every relevant VLAN converges without loops and redundant paths unblock only when needed.

C:

The new FortiSwitch discovers the designated controller while unrelated FortiGate interfaces retain their normal function. This result relates to FortiLink management interface provisioning, not the acceptance condition under test. The relevant result is: Every relevant VLAN converges without loops and redundant paths unblock only when needed.

D:

An access host receives the right subnet while only approved tagged VLANs traverse the uplink. This result relates to FortiSwitch native VLAN versus allowed VLANs, not the acceptance condition under test. The relevant result is: Every relevant VLAN converges without loops and redundant paths unblock only when needed.

Question 127

A previously used standalone switch never auto-discovers because its old configuration prevents expected default provisioning. Which TWO complementary steps identify the appropriate FortiSwitch response AND the evidence needed to verify it? Select TWO.

  1. Voice packets receive intended treatment without allowing arbitrary untrusted hosts to claim top priority.
  2. Inspect factory-default mode, DHCP or discovery exchange, upstream native VLAN, FortiLink enablement, NTP and controller authorization.
  3. Check managed tree, ISL link health, model compatibility, VLAN carriage, depth limitations and upstream aggregate status.
  4. Prepare supported provisioning, DHCP, management connectivity and secure bootstrap before assuming a factory-default FortiSwitch will auto-configure.
  5. Apply changes on the FortiGate controller and verify installed FortiSwitch state and reconciliation before rebooting.

Explanation

Correct Answers

B:

Inspect factory-default mode, DHCP or discovery exchange, upstream native VLAN, FortiLink enablement, NTP and controller authorization. Zero-touch deployment works only when the necessary discovery path and identity checks function; a link LED is insufficient. The paired action is: Prepare supported provisioning, DHCP, management connectivity and secure bootstrap before assuming a factory-default FortiSwitch will auto-configure. This is the diagnostic or verification half of the requested TWO-step pair.

D:

Prepare supported provisioning, DHCP, management connectivity and secure bootstrap before assuming a factory-default FortiSwitch will auto-configure. Zero-touch deployment works only when the necessary discovery path and identity checks function; a link LED is insufficient. Verify the action with: Inspect factory-default mode, DHCP or discovery exchange, upstream native VLAN, FortiLink enablement, NTP and controller authorization. This is the configuration or remediation half of the requested TWO-step pair.

Incorrect Answers

A:

Voice packets receive intended treatment without allowing arbitrary untrusted hosts to claim top priority. This step concerns QoS ingress classification and trust boundaries and is not part of the required paired solution. The correct action and evidence are: Prepare supported provisioning, DHCP, management connectivity and secure bootstrap before assuming a factory-default FortiSwitch will auto-configure. Together with: Inspect factory-default mode, DHCP or discovery exchange, upstream native VLAN, FortiLink enablement, NTP and controller authorization.

C:

Check managed tree, ISL link health, model compatibility, VLAN carriage, depth limitations and upstream aggregate status. This step concerns FortiSwitch multi-tier managed topology and is not part of the required paired solution. The correct action and evidence are: Prepare supported provisioning, DHCP, management connectivity and secure bootstrap before assuming a factory-default FortiSwitch will auto-configure. Together with: Inspect factory-default mode, DHCP or discovery exchange, upstream native VLAN, FortiLink enablement, NTP and controller authorization.

E:

Apply changes on the FortiGate controller and verify installed FortiSwitch state and reconciliation before rebooting. This step concerns Managed switch configuration synchronization and is not part of the required paired solution. The correct action and evidence are: Prepare supported provisioning, DHCP, management connectivity and secure bootstrap before assuming a factory-default FortiSwitch will auto-configure. Together with: Inspect factory-default mode, DHCP or discovery exchange, upstream native VLAN, FortiLink enablement, NTP and controller authorization.

Question 128

An approved static-IP server is blocked because its switch port lacks a binding entry after enabling source guard. Which FortiSwitch configuration or corrective action BEST addresses the requirement?

  1. Enable supported DHCP snooping on client VLANs and trust only known DHCP-server or relay-facing links.
  2. Use documented trusted DHCP-server lists or Option 82 information where supported to enforce authorized address assignment.
  3. Use supported FortiLink point-to-point L2 or Layer-3 transport configuration and validate discovery and control traffic end to end.
  4. Enable IPv4 source guard on supported switch interfaces only with appropriate DHCP snooping or static bindings.

Explanation

Correct Answer

D:

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.

Incorrect Answers

A:

Enable supported DHCP snooping on client VLANs and trust only known DHCP-server or relay-facing links. This action is relevant to DHCP snooping trust-boundary enforcement, not the controlling requirement in this case. Trusting every port defeats DHCP snooping and wrongly distrusting the server uplink may suppress all leases. The targeted response is: Enable IPv4 source guard on supported switch interfaces only with appropriate DHCP snooping or static bindings.

B:

Use documented trusted DHCP-server lists or Option 82 information where supported to enforce authorized address assignment. This action is relevant to DHCP server allowlist and Option 82 validation, not the controlling requirement in this case. DHCP server allowlist and Option 82 metadata provide additional context but cannot correct a failed VLAN or missing upstream relay. The targeted response is: Enable IPv4 source guard on supported switch interfaces only with appropriate DHCP snooping or static bindings.

C:

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: Enable IPv4 source guard on supported switch interfaces only with appropriate DHCP snooping or static bindings.

Question 129

A badge printer cannot run an EAP supplicant and is given an unrestricted staff VLAN rather than a limited MAC-auth profile. Which FortiSwitch configuration or corrective action BEST addresses the requirement?

  1. Use supported dynamic ARP inspection with valid switch bindings to reject spoofed IP-MAC claims at untrusted edges.
  2. Apply authorized device-class rules and dynamic port policies after confirming device detection evidence and fallback outcomes.
  3. Use supported MAC-based access controls with narrow authorized device roles and avoid treating MAC addresses as strong identity proof.
  4. Plan S-VLAN and C-VLAN mapping with the correct FortiLink VDOM and platform support for tenant-tagged traffic.

Explanation

Correct Answer

C:

Use supported MAC-based access controls with narrow authorized device roles and avoid treating MAC addresses as strong identity proof. A MAC address can be cloned; MAC authentication must be combined with appropriate segmentation and monitoring. Verify the action with: Check learned client MAC, RADIUS MAC authentication response, access policy, fallback sequence and effective VLAN.

Incorrect Answers

A:

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: Use supported MAC-based access controls with narrow authorized device roles and avoid treating MAC addresses as strong identity proof.

B:

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: Use supported MAC-based access controls with narrow authorized device roles and avoid treating MAC addresses as strong identity proof.

D:

Plan S-VLAN and C-VLAN mapping with the correct FortiLink VDOM and platform support for tenant-tagged traffic. This action is relevant to QinQ outer and inner VLAN tenant mapping, not the controlling requirement in this case. QinQ layering and VDOM assignment are separate controls; wrong outer tagging can mix customers even when inner VLAN IDs differ. The targeted response is: Use supported MAC-based access controls with narrow authorized device roles and avoid treating MAC addresses as strong identity proof.

Question 130

A printer is moved to a new patch panel but its MAC keeps appearing on an old trunk member. Which observable result BEST proves the intended FortiSwitch operation or security policy works?

  1. Only intended networks are reachable through the configured route and the return path remains valid.
  2. The authenticated client receives the intended per-user or per-port restrictions and unauthenticated hosts do not inherit them.
  3. Known unicast traffic reaches the correct access port while unknown traffic is confined to the intended VLAN.
  4. A redundant topology recovers after a link failure without simultaneous independent forwarding paths causing loops.

Explanation

Correct Answer

C:

Known unicast traffic reaches the correct access port while unknown traffic is confined to the intended VLAN. An L2 switch uses MAC destination and VLAN state for forwarding; a healthy SVI is not proof a host is on the proper port.

Incorrect Answers

A:

Only intended networks are reachable through the configured route and the return path remains valid. This result relates to Static route and default gateway validation, not the acceptance condition under test. The relevant result is: Known unicast traffic reaches the correct access port while unknown traffic is confined to the intended VLAN.

B:

The authenticated client receives the intended per-user or per-port restrictions and unauthenticated hosts do not inherit them. This result relates to DACL RADIUS attribute and per-session enforcement, not the acceptance condition under test. The relevant result is: Known unicast traffic reaches the correct access port while unknown traffic is confined to the intended VLAN.

D:

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: Known unicast traffic reaches the correct access port while unknown traffic is confined to the intended VLAN.

Fortinet NSE 5 - FortiSwitch 7.6 Administrator (NSE5_FSW_AD-7.6) Practice Tests