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

Question 570

A technician says “Investigate rogue DHCP offer logs” has solved the issue at the media studio. Which diagnostic step would substantiate that claim?

  1. Compare a client's address and MAC with the active binding database
  2. Compare current port trust, VLAN snooping enablement and the revised cabling diagram
  3. Compare ARP inspection statistics for the endpoint port and the relevant VLAN
  4. Correlate the rogue-server event with VLAN, port and packet source MAC
  5. Read the active binding after the move and compare it with the client's new port

Explanation

Correct Answer

D:

The critical distinction is that DHCP snooping can log the arrival of DHCP server packets on untrusted interfaces. Directly measuring that result demonstrates whether the step to locate an untrusted server attached to a client-facing port succeeded on a central switching stack.

Incorrect Answers

A:

The proposed check concerns “Use the DHCP-snooping binding table” rather than “Investigate rogue DHCP offer logs”: snooping records lease-derived bindings that other protections can reference. For “Investigate rogue DHCP offer logs” on a central switching stack, a better test would be to correlate the rogue-server event with VLAN, port and packet source MAC, which targets locate an untrusted server attached to a client-facing port rather than the alternative diagnostic “Use the DHCP-snooping binding table”.

B:

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 “Investigate rogue DHCP offer logs” at the media studio. Checking “Investigate rogue DHCP offer logs” at the media studio requires evidence of its own mechanism: DHCP snooping can log the arrival of DHCP server packets on untrusted interfaces; that is not the outcome measured by “Audit DHCP snooping after VLAN redesign”.

C:

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 “Investigate rogue DHCP offer logs” at the media studio. Checking “Investigate rogue DHCP offer logs” at the media studio requires evidence of its own mechanism: DHCP snooping can log the arrival of DHCP server packets on untrusted interfaces; that is not the outcome measured by “Keep DAI untrusted on endpoint interfaces”.

E:

The proposed check concerns “Check DHCP-derived bindings for IP source guard” rather than “Investigate rogue DHCP offer logs”: dynamic source-guard entries depend on valid snooping bindings for the interface and source identity. For “Investigate rogue DHCP offer logs” on a central switching stack, a better test would be to correlate the rogue-server event with VLAN, port and packet source MAC, which targets locate an untrusted server attached to a client-facing port rather than the alternative diagnostic “Check DHCP-derived bindings for IP source guard”.

Question 571

A switch rollout in the retail site will be approved only if it can avoid unintentionally permitting server traffic on newly repurposed host uplinks. Which administrative action meets this acceptance criterion?

  1. Audit DHCP snooping after VLAN redesign
  2. Trust only the uplink toward a legitimate DHCP server
  3. Use MAC-based VLAN classification
  4. Create a static DHCP-snooping binding for a fixed-IP host

Explanation

Correct Answer

A:

That setting is appropriate here because snooping configuration must follow actual VLAN membership and trusted-port boundaries. This distinction is material to the retail site, where the stated goal is to avoid unintentionally permitting server traffic on newly repurposed host uplinks.

Incorrect Answers

B:

Compared with the requested “Audit DHCP snooping after VLAN redesign” at the retail site, 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 retail site, the operational proof would instead be to compare current port trust, VLAN snooping enablement and the revised cabling diagram, 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.

C:

Compared with the requested “Audit DHCP snooping after VLAN redesign” at the retail site, this would assign a known endpoint to its designated VLAN independent of the access-port default instead: MAC-based VLAN policies identify permitted source MAC addresses and map them to VLANs. At the retail site, the operational proof would instead be to compare current port trust, VLAN snooping enablement and the revised cabling diagram, whereas “Use MAC-based VLAN classification” is validated by a different test: inspect the device MAC and the associated VLAN mapping rule.

D:

For the retail site, “Create a static DHCP-snooping binding for a fixed-IP host” is a different type of control from “Audit DHCP snooping after VLAN redesign”: a static port/IP/MAC binding supplies known information for binding-aware protections. Unlike the requested feature, that setting addresses the need to protect an endpoint whose address was not learned through a DHCP lease, not the objective to avoid unintentionally permitting server traffic on newly repurposed host uplinks.

Question 572

A colleague asks about the effect of “Audit DHCP snooping after VLAN redesign” on an access switch in routine maintenance. Which behavior best characterizes that feature?

  1. Untrusted ARP senders must match the permitted binding state to be forwarded
  2. Snooping configuration must follow actual VLAN membership and trusted-port boundaries
  3. Snooping records lease-derived bindings that other protections can reference
  4. Dynamic source-guard entries depend on valid snooping bindings for the interface and source identity

Explanation

Correct Answer

B:

This is the precise control because the configured operation is meant to avoid unintentionally permitting server traffic on newly repurposed host uplinks. The most relevant validation is to compare current port trust, VLAN snooping enablement and the revised cabling diagram for the equipment at the airport office.

Incorrect Answers

A:

This outcome would be relevant to “Keep DAI untrusted on endpoint interfaces” at the airport office, not the task “Audit DHCP snooping after VLAN redesign”; the other task is to verify ARP statements made by clients rather than exempting them from inspection. The action “Audit DHCP snooping after VLAN redesign” targets a different result: snooping configuration must follow actual VLAN membership and trusted-port boundaries; the proposed alternative would instead be checked by compare ARP inspection statistics for the endpoint port and the relevant VLAN.

C:

That behavior applies when engineers “Use the DHCP-snooping binding table”; the different operation “Audit DHCP snooping after VLAN redesign” is intended to avoid unintentionally permitting server traffic on newly repurposed host uplinks. That different feature is verified by compare a client's address and MAC with the active binding database; for “Audit DHCP snooping after VLAN redesign” on an access switch in routine maintenance, the relevant evidence is to compare current port trust, VLAN snooping enablement and the revised cabling diagram.

D:

That behavior applies when engineers “Check DHCP-derived bindings for IP source guard”; the different operation “Audit DHCP snooping after VLAN redesign” is intended to avoid unintentionally permitting server traffic on newly repurposed host uplinks. That different feature is verified by read the active binding after the move and compare it with the client's new port; for “Audit DHCP snooping after VLAN redesign” on an access switch in routine maintenance, the relevant evidence is to compare current port trust, VLAN snooping enablement and the revised cabling diagram.

Question 573

At the operations center, a dashboard shows ordinary link-up state, but the team also needs proof for “Audit DHCP snooping after VLAN redesign.” Which targeted check should be used?

  1. Compare observed frame rates with the selected per-port storm-control threshold
  2. Compare current port trust, VLAN snooping enablement and the revised cabling diagram
  3. Compare a client's address and MAC with the active binding database
  4. Correlate the rogue-server event with VLAN, port and packet source MAC
  5. Review ARP trust state on the uplink and confirm that host ports remain untrusted

Explanation

Correct Answer

B:

The implementation works because snooping configuration must follow actual VLAN membership and trusted-port boundaries. Directly measuring that result demonstrates whether the step to avoid unintentionally permitting server traffic on newly repurposed host uplinks succeeded on a newly racked distribution unit.

Incorrect Answers

A:

The proposed check concerns “Set a storm-control threshold appropriate to link capacity” rather than “Audit DHCP snooping after VLAN redesign”: a configured rate threshold distinguishes permitted traffic load from a sustained storm. For “Audit DHCP snooping after VLAN redesign” on a newly racked distribution unit, a better test would be to compare current port trust, VLAN snooping enablement and the revised cabling diagram, which targets avoid unintentionally permitting server traffic on newly repurposed host uplinks rather than the alternative diagnostic “Set a storm-control threshold appropriate to link capacity”.

C:

The proposed check concerns “Use the DHCP-snooping binding table” rather than “Audit DHCP snooping after VLAN redesign”: snooping records lease-derived bindings that other protections can reference. For “Audit DHCP snooping after VLAN redesign” on a newly racked distribution unit, a better test would be to compare current port trust, VLAN snooping enablement and the revised cabling diagram, which targets avoid unintentionally permitting server traffic on newly repurposed host uplinks rather than the alternative diagnostic “Use the DHCP-snooping binding table”.

D:

This check is suited to “Investigate rogue DHCP offer logs” when trying to locate an untrusted server attached to a client-facing port, not to verify “Audit DHCP snooping after VLAN redesign” at the operations center. Checking “Audit DHCP snooping after VLAN redesign” at the operations center requires evidence of its own mechanism: snooping configuration must follow actual VLAN membership and trusted-port boundaries; that is not the outcome measured by “Investigate rogue DHCP offer logs”.

E:

This check is suited to “Trust an infrastructure port for ARP inspection when justified” when trying to avoid inspecting ARP coming from an explicitly trusted network segment, not to verify “Audit DHCP snooping after VLAN redesign” at the operations center. Checking “Audit DHCP snooping after VLAN redesign” at the operations center requires evidence of its own mechanism: snooping configuration must follow actual VLAN membership and trusted-port boundaries; that is not the outcome measured by “Trust an infrastructure port for ARP inspection when justified”.

Question 574

An administrator responsible for two distribution switches in the warehouse must protect both IPv4 data-source integrity and ARP neighbor claims using the appropriate separate controls. Which configuration best matches that precise goal?

  1. Keep DAI untrusted on endpoint interfaces
  2. Check DHCP-derived bindings for IP source guard
  3. Use the DHCP-snooping binding table
  4. Avoid using source guard as an ARP-only inspection replacement

Explanation

Correct Answer

D:

Given the described goal, IPSG filters IPv4 packet sources while DAI validates ARP IP/MAC statements; they address different packet classes. The operator can test this claim by the specific check: capture whether the spoof is ordinary IPv4 payload traffic or ARP control traffic.

Incorrect Answers

A:

Compared with the requested “Avoid using source guard as an ARP-only inspection replacement” at the warehouse, 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 warehouse, the operational proof would instead be to capture whether the spoof is ordinary IPv4 payload traffic or ARP control traffic, 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.

B:

For the warehouse, “Check DHCP-derived bindings for IP source guard” is a different type of control from “Avoid using source guard as an ARP-only inspection replacement”: dynamic source-guard entries depend on valid snooping bindings for the interface and source identity. Unlike the requested feature, that setting addresses the need to explain why a recently moved DHCP client loses permitted IPv4 connectivity, not the objective to protect both IPv4 data-source integrity and ARP neighbor claims using the appropriate separate controls.

C:

Compared with the requested “Avoid using source guard as an ARP-only inspection replacement” at the warehouse, this would associate leased IPv4 identities with particular MAC addresses and ports instead: snooping records lease-derived bindings that other protections can reference. At the warehouse, the operational proof would instead be to capture whether the spoof is ordinary IPv4 payload traffic or ARP control traffic, whereas “Use the DHCP-snooping binding table” is validated by a different test: compare a client's address and MAC with the active binding database.

Question 575

When engineers avoid using source guard as an ARP-only inspection replacement at the headquarters, which forwarding, security, management or diagnostic outcome follows from that action?

  1. A configured rate threshold distinguishes permitted traffic load from a sustained storm
  2. IPSG filters IPv4 packet sources while DAI validates ARP IP/MAC statements; they address different packet classes
  3. The switch can designate trusted ARP interfaces when the network design warrants an exception
  4. DHCP snooping can log the arrival of DHCP server packets on untrusted interfaces

Explanation

Correct Answer

B:

The switch behavior that matters is: the configured operation is meant to protect both IPv4 data-source integrity and ARP neighbor claims using the appropriate separate controls. The most relevant validation is to capture whether the spoof is ordinary IPv4 payload traffic or ARP control traffic for the equipment at the headquarters.

Incorrect Answers

A:

This outcome would be relevant to “Set a storm-control threshold appropriate to link capacity” at the headquarters, not the task “Avoid using source guard as an ARP-only inspection replacement”; the other task is to contain traffic bursts without discarding ordinary service announcements. The action “Avoid using source guard as an ARP-only inspection replacement” targets a different result: IPSG filters IPv4 packet sources while DAI validates ARP IP/MAC statements; they address different packet classes; the proposed alternative would instead be checked by compare observed frame rates with the selected per-port storm-control threshold.

C:

That behavior applies when engineers “Trust an infrastructure port for ARP inspection when justified”; the different operation “Avoid using source guard as an ARP-only inspection replacement” is intended to protect both IPv4 data-source integrity and ARP neighbor claims using the appropriate separate controls. That different feature is verified by review ARP trust state on the uplink and confirm that host ports remain untrusted; for “Avoid using source guard as an ARP-only inspection replacement” on a staging FortiSwitch, the relevant evidence is to capture whether the spoof is ordinary IPv4 payload traffic or ARP control traffic.

D:

That behavior applies when engineers “Investigate rogue DHCP offer logs”; the different operation “Avoid using source guard as an ARP-only inspection replacement” is intended to protect both IPv4 data-source integrity and ARP neighbor claims using the appropriate separate controls. That different feature is verified by correlate the rogue-server event with VLAN, port and packet source MAC; for “Avoid using source guard as an ARP-only inspection replacement” on a staging FortiSwitch, the relevant evidence is to capture whether the spoof is ordinary IPv4 payload traffic or ARP control traffic.

Question 576

A production incident in the hospital wing reveals the need to filter packets as they enter a FortiSwitch forwarding pipeline. Which targeted FortiSwitch setting or method should the team use?

  1. Keep ACL group priority ordering consistent
  2. Install an egress ACL for outgoing traffic
  3. Install an ingress ACL for received traffic
  4. Apply a QoS action using an ACL

Explanation

Correct Answer

C:

At this network boundary, an ingress ACL classifies traffic arriving at an interface and applies permitted hardware actions. The operator can test this claim by the specific check: review ingress ACL match counters while sending matching test frames.

Incorrect Answers

A:

For the hospital wing, “Keep ACL group priority ordering consistent” is a different type of control from “Install an ingress ACL for received traffic”: for conflicting group actions, the lower-numbered ACL group has higher action priority. Unlike the requested feature, that setting addresses the need to resolve conflicting actions when several ACL groups match the same packet, not the objective to filter packets as they enter a FortiSwitch forwarding pipeline.

B:

Compared with the requested “Install an ingress ACL for received traffic” at the hospital wing, this would apply a traffic filter after traffic has been selected for an output interface instead: an egress-stage policy acts on frames being transmitted rather than their original entry classification. At the hospital wing, the operational proof would instead be to review ingress ACL match counters while sending matching test frames, whereas “Install an egress ACL for outgoing traffic” is validated by a different test: inspect egress ACL counters for the relevant outgoing port.

D:

Compared with the requested “Install an ingress ACL for received traffic” at the hospital wing, this would prioritize a defined class without requiring every endpoint to mark itself instead: ACL actions can assign supported classification or priority treatment to matching frames. At the hospital wing, the operational proof would instead be to review ingress ACL match counters while sending matching test frames, whereas “Apply a QoS action using an ACL” is validated by a different test: inspect ACL match counters and resulting QoS queue handling.

Question 577

When engineers install an ingress ACL for received traffic at the factory, which forwarding, security, management or diagnostic outcome follows from that action?

  1. Switch ACL classifiers, groups and counters consume finite hardware resources that can be fragmented
  2. An EtherType comparison identifies the payload protocol without relying on TCP/UDP port numbers
  3. Community PVLAN members can communicate with their own community and the promiscuous primary port
  4. An ingress ACL classifies traffic arriving at an interface and applies permitted hardware actions
  5. A drop action discards frames meeting the ACL match rather than disabling the whole physical port

Explanation

Correct Answer

D:

In this deployment, the configured operation is meant to filter packets as they enter a FortiSwitch forwarding pipeline. The most relevant validation is to review ingress ACL match counters while sending matching test frames for the equipment at the factory.

Incorrect Answers

A:

That behavior applies when engineers “Review the ACL hardware resource usage”; the different operation “Install an ingress ACL for received traffic” is intended to filter packets as they enter a FortiSwitch forwarding pipeline. That different feature is verified by inspect ACL usage and available hardware entries before changing rule order; for “Install an ingress ACL for received traffic” on a central switching stack, the relevant evidence is to review ingress ACL match counters while sending matching test frames.

B:

That behavior applies when engineers “Use an ACL Ethernet-type classifier”; the different operation “Install an ingress ACL for received traffic” is intended to filter packets as they enter a FortiSwitch forwarding pipeline. That different feature is verified by read the EtherType from the frame header and inspect the ACL service match; for “Install an ingress ACL for received traffic” on a central switching stack, the relevant evidence is to review ingress ACL match counters while sending matching test frames.

C:

This outcome would be relevant to “Apply a community secondary PVLAN to one workgroup” at the factory, not the task “Install an ingress ACL for received traffic”; the other task is to allow peers within one designated group to communicate but isolate them from other groups. The action “Install an ingress ACL for received traffic” targets a different result: an ingress ACL classifies traffic arriving at an interface and applies permitted hardware actions; the proposed alternative would instead be checked by test peer reachability inside the community and deny a connection to a different community.

E:

That behavior applies when engineers “Drop matched unwanted frames with an ACL action”; the different operation “Install an ingress ACL for received traffic” is intended to filter packets as they enter a FortiSwitch forwarding pipeline. That different feature is verified by confirm matching test packets are counted and discarded while unrelated traffic still passes; for “Install an ingress ACL for received traffic” on a central switching stack, the relevant evidence is to review ingress ACL match counters while sending matching test frames.

Question 578

A post-change review at the distribution floor must validate the implementation of “Install an ingress ACL for received traffic.” What should the reviewer inspect first?

  1. Check prelookup stage configuration and rule-use counters
  2. Capture the double-tagged frame and verify distinct S-tag and customer C-tag fields
  3. Review ingress ACL match counters while sending matching test frames
  4. Inspect policer conformance/excess statistics alongside ACL counters

Explanation

Correct Answer

C:

For the stated requirement, an ingress ACL classifies traffic arriving at an interface and applies permitted hardware actions. Directly measuring that result demonstrates whether the step to filter packets as they enter a FortiSwitch forwarding pipeline succeeded on a FortiSwitch connected to the security edge.

Incorrect Answers

A:

The proposed check concerns “Use prelookup ACL classification” rather than “Install an ingress ACL for received traffic”: a prelookup ACL applies available classifiers at its pipeline stage; it is not a route-table entry. For “Install an ingress ACL for received traffic” on a FortiSwitch connected to the security edge, a better test would be to review ingress ACL match counters while sending matching test frames, which targets filter packets as they enter a FortiSwitch forwarding pipeline rather than the alternative diagnostic “Use prelookup ACL classification”.

B:

This check is suited to “Use an 802.1Q QinQ outer service VLAN” when trying to transport independently numbered customer VLANs through provider infrastructure, not to verify “Install an ingress ACL for received traffic” at the distribution floor. Checking “Install an ingress ACL for received traffic” at the distribution floor requires evidence of its own mechanism: an ingress ACL classifies traffic arriving at an interface and applies permitted hardware actions; that is not the outcome measured by “Use an 802.1Q QinQ outer service VLAN”.

D:

This check is suited to “Apply an ACL policer to matching frames” when trying to rate-control selected traffic rather than dropping every matching packet, not to verify “Install an ingress ACL for received traffic” at the distribution floor. Checking “Install an ingress ACL for received traffic” at the distribution floor requires evidence of its own mechanism: an ingress ACL classifies traffic arriving at an interface and applies permitted hardware actions; that is not the outcome measured by “Apply an ACL policer to matching frames”.

Question 579

The operational requirement for an access switch in routine maintenance at the media studio is to apply a traffic filter after traffic has been selected for an output interface. Which FortiSwitch choice directly targets it?

  1. Use selective packet sampling where supported
  2. Install an egress ACL for outgoing traffic
  3. Use an 802.1Q QinQ outer service VLAN
  4. Use prelookup ACL classification

Explanation

Correct Answer

B:

The deciding detail is that an egress-stage policy acts on frames being transmitted rather than their original entry classification. This distinction is material to the media studio, where the stated goal is to apply a traffic filter after traffic has been selected for an output interface.

Incorrect Answers

A:

Compared with the requested “Install an egress ACL for outgoing traffic” at the media studio, this would gather representative traffic metadata without mirroring every packet instead: sampling selects a subset of matching packets for observation while forwarding rules remain in effect. At the media studio, the operational proof would instead be to inspect egress ACL counters for the relevant outgoing port, whereas “Use selective packet sampling where supported” is validated by a different test: check the sampling configuration and resulting observed packet frequency.

C:

Compared with the requested “Install an egress ACL for outgoing traffic” at the media studio, this would transport independently numbered customer VLANs through provider infrastructure instead: VLAN stacking adds an outer service tag while preserving the customer's internal VLAN identifier. At the media studio, the operational proof would instead be to inspect egress ACL counters for the relevant outgoing port, whereas “Use an 802.1Q QinQ outer service VLAN” is validated by a different test: capture the double-tagged frame and verify distinct S-tag and customer C-tag fields.

D:

For the media studio, “Use prelookup ACL classification” is a different type of control from “Install an egress ACL for outgoing traffic”: a prelookup ACL applies available classifiers at its pipeline stage; it is not a route-table entry. Unlike the requested feature, that setting addresses the need to match traffic in an early processing stage before subsequent forwarding decisions, not the objective to apply a traffic filter after traffic has been selected for an output interface.

Question 580

Before applying the planned operation “Install an egress ACL for outgoing traffic” at the retail site, the administrator must predict its impact. Which prediction is sound?

  1. An egress-stage policy acts on frames being transmitted rather than their original entry classification
  2. An IP source or destination prefix classifier restricts the match to packets meeting the configured address condition
  3. Time-based ACL scheduling controls policy applicability, not the device system clock itself
  4. MAC-to-VLAN mapping is based on source identity and differs from general ACL drop actions

Explanation

Correct Answer

A:

The relevant mechanism is: the configured operation is meant to apply a traffic filter after traffic has been selected for an output interface. The most relevant validation is to inspect egress ACL counters for the relevant outgoing port for the equipment at the retail site.

Incorrect Answers

B:

This outcome would be relevant to “Match an ACL using an IP subnet” at the retail site, not the task “Install an egress ACL for outgoing traffic”; the other task is to filter traffic from a designated routed network range. The action “Install an egress ACL for outgoing traffic” targets a different result: an egress-stage policy acts on frames being transmitted rather than their original entry classification; the proposed alternative would instead be checked by compare captured source/destination IP fields and the rule's mask.

C:

That behavior applies when engineers “Configure an ACL schedule”; the different operation “Install an egress ACL for outgoing traffic” is intended to apply a traffic filter after traffic has been selected for an output interface. That different feature is verified by compare current FortiSwitch time with the configured schedule and observed rule counters; for “Install an egress ACL for outgoing traffic” on a managed campus switch, the relevant evidence is to inspect egress ACL counters for the relevant outgoing port.

D:

That behavior applies when engineers “Use a MAC-based VLAN security association”; the different operation “Install an egress ACL for outgoing traffic” is intended to apply a traffic filter after traffic has been selected for an output interface. That different feature is verified by compare the source MAC with the VLAN-assignment entry and effective port VLAN membership; for “Install an egress ACL for outgoing traffic” on a managed campus switch, the relevant evidence is to inspect egress ACL counters for the relevant outgoing port.

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