Fortinet NSE5_FSW_AD-7.6 (Fortinet NSE 5 - FortiSwitch 7.6 Administrator) Practice Test 56

Question 550

For the training center, the network team needs to limit disruption from excessive broadcast, multicast or unknown-unicast traffic. Which change is the most direct way to implement that requirement on a switch serving a high-density endpoint area?

  1. Set a storm-control threshold appropriate to link capacity
  2. Investigate rogue DHCP offer logs
  3. Enable DHCP snooping before dynamic ARP inspection
  4. Use storm control on a broadcast-heavy access port

Explanation

Correct Answer

D:

Given the described goal, storm control rate-limits selected Layer 2 traffic categories at a switch port. The operator can test this claim by the specific check: read storm-control counters during the observed high-rate event.

Incorrect Answers

A:

Compared with the requested “Use storm control on a broadcast-heavy access port” at the training center, this would contain traffic bursts without discarding ordinary service announcements instead: a configured rate threshold distinguishes permitted traffic load from a sustained storm. At the training center, the operational proof would instead be to read storm-control counters during the observed high-rate event, whereas “Set a storm-control threshold appropriate to link capacity” is validated by a different test: compare observed frame rates with the selected per-port storm-control threshold.

B:

For the training center, “Investigate rogue DHCP offer logs” is a different type of control from “Use storm control on a broadcast-heavy access port”: DHCP snooping can log the arrival of DHCP server packets on untrusted interfaces. Unlike the requested feature, that setting addresses the need to locate an untrusted server attached to a client-facing port, not the objective to limit disruption from excessive broadcast, multicast or unknown-unicast traffic.

C:

Compared with the requested “Use storm control on a broadcast-heavy access port” at the training center, this would provide the binding information DAI needs for validating ARP on client networks instead: Fortinet requires DHCP snooping to be configured before enabling DAI for the VLAN. At the training center, the operational proof would instead be to read storm-control counters during the observed high-rate event, whereas “Enable DHCP snooping before dynamic ARP inspection” is validated by a different test: check both the VLAN's DHCP snooping setting and DAI enablement.

Question 551

A change record for a managed switch running FortiSwitchOS 7.6 states “Use storm control on a broadcast-heavy access port.” Which description correctly explains what this will accomplish?

  1. Storm control rate-limits selected Layer 2 traffic categories at a switch port
  2. IPSG filters IPv4 packet sources while DAI validates ARP IP/MAC statements; they address different packet classes
  3. Server whitelisting can narrow acceptable DHCP sources beyond the physical trust-port arrangement
  4. Protocol-based classification maps matching frame protocol to the configured VLAN policy
  5. Fortinet requires DHCP snooping to be configured before enabling DAI for the VLAN

Explanation

Correct Answer

A:

The switch behavior that matters is: the configured operation is meant to limit disruption from excessive broadcast, multicast or unknown-unicast traffic. The most relevant validation is to read storm-control counters during the observed high-rate event for the equipment at the lab.

Incorrect Answers

B:

This outcome would be relevant to “Avoid using source guard as an ARP-only inspection replacement” at the lab, not the task “Use storm control on a broadcast-heavy access port”; the other task is to protect both IPv4 data-source integrity and ARP neighbor claims using the appropriate separate controls. The action “Use storm control on a broadcast-heavy access port” targets a different result: storm control rate-limits selected Layer 2 traffic categories at a switch port; the proposed alternative would instead be checked by capture whether the spoof is ordinary IPv4 payload traffic or ARP control traffic.

C:

That behavior applies when engineers “Configure an authorized DHCP server list”; the different operation “Use storm control on a broadcast-heavy access port” is intended to limit disruption from excessive broadcast, multicast or unknown-unicast traffic. That different feature is verified by inspect the configured allowlist and observe whether an unlisted server offer is accepted; for “Use storm control on a broadcast-heavy access port” on a managed switch running FortiSwitchOS 7.6, the relevant evidence is to read storm-control counters during the observed high-rate event.

D:

That behavior applies when engineers “Use protocol-based VLAN classification”; the different operation “Use storm control on a broadcast-heavy access port” is intended to limit disruption from excessive broadcast, multicast or unknown-unicast traffic. That different feature is verified by capture a packet's EtherType and compare it with protocol-VLAN policy entries; for “Use storm control on a broadcast-heavy access port” on a managed switch running FortiSwitchOS 7.6, the relevant evidence is to read storm-control counters during the observed high-rate event.

E:

That behavior applies when engineers “Enable DHCP snooping before dynamic ARP inspection”; the different operation “Use storm control on a broadcast-heavy access port” is intended to limit disruption from excessive broadcast, multicast or unknown-unicast traffic. That different feature is verified by check both the VLAN's DHCP snooping setting and DAI enablement; for “Use storm control on a broadcast-heavy access port” on a managed switch running FortiSwitchOS 7.6, the relevant evidence is to read storm-control counters during the observed high-rate event.

Question 552

The change-control ticket for a remote FortiSwitch installation requires one validation of the goal to limit disruption from excessive broadcast, multicast or unknown-unicast traffic. Which evidence should be collected?

  1. Check configured trusted interfaces and the source port of DHCP offers
  2. Inspect the configured static binding and verify the endpoint's actual source identity
  3. Read storm-control counters during the observed high-rate event
  4. Compare the source IP of rejected traffic with the allowed binding set

Explanation

Correct Answer

C:

At this network boundary, storm control rate-limits selected Layer 2 traffic categories at a switch port. Directly measuring that result demonstrates whether the step to limit disruption from excessive broadcast, multicast or unknown-unicast traffic succeeded on a remote FortiSwitch installation.

Incorrect Answers

A:

This check is suited to “Trust only the uplink toward a legitimate DHCP server” when trying to allow server responses on an approved infrastructure-facing interface, not to verify “Use storm control on a broadcast-heavy access port” at the staging rack. Checking “Use storm control on a broadcast-heavy access port” at the staging rack requires evidence of its own mechanism: storm control rate-limits selected Layer 2 traffic categories at a switch port; that is not the outcome measured by “Trust only the uplink toward a legitimate DHCP server”.

B:

The proposed check concerns “Create a static DHCP-snooping binding for a fixed-IP host” rather than “Use storm control on a broadcast-heavy access port”: a static port/IP/MAC binding supplies known information for binding-aware protections. For “Use storm control on a broadcast-heavy access port” on a remote FortiSwitch installation, a better test would be to read storm-control counters during the observed high-rate event, which targets limit disruption from excessive broadcast, multicast or unknown-unicast traffic rather than the alternative diagnostic “Create a static DHCP-snooping binding for a fixed-IP host”.

D:

This check is suited to “Enable IPv4 source guard on an access port” when trying to discard host IP packets that use source addresses not authorized for that interface, not to verify “Use storm control on a broadcast-heavy access port” at the staging rack. Checking “Use storm control on a broadcast-heavy access port” at the staging rack requires evidence of its own mechanism: storm control rate-limits selected Layer 2 traffic categories at a switch port; that is not the outcome measured by “Enable IPv4 source guard on an access port”.

Question 553

On an endpoint-facing FortiSwitch port in the research building, the next task is to contain traffic bursts without discarding ordinary service announcements. What is the appropriate configuration decision?

  1. Create a static DHCP-snooping binding for a fixed-IP host
  2. Enable IPv4 source guard on an access port
  3. Trust only the uplink toward a legitimate DHCP server
  4. Set a storm-control threshold appropriate to link capacity

Explanation

Correct Answer

D:

In this deployment, a configured rate threshold distinguishes permitted traffic load from a sustained storm. This distinction is material to the research building, where the stated goal is to contain traffic bursts without discarding ordinary service announcements.

Incorrect Answers

A:

Compared with the requested “Set a storm-control threshold appropriate to link capacity” at the research building, this would protect an endpoint whose address was not learned through a DHCP lease instead: a static port/IP/MAC binding supplies known information for binding-aware protections. At the research building, the operational proof would instead be to compare observed frame rates with the selected per-port storm-control threshold, whereas “Create a static DHCP-snooping binding for a fixed-IP host” is validated by a different test: inspect the configured static binding and verify the endpoint's actual source identity.

B:

For the research building, “Enable IPv4 source guard on an access port” is a different type of control from “Set a storm-control threshold appropriate to link capacity”: IP source guard matches IPv4 origin against static or DHCP-snooping-learned source bindings. Unlike the requested feature, that setting addresses the need to discard host IP packets that use source addresses not authorized for that interface, not the objective to contain traffic bursts without discarding ordinary service announcements.

C:

Compared with the requested “Set a storm-control threshold appropriate to link capacity” at the research building, this would allow server responses on an approved infrastructure-facing interface instead: a DHCP-snooping trusted port may convey legitimate server replies while host-facing ports remain untrusted. At the research building, the operational proof would instead be to compare observed frame rates with the selected per-port storm-control threshold, whereas “Trust only the uplink toward a legitimate DHCP server” is validated by a different test: check configured trusted interfaces and the source port of DHCP offers.

Question 554

An operations log records this activity at the clinic: set a storm-control threshold appropriate to link capacity. Which result is specifically attributable to that action?

  1. Dynamic source-guard entries depend on valid snooping bindings for the interface and source identity
  2. Untrusted ARP senders must match the permitted binding state to be forwarded
  3. A configured rate threshold distinguishes permitted traffic load from a sustained storm
  4. Source subnet classification uses IP address information to select a configured VLAN association

Explanation

Correct Answer

C:

For the stated requirement, the configured operation is meant to contain traffic bursts without discarding ordinary service announcements. The most relevant validation is to compare observed frame rates with the selected per-port storm-control threshold for the equipment at the clinic.

Incorrect Answers

A:

This outcome would be relevant to “Check DHCP-derived bindings for IP source guard” at the clinic, not the task “Set a storm-control threshold appropriate to link capacity”; the other task is to explain why a recently moved DHCP client loses permitted IPv4 connectivity. The action “Set a storm-control threshold appropriate to link capacity” targets a different result: a configured rate threshold distinguishes permitted traffic load from a sustained storm; the proposed alternative would instead be checked by read the active binding after the move and compare it with the client's new port.

B:

That behavior applies when engineers “Keep DAI untrusted on endpoint interfaces”; the different operation “Set a storm-control threshold appropriate to link capacity” is intended to contain traffic bursts without discarding ordinary service announcements. That different feature is verified by compare ARP inspection statistics for the endpoint port and the relevant VLAN; for “Set a storm-control threshold appropriate to link capacity” on a standalone FortiSwitch appliance, the relevant evidence is to compare observed frame rates with the selected per-port storm-control threshold.

D:

That behavior applies when engineers “Use IP-subnet-based VLAN assignment”; the different operation “Set a storm-control threshold appropriate to link capacity” is intended to contain traffic bursts without discarding ordinary service announcements. That different feature is verified by compare received source IP with configured IP-based VLAN mapping; for “Set a storm-control threshold appropriate to link capacity” on a standalone FortiSwitch appliance, the relevant evidence is to compare observed frame rates with the selected per-port storm-control threshold.

Question 555

A FortiSwitch engineer in the data hall is documenting successful operation of “Set a storm-control threshold appropriate to link capacity.” Which measurement or inspection confirms it?

  1. Compare observed frame rates with the selected per-port storm-control threshold
  2. Capture unauthorized ICMPv6 router advertisements and monitor guard drops
  3. Compare a client's address and MAC with the active binding database
  4. Compare current port trust, VLAN snooping enablement and the revised cabling diagram
  5. Compare ARP inspection statistics for the endpoint port and the relevant VLAN

Explanation

Correct Answer

A:

The deciding detail is that a configured rate threshold distinguishes permitted traffic load from a sustained storm. Directly measuring that result demonstrates whether the step to contain traffic bursts without discarding ordinary service announcements succeeded on a newly commissioned floor switch.

Incorrect Answers

B:

This check is suited to “Apply IPv6 RA guard where supported” when trying to block unauthorized IPv6 router advertisements on user-facing ports, not to verify “Set a storm-control threshold appropriate to link capacity” at the data hall. Checking “Set a storm-control threshold appropriate to link capacity” at the data hall requires evidence of its own mechanism: a configured rate threshold distinguishes permitted traffic load from a sustained storm; that is not the outcome measured by “Apply IPv6 RA guard where supported”.

C:

This check is suited to “Use the DHCP-snooping binding table” when trying to associate leased IPv4 identities with particular MAC addresses and ports, not to verify “Set a storm-control threshold appropriate to link capacity” at the data hall. Checking “Set a storm-control threshold appropriate to link capacity” at the data hall requires evidence of its own mechanism: a configured rate threshold distinguishes permitted traffic load from a sustained storm; that is not the outcome measured by “Use the DHCP-snooping binding table”.

D:

The proposed check concerns “Audit DHCP snooping after VLAN redesign” rather than “Set a storm-control threshold appropriate to link capacity”: snooping configuration must follow actual VLAN membership and trusted-port boundaries. For “Set a storm-control threshold appropriate to link capacity” on a newly commissioned floor switch, a better test would be to compare observed frame rates with the selected per-port storm-control threshold, which targets contain traffic bursts without discarding ordinary service announcements rather than the alternative diagnostic “Audit DHCP snooping after VLAN redesign”.

E:

The proposed check concerns “Keep DAI untrusted on endpoint interfaces” rather than “Set a storm-control threshold appropriate to link capacity”: untrusted ARP senders must match the permitted binding state to be forwarded. For “Set a storm-control threshold appropriate to link capacity” on a newly commissioned floor switch, a better test would be to compare observed frame rates with the selected per-port storm-control threshold, which targets contain traffic bursts without discarding ordinary service announcements rather than the alternative diagnostic “Keep DAI untrusted on endpoint interfaces”.

Question 556

At the warehouse, a technician is choosing between several switching features to block unauthorized IPv6 router advertisements on user-facing ports. Which one belongs in the implementation plan?

  1. Use protocol-based VLAN classification
  2. Apply IPv6 RA guard where supported
  3. Enable IPv4 source guard on an access port
  4. Create a static DHCP-snooping binding for a fixed-IP host

Explanation

Correct Answer

B:

The relevant mechanism is: RA guard filters IPv6 router advertisements originating from untrusted switch access links. The operator can test this claim by the specific check: capture unauthorized ICMPv6 router advertisements and monitor guard drops.

Incorrect Answers

A:

For the warehouse, “Use protocol-based VLAN classification” is a different type of control from “Apply IPv6 RA guard where supported”: protocol-based classification maps matching frame protocol to the configured VLAN policy. Unlike the requested feature, that setting addresses the need to assign inbound traffic to a VLAN based on its protocol identifier when required, not the objective to block unauthorized IPv6 router advertisements on user-facing ports.

C:

Compared with the requested “Apply IPv6 RA guard where supported” at the warehouse, this would discard host IP packets that use source addresses not authorized for that interface instead: IP source guard matches IPv4 origin against static or DHCP-snooping-learned source bindings. At the warehouse, the operational proof would instead be to capture unauthorized ICMPv6 router advertisements and monitor guard drops, whereas “Enable IPv4 source guard on an access port” is validated by a different test: compare the source IP of rejected traffic with the allowed binding set.

D:

Compared with the requested “Apply IPv6 RA guard where supported” at the warehouse, this would protect an endpoint whose address was not learned through a DHCP lease instead: a static port/IP/MAC binding supplies known information for binding-aware protections. At the warehouse, the operational proof would instead be to capture unauthorized ICMPv6 router advertisements and monitor guard drops, whereas “Create a static DHCP-snooping binding for a fixed-IP host” is validated by a different test: inspect the configured static binding and verify the endpoint's actual source identity.

Question 557

A change record for a switch used by multiple office teams states “Apply IPv6 RA guard where supported.” Which description correctly explains what this will accomplish?

  1. A DHCP-snooping trusted port may convey legitimate server replies while host-facing ports remain untrusted
  2. RA guard filters IPv6 router advertisements originating from untrusted switch access links
  3. Source subnet classification uses IP address information to select a configured VLAN association
  4. Dynamic source-guard entries depend on valid snooping bindings for the interface and source identity

Explanation

Correct Answer

B:

This approach fits because the configured operation is meant to block unauthorized IPv6 router advertisements on user-facing ports. The most relevant validation is to capture unauthorized ICMPv6 router advertisements and monitor guard drops for the equipment at the headquarters.

Incorrect Answers

A:

That behavior applies when engineers “Trust only the uplink toward a legitimate DHCP server”; the different operation “Apply IPv6 RA guard where supported” is intended to block unauthorized IPv6 router advertisements on user-facing ports. That different feature is verified by check configured trusted interfaces and the source port of DHCP offers; for “Apply IPv6 RA guard where supported” on a switch used by multiple office teams, the relevant evidence is to capture unauthorized ICMPv6 router advertisements and monitor guard drops.

C:

This outcome would be relevant to “Use IP-subnet-based VLAN assignment” at the headquarters, not the task “Apply IPv6 RA guard where supported”; the other task is to assign traffic from recognized source IPv4 subnets to specific VLANs where supported. The action “Apply IPv6 RA guard where supported” targets a different result: RA guard filters IPv6 router advertisements originating from untrusted switch access links; the proposed alternative would instead be checked by compare received source IP with configured IP-based VLAN mapping.

D:

That behavior applies when engineers “Check DHCP-derived bindings for IP source guard”; the different operation “Apply IPv6 RA guard where supported” is intended to block unauthorized IPv6 router advertisements on user-facing ports. That different feature is verified by read the active binding after the move and compare it with the client's new port; for “Apply IPv6 RA guard where supported” on a switch used by multiple office teams, the relevant evidence is to capture unauthorized ICMPv6 router advertisements and monitor guard drops.

Question 558

A feature acceptance test on a production FortiSwitch fabric concerns “Apply IPv6 RA guard where supported.” What should be checked to establish its expected operation?

  1. Capture unauthorized ICMPv6 router advertisements and monitor guard drops
  2. Compare ARP inspection statistics for the endpoint port and the relevant VLAN
  3. Compare a client's address and MAC with the active binding database
  4. Compare current port trust, VLAN snooping enablement and the revised cabling diagram

Explanation

Correct Answer

A:

The critical distinction is that RA guard filters IPv6 router advertisements originating from untrusted switch access links. Directly measuring that result demonstrates whether the step to block unauthorized IPv6 router advertisements on user-facing ports succeeded on a production FortiSwitch fabric.

Incorrect Answers

B:

This check is suited to “Keep DAI untrusted on endpoint interfaces” when trying to verify ARP statements made by clients rather than exempting them from inspection, not to verify “Apply IPv6 RA guard where supported” at the hospital wing. Checking “Apply IPv6 RA guard where supported” at the hospital wing requires evidence of its own mechanism: RA guard filters IPv6 router advertisements originating from untrusted switch access links; that is not the outcome measured by “Keep DAI untrusted on endpoint interfaces”.

C:

The proposed check concerns “Use the DHCP-snooping binding table” rather than “Apply IPv6 RA guard where supported”: snooping records lease-derived bindings that other protections can reference. For “Apply IPv6 RA guard where supported” on a production FortiSwitch fabric, a better test would be to capture unauthorized ICMPv6 router advertisements and monitor guard drops, which targets block unauthorized IPv6 router advertisements on user-facing ports rather than the alternative diagnostic “Use the DHCP-snooping binding table”.

D:

This check is suited to “Audit DHCP snooping after VLAN redesign” when trying to avoid unintentionally permitting server traffic on newly repurposed host uplinks, not to verify “Apply IPv6 RA guard where supported” at the hospital wing. Checking “Apply IPv6 RA guard where supported” at the hospital wing requires evidence of its own mechanism: RA guard filters IPv6 router advertisements originating from untrusted switch access links; that is not the outcome measured by “Audit DHCP snooping after VLAN redesign”.

Question 559

The accepted design for the training center requires the ability to assign inbound traffic to a VLAN based on its protocol identifier when required. Which switch feature is the closest fit?

  1. Use protocol-based VLAN classification
  2. Keep DAI untrusted on endpoint interfaces
  3. Use the DHCP-snooping binding table
  4. Audit DHCP snooping after VLAN redesign
  5. Set a storm-control threshold appropriate to link capacity

Explanation

Correct Answer

A:

That setting is appropriate here because protocol-based classification maps matching frame protocol to the configured VLAN policy. This distinction is material to the training center, where the stated goal is to assign inbound traffic to a VLAN based on its protocol identifier when required.

Incorrect Answers

B:

Compared with the requested “Use protocol-based VLAN classification” at the training center, this would verify ARP statements made by clients rather than exempting them from inspection instead: untrusted ARP senders must match the permitted binding state to be forwarded. At the training center, the operational proof would instead be to capture a packet's EtherType and compare it with protocol-VLAN policy entries, whereas “Keep DAI untrusted on endpoint interfaces” is validated by a different test: compare ARP inspection statistics for the endpoint port and the relevant VLAN.

C:

For the training center, “Use the DHCP-snooping binding table” is a different type of control from “Use protocol-based VLAN classification”: snooping records lease-derived bindings that other protections can reference. Unlike the requested feature, that setting addresses the need to associate leased IPv4 identities with particular MAC addresses and ports, not the objective to assign inbound traffic to a VLAN based on its protocol identifier when required.

D:

Compared with the requested “Use protocol-based VLAN classification” at the training center, this would avoid unintentionally permitting server traffic on newly repurposed host uplinks instead: snooping configuration must follow actual VLAN membership and trusted-port boundaries. At the training center, the operational proof would instead be to capture a packet's EtherType and compare it with protocol-VLAN policy entries, whereas “Audit DHCP snooping after VLAN redesign” is validated by a different test: compare current port trust, VLAN snooping enablement and the revised cabling diagram.

E:

Compared with the requested “Use protocol-based VLAN classification” at the training center, this would contain traffic bursts without discarding ordinary service announcements instead: a configured rate threshold distinguishes permitted traffic load from a sustained storm. At the training center, the operational proof would instead be to capture a packet's EtherType and compare it with protocol-VLAN policy entries, whereas “Set a storm-control threshold appropriate to link capacity” is validated by a different test: compare observed frame rates with the selected per-port storm-control threshold.

Question 560

An operations log records this activity at the lab: use protocol-based VLAN classification. Which result is specifically attributable to that action?

  1. Protocol-based classification maps matching frame protocol to the configured VLAN policy
  2. DHCP snooping checks DHCP packets on the VLAN and builds trusted IP-to-MAC lease bindings
  3. The switch can designate trusted ARP interfaces when the network design warrants an exception
  4. Option 82 carries relay-agent information such as circuit and remote identifiers toward the DHCP infrastructure

Explanation

Correct Answer

A:

This is the precise control because the configured operation is meant to assign inbound traffic to a VLAN based on its protocol identifier when required. The most relevant validation is to capture a packet's EtherType and compare it with protocol-VLAN policy entries for the equipment at the lab.

Incorrect Answers

B:

That behavior applies when engineers “Enable DHCP snooping on an access VLAN”; the different operation “Use protocol-based VLAN classification” is intended to assign inbound traffic to a VLAN based on its protocol identifier when required. That different feature is verified by inspect DHCP snooping status and the learned bindings for that VLAN; for “Use protocol-based VLAN classification” on an endpoint-facing FortiSwitch port, the relevant evidence is to capture a packet's EtherType and compare it with protocol-VLAN policy entries.

C:

That behavior applies when engineers “Trust an infrastructure port for ARP inspection when justified”; the different operation “Use protocol-based VLAN classification” is intended to assign inbound traffic to a VLAN based on its protocol identifier when required. That different feature is verified by review ARP trust state on the uplink and confirm that host ports remain untrusted; for “Use protocol-based VLAN classification” on an endpoint-facing FortiSwitch port, the relevant evidence is to capture a packet's EtherType and compare it with protocol-VLAN policy entries.

D:

This outcome would be relevant to “Include DHCP option 82 for relay-agent context” at the lab, not the task “Use protocol-based VLAN classification”; the other task is to identify the access circuit or switch involved in a DHCP client request. The action “Use protocol-based VLAN classification” targets a different result: protocol-based classification maps matching frame protocol to the configured VLAN policy; the proposed alternative would instead be checked by capture a forwarded DHCP discover and inspect its option-82 fields.

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