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

Question 600

On a remote FortiSwitch installation in the conference venue, the next task is to block a targeted source or protocol using explicit hardware filtering. What is the appropriate configuration decision?

  1. Apply a community secondary PVLAN to one workgroup
  2. Drop matched unwanted frames with an ACL action
  3. Match an ACL using an IP subnet
  4. Review the ACL hardware resource usage

Explanation

Correct Answer

B:

At this network boundary, a drop action discards frames meeting the ACL match rather than disabling the whole physical port. The operator can test this claim by the specific check: confirm matching test packets are counted and discarded while unrelated traffic still passes.

Incorrect Answers

A:

Compared with the requested “Drop matched unwanted frames with an ACL action” at the conference venue, this would allow peers within one designated group to communicate but isolate them from other groups instead: community PVLAN members can communicate with their own community and the promiscuous primary port. At the conference venue, the operational proof would instead be to confirm matching test packets are counted and discarded while unrelated traffic still passes, whereas “Apply a community secondary PVLAN to one workgroup” is validated by a different test: test peer reachability inside the community and deny a connection to a different community.

C:

For the conference venue, “Match an ACL using an IP subnet” is a different type of control from “Drop matched unwanted frames with an ACL action”: an IP source or destination prefix classifier restricts the match to packets meeting the configured address condition. Unlike the requested feature, that setting addresses the need to filter traffic from a designated routed network range, not the objective to block a targeted source or protocol using explicit hardware filtering.

D:

Compared with the requested “Drop matched unwanted frames with an ACL action” at the conference venue, this would diagnose rejection of additional switch ACL entries despite apparently valid syntax instead: switch ACL classifiers, groups and counters consume finite hardware resources that can be fragmented. At the conference venue, the operational proof would instead be to confirm matching test packets are counted and discarded while unrelated traffic still passes, whereas “Review the ACL hardware resource usage” is validated by a different test: inspect ACL usage and available hardware entries before changing rule order.

Question 601

A switch change for the campus consists of this step: drop matched unwanted frames with an ACL action. Which behavior reflects the purpose of that change?

  1. ACL actions can assign supported classification or priority treatment to matching frames
  2. Isolated PVLAN ports can reach the promiscuous primary attachment but not one another
  3. An egress-stage policy acts on frames being transmitted rather than their original entry classification
  4. 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 block a targeted source or protocol using explicit hardware filtering. The most relevant validation is to confirm matching test packets are counted and discarded while unrelated traffic still passes for the equipment at the campus.

Incorrect Answers

A:

This outcome would be relevant to “Apply a QoS action using an ACL” at the campus, not the task “Drop matched unwanted frames with an ACL action”; the other task is to prioritize a defined class without requiring every endpoint to mark itself. The action “Drop matched unwanted frames with an ACL action” targets a different result: a drop action discards frames meeting the ACL match rather than disabling the whole physical port; the proposed alternative would instead be checked by inspect ACL match counters and resulting QoS queue handling.

B:

That behavior applies when engineers “Apply an isolated secondary PVLAN for tenant servers”; the different operation “Drop matched unwanted frames with an ACL action” is intended to block a targeted source or protocol using explicit hardware filtering. That different feature is verified by test server-to-gateway reachability and server-to-server isolation within the isolated VLAN; for “Drop matched unwanted frames with an ACL action” on an endpoint-facing FortiSwitch port, the relevant evidence is to confirm matching test packets are counted and discarded while unrelated traffic still passes.

C:

That behavior applies when engineers “Install an egress ACL for outgoing traffic”; the different operation “Drop matched unwanted frames with an ACL action” is intended to block a targeted source or protocol using explicit hardware filtering. That different feature is verified by inspect egress ACL counters for the relevant outgoing port; for “Drop matched unwanted frames with an ACL action” on an endpoint-facing FortiSwitch port, the relevant evidence is to confirm matching test packets are counted and discarded while unrelated traffic still passes.

Question 602

A post-change review at the remote depot must validate the implementation of “Drop matched unwanted frames with an ACL action.” What should the reviewer inspect first?

  1. Confirm matching test packets are counted and discarded while unrelated traffic still passes
  2. Inspect gateway reachability from each secondary VLAN without direct host-to-host communication
  3. Review ingress ACL match counters while sending matching test frames
  4. Compare current FortiSwitch time with the configured schedule and observed rule counters

Explanation

Correct Answer

A:

For the stated requirement, a drop action discards frames meeting the ACL match rather than disabling the whole physical port. Directly measuring that result demonstrates whether the step to block a targeted source or protocol using explicit hardware filtering succeeded on a standalone FortiSwitch appliance.

Incorrect Answers

B:

The proposed check concerns “Configure a promiscuous PVLAN port for a shared gateway” rather than “Drop matched unwanted frames with an ACL action”: the promiscuous port connects secondary VLANs to the common routed or shared service endpoint. For “Drop matched unwanted frames with an ACL action” on a standalone FortiSwitch appliance, a better test would be to confirm matching test packets are counted and discarded while unrelated traffic still passes, which targets block a targeted source or protocol using explicit hardware filtering rather than the alternative diagnostic “Configure a promiscuous PVLAN port for a shared gateway”.

C:

This check is suited to “Install an ingress ACL for received traffic” when trying to filter packets as they enter a FortiSwitch forwarding pipeline, not to verify “Drop matched unwanted frames with an ACL action” at the remote depot. Checking “Drop matched unwanted frames with an ACL action” at the remote depot requires evidence of its own mechanism: a drop action discards frames meeting the ACL match rather than disabling the whole physical port; that is not the outcome measured by “Install an ingress ACL for received traffic”.

D:

This check is suited to “Configure an ACL schedule” when trying to enforce a selected match/action only during approved operational hours, not to verify “Drop matched unwanted frames with an ACL action” at the remote depot. Checking “Drop matched unwanted frames with an ACL action” at the remote depot requires evidence of its own mechanism: a drop action discards frames meeting the ACL match rather than disabling the whole physical port; that is not the outcome measured by “Configure an ACL schedule”.

Question 603

A production incident in the branch office reveals the need to enforce a selected match/action only during approved operational hours. Which targeted FortiSwitch setting or method should the team use?

  1. Use an ACL Ethernet-type classifier
  2. Configure an ACL schedule
  3. Keep ACL group priority ordering consistent
  4. Configure a protocol-based VLAN ACL where needed
  5. Install an ingress ACL for received traffic

Explanation

Correct Answer

B:

The deciding detail is that time-based ACL scheduling controls policy applicability, not the device system clock itself. This distinction is material to the branch office, where the stated goal is to enforce a selected match/action only during approved operational hours.

Incorrect Answers

A:

Compared with the requested “Configure an ACL schedule” at the branch office, this would separate IPv4, IPv6 or other Ethernet frame types in a hardware policy instead: an EtherType comparison identifies the payload protocol without relying on TCP/UDP port numbers. At the branch office, the operational proof would instead be to compare current FortiSwitch time with the configured schedule and observed rule counters, whereas “Use an ACL Ethernet-type classifier” is validated by a different test: read the EtherType from the frame header and inspect the ACL service match.

C:

For the branch office, “Keep ACL group priority ordering consistent” is a different type of control from “Configure an ACL schedule”: 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 enforce a selected match/action only during approved operational hours.

D:

Compared with the requested “Configure an ACL schedule” at the branch office, 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 branch office, the operational proof would instead be to compare current FortiSwitch time with the configured schedule and observed rule counters, 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.

E:

Compared with the requested “Configure an ACL schedule” at the branch office, this would filter packets as they enter a FortiSwitch forwarding pipeline instead: an ingress ACL classifies traffic arriving at an interface and applies permitted hardware actions. At the branch office, the operational proof would instead be to compare current FortiSwitch time with the configured schedule and observed rule counters, whereas “Install an ingress ACL for received traffic” is validated by a different test: review ingress ACL match counters while sending matching test frames.

Question 604

The operator has decided to configure an ACL schedule on a local switch administering branch clients at the factory. Which operational behavior is the most reasonable expectation of that specific feature?

  1. A linked policer enforces meter behavior for the matched ACL class
  2. Community PVLAN members can communicate with their own community and the promiscuous primary port
  3. Switch ACL classifiers, groups and counters consume finite hardware resources that can be fragmented
  4. Time-based ACL scheduling controls policy applicability, not the device system clock itself

Explanation

Correct Answer

D:

The relevant mechanism is: the configured operation is meant to enforce a selected match/action only during approved operational hours. The most relevant validation is to compare current FortiSwitch time with the configured schedule and observed rule counters for the equipment at the factory.

Incorrect Answers

A:

That behavior applies when engineers “Apply an ACL policer to matching frames”; the different operation “Configure an ACL schedule” is intended to enforce a selected match/action only during approved operational hours. That different feature is verified by inspect policer conformance/excess statistics alongside ACL counters; for “Configure an ACL schedule” on a local switch administering branch clients, the relevant evidence is to compare current FortiSwitch time with the configured schedule and observed rule counters.

B:

This outcome would be relevant to “Apply a community secondary PVLAN to one workgroup” at the factory, not the task “Configure an ACL schedule”; the other task is to allow peers within one designated group to communicate but isolate them from other groups. The action “Configure an ACL schedule” targets a different result: time-based ACL scheduling controls policy applicability, not the device system clock itself; the proposed alternative would instead be checked by test peer reachability inside the community and deny a connection to a different community.

C:

That behavior applies when engineers “Review the ACL hardware resource usage”; the different operation “Configure an ACL schedule” is intended to enforce a selected match/action only during approved operational hours. That different feature is verified by inspect ACL usage and available hardware entries before changing rule order; for “Configure an ACL schedule” on a local switch administering branch clients, the relevant evidence is to compare current FortiSwitch time with the configured schedule and observed rule counters.

Question 605

The work order to enforce a selected match/action only during approved operational hours is marked complete on a switch used by multiple office teams. Which observation most directly tests the completed configuration?

  1. Inspect ACL match counters and resulting QoS queue handling
  2. Capture the double-tagged frame and verify distinct S-tag and customer C-tag fields
  3. Inspect egress ACL counters for the relevant outgoing port
  4. Compare current FortiSwitch time with the configured schedule and observed rule counters

Explanation

Correct Answer

D:

This approach fits because time-based ACL scheduling controls policy applicability, not the device system clock itself. Directly measuring that result demonstrates whether the step to enforce a selected match/action only during approved operational hours succeeded on a switch used by multiple office teams.

Incorrect Answers

A:

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 “Configure an ACL schedule” at the research building. Checking “Configure an ACL schedule” at the research building requires evidence of its own mechanism: time-based ACL scheduling controls policy applicability, not the device system clock itself; that is not the outcome measured by “Apply a QoS action using an ACL”.

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 “Configure an ACL schedule” at the research building. Checking “Configure an ACL schedule” at the research building requires evidence of its own mechanism: time-based ACL scheduling controls policy applicability, not the device system clock itself; that is not the outcome measured by “Use an 802.1Q QinQ outer service VLAN”.

C:

The proposed check concerns “Install an egress ACL for outgoing traffic” rather than “Configure an ACL schedule”: an egress-stage policy acts on frames being transmitted rather than their original entry classification. For “Configure an ACL schedule” on a switch used by multiple office teams, a better test would be to compare current FortiSwitch time with the configured schedule and observed rule counters, which targets enforce a selected match/action only during approved operational hours rather than the alternative diagnostic “Install an egress ACL for outgoing traffic”.

Question 606

A switch rollout in the clinic will be approved only if it can gather representative traffic metadata without mirroring every packet. Which administrative action meets this acceptance criterion?

  1. Configure an ACL schedule
  2. Match an ACL using an IP subnet
  3. Use selective packet sampling where supported
  4. Review the ACL hardware resource usage
  5. Apply a community secondary PVLAN to one workgroup

Explanation

Correct Answer

C:

The critical distinction is that sampling selects a subset of matching packets for observation while forwarding rules remain in effect. The operator can test this claim by the specific check: check the sampling configuration and resulting observed packet frequency.

Incorrect Answers

A:

Compared with the requested “Use selective packet sampling where supported” at the clinic, this would enforce a selected match/action only during approved operational hours instead: time-based ACL scheduling controls policy applicability, not the device system clock itself. At the clinic, the operational proof would instead be to check the sampling configuration and resulting observed packet frequency, whereas “Configure an ACL schedule” is validated by a different test: compare current FortiSwitch time with the configured schedule and observed rule counters.

B:

For the clinic, “Match an ACL using an IP subnet” is a different type of control from “Use selective packet sampling where supported”: an IP source or destination prefix classifier restricts the match to packets meeting the configured address condition. Unlike the requested feature, that setting addresses the need to filter traffic from a designated routed network range, not the objective to gather representative traffic metadata without mirroring every packet.

D:

Compared with the requested “Use selective packet sampling where supported” at the clinic, this would diagnose rejection of additional switch ACL entries despite apparently valid syntax instead: switch ACL classifiers, groups and counters consume finite hardware resources that can be fragmented. At the clinic, the operational proof would instead be to check the sampling configuration and resulting observed packet frequency, whereas “Review the ACL hardware resource usage” is validated by a different test: inspect ACL usage and available hardware entries before changing rule order.

E:

Compared with the requested “Use selective packet sampling where supported” at the clinic, this would allow peers within one designated group to communicate but isolate them from other groups instead: community PVLAN members can communicate with their own community and the promiscuous primary port. At the clinic, the operational proof would instead be to check the sampling configuration and resulting observed packet frequency, whereas “Apply a community secondary PVLAN to one workgroup” is validated by a different test: test peer reachability inside the community and deny a connection to a different community.

Question 607

A switch change for the data hall consists of this step: use selective packet sampling where supported. Which behavior reflects the purpose of that change?

  1. Sampling selects a subset of matching packets for observation while forwarding rules remain in effect
  2. Isolated PVLAN ports can reach the promiscuous primary attachment but not one another
  3. An egress-stage policy acts on frames being transmitted rather than their original entry classification
  4. ACL actions can assign supported classification or priority treatment to matching frames

Explanation

Correct Answer

A:

That setting is appropriate here because the configured operation is meant to gather representative traffic metadata without mirroring every packet. The most relevant validation is to check the sampling configuration and resulting observed packet frequency for the equipment at the data hall.

Incorrect Answers

B:

That behavior applies when engineers “Apply an isolated secondary PVLAN for tenant servers”; the different operation “Use selective packet sampling where supported” is intended to gather representative traffic metadata without mirroring every packet. That different feature is verified by test server-to-gateway reachability and server-to-server isolation within the isolated VLAN; for “Use selective packet sampling where supported” on a newly racked distribution unit, the relevant evidence is to check the sampling configuration and resulting observed packet frequency.

C:

That behavior applies when engineers “Install an egress ACL for outgoing traffic”; the different operation “Use selective packet sampling where supported” is intended to gather representative traffic metadata without mirroring every packet. That different feature is verified by inspect egress ACL counters for the relevant outgoing port; for “Use selective packet sampling where supported” on a newly racked distribution unit, the relevant evidence is to check the sampling configuration and resulting observed packet frequency.

D:

This outcome would be relevant to “Apply a QoS action using an ACL” at the data hall, not the task “Use selective packet sampling where supported”; the other task is to prioritize a defined class without requiring every endpoint to mark itself. The action “Use selective packet sampling where supported” targets a different result: sampling selects a subset of matching packets for observation while forwarding rules remain in effect; the proposed alternative would instead be checked by inspect ACL match counters and resulting QoS queue handling.

Question 608

A technician says “Use selective packet sampling where supported” has solved the issue at the development floor. Which diagnostic step would substantiate that claim?

  1. Inspect gateway reachability from each secondary VLAN without direct host-to-host communication
  2. Review ingress ACL match counters while sending matching test frames
  3. Check the sampling configuration and resulting observed packet frequency
  4. Confirm matching test packets are counted and discarded while unrelated traffic still passes

Explanation

Correct Answer

C:

This is the precise control because sampling selects a subset of matching packets for observation while forwarding rules remain in effect. Directly measuring that result demonstrates whether the step to gather representative traffic metadata without mirroring every packet succeeded on two distribution switches.

Incorrect Answers

A:

The proposed check concerns “Configure a promiscuous PVLAN port for a shared gateway” rather than “Use selective packet sampling where supported”: the promiscuous port connects secondary VLANs to the common routed or shared service endpoint. For “Use selective packet sampling where supported” on two distribution switches, a better test would be to check the sampling configuration and resulting observed packet frequency, which targets gather representative traffic metadata without mirroring every packet rather than the alternative diagnostic “Configure a promiscuous PVLAN port for a shared gateway”.

B:

This check is suited to “Install an ingress ACL for received traffic” when trying to filter packets as they enter a FortiSwitch forwarding pipeline, not to verify “Use selective packet sampling where supported” at the development floor. Checking “Use selective packet sampling where supported” at the development floor requires evidence of its own mechanism: sampling selects a subset of matching packets for observation while forwarding rules remain in effect; that is not the outcome measured by “Install an ingress ACL for received traffic”.

D:

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 “Use selective packet sampling where supported” at the development floor. Checking “Use selective packet sampling where supported” at the development floor requires evidence of its own mechanism: sampling selects a subset of matching packets for observation while forwarding rules remain in effect; that is not the outcome measured by “Drop matched unwanted frames with an ACL action”.

Question 609

An administrator responsible for a staging FortiSwitch in the conference venue must resolve conflicting actions when several ACL groups match the same packet. Which configuration best matches that precise goal?

  1. Apply a community secondary PVLAN to one workgroup
  2. Use prelookup ACL classification
  3. Keep ACL group priority ordering consistent
  4. Apply an ACL policer to matching frames

Explanation

Correct Answer

C:

The implementation works because for conflicting group actions, the lower-numbered ACL group has higher action priority. This distinction is material to the conference venue, where the stated goal is to resolve conflicting actions when several ACL groups match the same packet.

Incorrect Answers

A:

For the conference venue, “Apply a community secondary PVLAN to one workgroup” is a different type of control from “Keep ACL group priority ordering consistent”: community PVLAN members can communicate with their own community and the promiscuous primary port. Unlike the requested feature, that setting addresses the need to allow peers within one designated group to communicate but isolate them from other groups, not the objective to resolve conflicting actions when several ACL groups match the same packet.

B:

Compared with the requested “Keep ACL group priority ordering consistent” at the conference venue, this would match traffic in an early processing stage before subsequent forwarding decisions instead: a prelookup ACL applies available classifiers at its pipeline stage; it is not a route-table entry. At the conference venue, the operational proof would instead be to inspect matching rules by ACL group and compare their group numbers, whereas “Use prelookup ACL classification” is validated by a different test: check prelookup stage configuration and rule-use counters.

D:

Compared with the requested “Keep ACL group priority ordering consistent” at the conference venue, this would rate-control selected traffic rather than dropping every matching packet instead: a linked policer enforces meter behavior for the matched ACL class. At the conference venue, the operational proof would instead be to inspect matching rules by ACL group and compare their group numbers, whereas “Apply an ACL policer to matching frames” is validated by a different test: inspect policer conformance/excess statistics alongside ACL counters.

Question 610

The operator has decided to keep ACL group priority ordering consistent on a carefully segmented Layer 2 network at the campus. Which operational behavior is the most reasonable expectation of that specific feature?

  1. VLAN stacking adds an outer service tag while preserving the customer's internal VLAN identifier
  2. Time-based ACL scheduling controls policy applicability, not the device system clock itself
  3. For conflicting group actions, the lower-numbered ACL group has higher action priority
  4. An egress-stage policy acts on frames being transmitted rather than their original entry classification
  5. ACL actions can assign supported classification or priority treatment to matching frames
  6. Isolated PVLAN ports can reach the promiscuous primary attachment but not one another

Explanation

Correct Answer

C:

Given the described goal, the configured operation is meant to resolve conflicting actions when several ACL groups match the same packet. The most relevant validation is to inspect matching rules by ACL group and compare their group numbers for the equipment at the campus.

Incorrect Answers

A:

This outcome would be relevant to “Use an 802.1Q QinQ outer service VLAN” at the campus, not the task “Keep ACL group priority ordering consistent”; the other task is to transport independently numbered customer VLANs through provider infrastructure. The action “Keep ACL group priority ordering consistent” targets a different result: for conflicting group actions, the lower-numbered ACL group has higher action priority; the proposed alternative would instead be checked by capture the double-tagged frame and verify distinct S-tag and customer C-tag fields.

B:

That behavior applies when engineers “Configure an ACL schedule”; the different operation “Keep ACL group priority ordering consistent” is intended to resolve conflicting actions when several ACL groups match the same packet. That different feature is verified by compare current FortiSwitch time with the configured schedule and observed rule counters; for “Keep ACL group priority ordering consistent” on a carefully segmented Layer 2 network, the relevant evidence is to inspect matching rules by ACL group and compare their group numbers.

D:

That behavior applies when engineers “Install an egress ACL for outgoing traffic”; the different operation “Keep ACL group priority ordering consistent” is intended to resolve conflicting actions when several ACL groups match the same packet. That different feature is verified by inspect egress ACL counters for the relevant outgoing port; for “Keep ACL group priority ordering consistent” on a carefully segmented Layer 2 network, the relevant evidence is to inspect matching rules by ACL group and compare their group numbers.

E:

That behavior applies when engineers “Apply a QoS action using an ACL”; the different operation “Keep ACL group priority ordering consistent” is intended to resolve conflicting actions when several ACL groups match the same packet. That different feature is verified by inspect ACL match counters and resulting QoS queue handling; for “Keep ACL group priority ordering consistent” on a carefully segmented Layer 2 network, the relevant evidence is to inspect matching rules by ACL group and compare their group numbers.

F:

This outcome would be relevant to “Apply an isolated secondary PVLAN for tenant servers” at the campus, not the task “Keep ACL group priority ordering consistent”; the other task is to allow server access to a shared gateway while blocking any host-to-host communication. The action “Keep ACL group priority ordering consistent” targets a different result: for conflicting group actions, the lower-numbered ACL group has higher action priority; the proposed alternative would instead be checked by test server-to-gateway reachability and server-to-server isolation within the isolated VLAN.

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