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

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.

Question 581

The work order to apply a traffic filter after traffic has been selected for an output interface is marked complete on a recently upgraded FortiSwitch. Which observation most directly tests the completed configuration?

  1. Inspect matching rules by ACL group and compare their group numbers
  2. Confirm matching test packets are counted and discarded while unrelated traffic still passes
  3. Inspect egress ACL counters for the relevant outgoing port
  4. Inspect protocol classifier order and the VLAN ID assigned to matching traffic
  5. Inspect ACL match counters and resulting QoS queue handling
  6. Compare the captured Ethernet source address with the ACL match value

Explanation

Correct Answer

C:

This approach fits because an egress-stage policy acts on frames being transmitted rather than their original entry classification. Directly measuring that result demonstrates whether the step to apply a traffic filter after traffic has been selected for an output interface succeeded on a recently upgraded FortiSwitch.

Incorrect Answers

A:

The proposed check concerns “Keep ACL group priority ordering consistent” rather than “Install an egress ACL for outgoing traffic”: for conflicting group actions, the lower-numbered ACL group has higher action priority. For “Install an egress ACL for outgoing traffic” on a recently upgraded FortiSwitch, a better test would be to inspect egress ACL counters for the relevant outgoing port, which targets apply a traffic filter after traffic has been selected for an output interface rather than the alternative diagnostic “Keep ACL group priority ordering consistent”.

B:

This check is suited to “Drop matched unwanted frames with an ACL action” when trying to block a targeted source or protocol using explicit hardware filtering, not to verify “Install an egress ACL for outgoing traffic” at the airport office. Checking “Install an egress ACL for outgoing traffic” at the airport office requires evidence of its own mechanism: an egress-stage policy acts on frames being transmitted rather than their original entry classification; that is not the outcome measured by “Drop matched unwanted frames with an ACL action”.

D:

This check is suited to “Configure a protocol-based VLAN ACL where needed” when trying to classify a defined payload type into a separate forwarding VLAN, not to verify “Install an egress ACL for outgoing traffic” at the airport office. Checking “Install an egress ACL for outgoing traffic” at the airport office requires evidence of its own mechanism: an egress-stage policy acts on frames being transmitted rather than their original entry classification; that is not the outcome measured by “Configure a protocol-based VLAN ACL where needed”.

E:

This check is suited to “Apply a QoS action using an ACL” when trying to prioritize a defined class without requiring every endpoint to mark itself, not to verify “Install an egress ACL for outgoing traffic” at the airport office. Checking “Install an egress ACL for outgoing traffic” at the airport office requires evidence of its own mechanism: an egress-stage policy acts on frames being transmitted rather than their original entry classification; that is not the outcome measured by “Apply a QoS action using an ACL”.

F:

The proposed check concerns “Match a FortiSwitch ACL by source MAC address” rather than “Install an egress ACL for outgoing traffic”: the layer-2 source MAC classifier selects packets by the originating address at the configured ACL stage. For “Install an egress ACL for outgoing traffic” on a recently upgraded FortiSwitch, a better test would be to inspect egress ACL counters for the relevant outgoing port, which targets apply a traffic filter after traffic has been selected for an output interface rather than the alternative diagnostic “Match a FortiSwitch ACL by source MAC address”.

Question 582

During a change window in the operations center, engineers are asked to match traffic in an early processing stage before subsequent forwarding decisions. What should they configure rather than using a feature for an adjacent purpose?

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

Explanation

Correct Answer

C:

The critical distinction is that a prelookup ACL applies available classifiers at its pipeline stage; it is not a route-table entry. The operator can test this claim by the specific check: check prelookup stage configuration and rule-use counters.

Incorrect Answers

A:

For the operations center, “Install an egress ACL for outgoing traffic” is a different type of control from “Use prelookup ACL classification”: an egress-stage policy acts on frames being transmitted rather than their original entry classification. Unlike the requested feature, that setting addresses the need to apply a traffic filter after traffic has been selected for an output interface, not the objective to match traffic in an early processing stage before subsequent forwarding decisions.

B:

Compared with the requested “Use prelookup ACL classification” at the operations center, 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 operations center, the operational proof would instead be to check prelookup stage configuration and rule-use counters, 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:

Compared with the requested “Use prelookup ACL classification” at the operations center, 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 operations center, the operational proof would instead be to check prelookup stage configuration and rule-use counters, whereas “Use selective packet sampling where supported” is validated by a different test: check the sampling configuration and resulting observed packet frequency.

Question 583

During validation of a switch linked to a FortiGate running FortiOS 7.6 at the warehouse, the team asks what the change “Use prelookup ACL classification” actually does. Which outcome is correct?

  1. A prelookup ACL applies available classifiers at its pipeline stage; it is not a route-table entry
  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:

That setting is appropriate here because the configured operation is meant to match traffic in an early processing stage before subsequent forwarding decisions. The most relevant validation is to check prelookup stage configuration and rule-use counters for the equipment at the warehouse.

Incorrect Answers

B:

This outcome would be relevant to “Match an ACL using an IP subnet” at the warehouse, not the task “Use prelookup ACL classification”; the other task is to filter traffic from a designated routed network range. The action “Use prelookup ACL classification” targets a different result: a prelookup ACL applies available classifiers at its pipeline stage; it is not a route-table entry; 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 “Use prelookup ACL classification” is intended to match traffic in an early processing stage before subsequent forwarding decisions. That different feature is verified by compare current FortiSwitch time with the configured schedule and observed rule counters; for “Use prelookup ACL classification” on a switch linked to a FortiGate running FortiOS 7.6, the relevant evidence is to check prelookup stage configuration and rule-use counters.

D:

That behavior applies when engineers “Use a MAC-based VLAN security association”; the different operation “Use prelookup ACL classification” is intended to match traffic in an early processing stage before subsequent forwarding decisions. That different feature is verified by compare the source MAC with the VLAN-assignment entry and effective port VLAN membership; for “Use prelookup ACL classification” on a switch linked to a FortiGate running FortiOS 7.6, the relevant evidence is to check prelookup stage configuration and rule-use counters.

Question 584

A technician says “Use prelookup ACL classification” has solved the issue at the remote depot. Which diagnostic step would substantiate that claim?

  1. Inspect matching rules by ACL group and compare their group numbers
  2. Inspect protocol classifier order and the VLAN ID assigned to matching traffic
  3. Compare the captured Ethernet source address with the ACL match value
  4. Inspect ACL match counters and resulting QoS queue handling
  5. Check prelookup stage configuration and rule-use counters

Explanation

Correct Answer

E:

This is the precise control because a prelookup ACL applies available classifiers at its pipeline stage; it is not a route-table entry. Directly measuring that result demonstrates whether the step to match traffic in an early processing stage before subsequent forwarding decisions succeeded on a switch serving a high-density endpoint area.

Incorrect Answers

A:

The proposed check concerns “Keep ACL group priority ordering consistent” rather than “Use prelookup ACL classification”: for conflicting group actions, the lower-numbered ACL group has higher action priority. For “Use prelookup ACL classification” on a switch serving a high-density endpoint area, a better test would be to check prelookup stage configuration and rule-use counters, which targets match traffic in an early processing stage before subsequent forwarding decisions rather than the alternative diagnostic “Keep ACL group priority ordering consistent”.

B:

This check is suited to “Configure a protocol-based VLAN ACL where needed” when trying to classify a defined payload type into a separate forwarding VLAN, not to verify “Use prelookup ACL classification” at the remote depot. Checking “Use prelookup ACL classification” at the remote depot requires evidence of its own mechanism: a prelookup ACL applies available classifiers at its pipeline stage; it is not a route-table entry; that is not the outcome measured by “Configure a protocol-based VLAN ACL where needed”.

C:

The proposed check concerns “Match a FortiSwitch ACL by source MAC address” rather than “Use prelookup ACL classification”: the layer-2 source MAC classifier selects packets by the originating address at the configured ACL stage. For “Use prelookup ACL classification” on a switch serving a high-density endpoint area, a better test would be to check prelookup stage configuration and rule-use counters, which targets match traffic in an early processing stage before subsequent forwarding decisions rather than the alternative diagnostic “Match a FortiSwitch ACL by source MAC address”.

D:

This check is suited to “Apply a QoS action using an ACL” when trying to prioritize a defined class without requiring every endpoint to mark itself, not to verify “Use prelookup ACL classification” at the remote depot. Checking “Use prelookup ACL classification” at the remote depot requires evidence of its own mechanism: a prelookup ACL applies available classifiers at its pipeline stage; it is not a route-table entry; that is not the outcome measured by “Apply a QoS action using an ACL”.

Question 585

For the branch office, the network team needs to limit an Ethernet policy to frames from a specific hardware address. Which change is the most direct way to implement that requirement on a managed switch running FortiSwitchOS 7.6?

  1. Install an egress ACL for outgoing traffic
  2. Match a FortiSwitch ACL by source MAC address
  3. Apply an ACL policer to matching frames
  4. Use an 802.1Q QinQ outer service VLAN

Explanation

Correct Answer

B:

The implementation works because the layer-2 source MAC classifier selects packets by the originating address at the configured ACL stage. This distinction is material to the branch office, where the stated goal is to limit an Ethernet policy to frames from a specific hardware address.

Incorrect Answers

A:

Compared with the requested “Match a FortiSwitch ACL by source MAC address” at the branch office, 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 branch office, the operational proof would instead be to compare the captured Ethernet source address with the ACL match value, whereas “Install an egress ACL for outgoing traffic” is validated by a different test: inspect egress ACL counters for the relevant outgoing port.

C:

For the branch office, “Apply an ACL policer to matching frames” is a different type of control from “Match a FortiSwitch ACL by source MAC address”: a linked policer enforces meter behavior for the matched ACL class. Unlike the requested feature, that setting addresses the need to rate-control selected traffic rather than dropping every matching packet, not the objective to limit an Ethernet policy to frames from a specific hardware address.

D:

Compared with the requested “Match a FortiSwitch ACL by source MAC address” at the branch office, 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 branch office, the operational proof would instead be to compare the captured Ethernet source address with the ACL match value, 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.

Question 586

Before applying the planned operation “Match a FortiSwitch ACL by source MAC address” at the factory, the administrator must predict its impact. Which prediction is sound?

  1. The layer-2 source MAC classifier selects packets by the originating address at the configured ACL stage
  2. Time-based ACL scheduling controls policy applicability, not the device system clock itself
  3. The promiscuous port connects secondary VLANs to the common routed or shared service endpoint
  4. An IP source or destination prefix classifier restricts the match to packets meeting the configured address condition

Explanation

Correct Answer

A:

Given the described goal, the configured operation is meant to limit an Ethernet policy to frames from a specific hardware address. The most relevant validation is to compare the captured Ethernet source address with the ACL match value for the equipment at the factory.

Incorrect Answers

B:

This outcome would be relevant to “Configure an ACL schedule” at the factory, not the task “Match a FortiSwitch ACL by source MAC address”; the other task is to enforce a selected match/action only during approved operational hours. The action “Match a FortiSwitch ACL by source MAC address” targets a different result: the layer-2 source MAC classifier selects packets by the originating address at the configured ACL stage; the proposed alternative would instead be checked by compare current FortiSwitch time with the configured schedule and observed rule counters.

C:

That behavior applies when engineers “Configure a promiscuous PVLAN port for a shared gateway”; the different operation “Match a FortiSwitch ACL by source MAC address” is intended to limit an Ethernet policy to frames from a specific hardware address. That different feature is verified by inspect gateway reachability from each secondary VLAN without direct host-to-host communication; for “Match a FortiSwitch ACL by source MAC address” on an access switch in routine maintenance, the relevant evidence is to compare the captured Ethernet source address with the ACL match value.

D:

That behavior applies when engineers “Match an ACL using an IP subnet”; the different operation “Match a FortiSwitch ACL by source MAC address” is intended to limit an Ethernet policy to frames from a specific hardware address. That different feature is verified by compare captured source/destination IP fields and the rule's mask; for “Match a FortiSwitch ACL by source MAC address” on an access switch in routine maintenance, the relevant evidence is to compare the captured Ethernet source address with the ACL match value.

Question 587

After implementing “Match a FortiSwitch ACL by source MAC address,” the site engineer needs to assess its actual effect on a managed campus switch. Which test is the best match?

  1. Compare the captured Ethernet source address with the ACL match value
  2. Check prelookup stage configuration and rule-use counters
  3. Inspect protocol classifier order and the VLAN ID assigned to matching traffic
  4. Inspect matching rules by ACL group and compare their group numbers

Explanation

Correct Answer

A:

The switch behavior that matters is: the layer-2 source MAC classifier selects packets by the originating address at the configured ACL stage. Directly measuring that result demonstrates whether the step to limit an Ethernet policy to frames from a specific hardware address succeeded on a managed campus switch.

Incorrect Answers

B:

This check is suited to “Use prelookup ACL classification” when trying to match traffic in an early processing stage before subsequent forwarding decisions, not to verify “Match a FortiSwitch ACL by source MAC address” at the distribution floor. Checking “Match a FortiSwitch ACL by source MAC address” at the distribution floor requires evidence of its own mechanism: the layer-2 source MAC classifier selects packets by the originating address at the configured ACL stage; that is not the outcome measured by “Use prelookup ACL classification”.

C:

The proposed check concerns “Configure a protocol-based VLAN ACL where needed” rather than “Match a FortiSwitch ACL by source MAC address”: protocol classification relies on a match such as EtherType rather than every frame arriving on one physical port. For “Match a FortiSwitch ACL by source MAC address” on a managed campus switch, a better test would be to compare the captured Ethernet source address with the ACL match value, which targets limit an Ethernet policy to frames from a specific hardware address rather than the alternative diagnostic “Configure a protocol-based VLAN ACL where needed”.

D:

This check is suited to “Keep ACL group priority ordering consistent” when trying to resolve conflicting actions when several ACL groups match the same packet, not to verify “Match a FortiSwitch ACL by source MAC address” at the distribution floor. Checking “Match a FortiSwitch ACL by source MAC address” at the distribution floor requires evidence of its own mechanism: the layer-2 source MAC classifier selects packets by the originating address at the configured ACL stage; that is not the outcome measured by “Keep ACL group priority ordering consistent”.

Question 588

A network architect documents a single goal for a recently upgraded FortiSwitch: filter traffic from a designated routed network range. Which listed procedure provides that capability?

  1. Configure a protocol-based VLAN ACL where needed
  2. Use prelookup ACL classification
  3. Keep ACL group priority ordering consistent
  4. Match an ACL using an IP subnet
  5. Drop matched unwanted frames with an ACL action

Explanation

Correct Answer

D:

At this network boundary, an IP source or destination prefix classifier restricts the match to packets meeting the configured address condition. The operator can test this claim by the specific check: compare captured source/destination IP fields and the rule's mask.

Incorrect Answers

A:

Compared with the requested “Match an ACL using an IP subnet” at the media studio, this would classify a defined payload type into a separate forwarding VLAN instead: protocol classification relies on a match such as EtherType rather than every frame arriving on one physical port. At the media studio, the operational proof would instead be to compare captured source/destination IP fields and the rule's mask, whereas “Configure a protocol-based VLAN ACL where needed” is validated by a different test: inspect protocol classifier order and the VLAN ID assigned to matching traffic.

B:

For the media studio, “Use prelookup ACL classification” is a different type of control from “Match an ACL using an IP subnet”: 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 filter traffic from a designated routed network range.

C:

Compared with the requested “Match an ACL using an IP subnet” at the media studio, this would resolve conflicting actions when several ACL groups match the same packet instead: for conflicting group actions, the lower-numbered ACL group has higher action priority. At the media studio, the operational proof would instead be to compare captured source/destination IP fields and the rule's mask, whereas “Keep ACL group priority ordering consistent” is validated by a different test: inspect matching rules by ACL group and compare their group numbers.

E:

Compared with the requested “Match an ACL using an IP subnet” at the media studio, this would block a targeted source or protocol using explicit hardware filtering instead: a drop action discards frames meeting the ACL match rather than disabling the whole physical port. At the media studio, the operational proof would instead be to compare captured source/destination IP fields and the rule's mask, whereas “Drop matched unwanted frames with an ACL action” is validated by a different test: confirm matching test packets are counted and discarded while unrelated traffic still passes.

Question 589

During validation of a FortiLink-managed access switch at the retail site, the team asks what the change “Match an ACL using an IP subnet” actually does. Which outcome is correct?

  1. Sampling selects a subset of matching packets for observation while forwarding rules remain in effect
  2. Switch ACL classifiers, groups and counters consume finite hardware resources that can be fragmented
  3. An IP source or destination prefix classifier restricts the match to packets meeting the configured address condition
  4. An EtherType comparison identifies the payload protocol without relying on TCP/UDP port numbers

Explanation

Correct Answer

C:

In this deployment, the configured operation is meant to filter traffic from a designated routed network range. The most relevant validation is to compare captured source/destination IP fields and the rule's mask for the equipment at the retail site.

Incorrect Answers

A:

That behavior applies when engineers “Use selective packet sampling where supported”; the different operation “Match an ACL using an IP subnet” is intended to filter traffic from a designated routed network range. That different feature is verified by check the sampling configuration and resulting observed packet frequency; for “Match an ACL using an IP subnet” on a FortiLink-managed access switch, the relevant evidence is to compare captured source/destination IP fields and the rule's mask.

B:

That behavior applies when engineers “Review the ACL hardware resource usage”; the different operation “Match an ACL using an IP subnet” is intended to filter traffic from a designated routed network range. That different feature is verified by inspect ACL usage and available hardware entries before changing rule order; for “Match an ACL using an IP subnet” on a FortiLink-managed access switch, the relevant evidence is to compare captured source/destination IP fields and the rule's mask.

D:

This outcome would be relevant to “Use an ACL Ethernet-type classifier” at the retail site, not the task “Match an ACL using an IP subnet”; the other task is to separate IPv4, IPv6 or other Ethernet frame types in a hardware policy. The action “Match an ACL using an IP subnet” targets a different result: an IP source or destination prefix classifier restricts the match to packets meeting the configured address condition; the proposed alternative would instead be checked by read the EtherType from the frame header and inspect the ACL service match.

Question 590

At the airport office, a dashboard shows ordinary link-up state, but the team also needs proof for “Match an ACL using an IP subnet.” Which targeted check should be used?

  1. Inspect policer conformance/excess statistics alongside ACL counters
  2. Compare the source MAC with the VLAN-assignment entry and effective port VLAN membership
  3. Test server-to-gateway reachability and server-to-server isolation within the isolated VLAN
  4. Compare captured source/destination IP fields and the rule's mask

Explanation

Correct Answer

D:

For the stated requirement, an IP source or destination prefix classifier restricts the match to packets meeting the configured address condition. Directly measuring that result demonstrates whether the step to filter traffic from a designated routed network range succeeded on a switch linked to a FortiGate running FortiOS 7.6.

Incorrect Answers

A:

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 “Match an ACL using an IP subnet” at the airport office. Checking “Match an ACL using an IP subnet” at the airport office requires evidence of its own mechanism: an IP source or destination prefix classifier restricts the match to packets meeting the configured address condition; that is not the outcome measured by “Apply an ACL policer to matching frames”.

B:

This check is suited to “Use a MAC-based VLAN security association” when trying to keep a known endpoint's traffic on an assigned segment when moved among permitted ports, not to verify “Match an ACL using an IP subnet” at the airport office. Checking “Match an ACL using an IP subnet” at the airport office requires evidence of its own mechanism: an IP source or destination prefix classifier restricts the match to packets meeting the configured address condition; that is not the outcome measured by “Use a MAC-based VLAN security association”.

C:

The proposed check concerns “Apply an isolated secondary PVLAN for tenant servers” rather than “Match an ACL using an IP subnet”: isolated PVLAN ports can reach the promiscuous primary attachment but not one another. For “Match an ACL using an IP subnet” on a switch linked to a FortiGate running FortiOS 7.6, a better test would be to compare captured source/destination IP fields and the rule's mask, which targets filter traffic from a designated routed network range rather than the alternative diagnostic “Apply an isolated secondary PVLAN for tenant servers”.

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