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

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.

Question 611

After implementing “Keep ACL group priority ordering consistent,” the site engineer needs to assess its actual effect on a central switching stack. Which test is the best match?

  1. Compare the captured Ethernet source address with the ACL match value
  2. Inspect matching rules by ACL group and compare their group numbers
  3. Compare the source MAC with the VLAN-assignment entry and effective port VLAN membership
  4. Confirm matching test packets are counted and discarded while unrelated traffic still passes

Explanation

Correct Answer

B:

The switch behavior that matters is: for conflicting group actions, the lower-numbered ACL group has higher action priority. Directly measuring that result demonstrates whether the step to resolve conflicting actions when several ACL groups match the same packet succeeded on a central switching stack.

Incorrect Answers

A:

The proposed check concerns “Match a FortiSwitch ACL by source MAC address” rather than “Keep ACL group priority ordering consistent”: the layer-2 source MAC classifier selects packets by the originating address at the configured ACL stage. For “Keep ACL group priority ordering consistent” on a central switching stack, a better test would be to inspect matching rules by ACL group and compare their group numbers, which targets resolve conflicting actions when several ACL groups match the same packet rather than the alternative diagnostic “Match a FortiSwitch ACL by source MAC address”.

C:

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 “Keep ACL group priority ordering consistent” at the remote depot. Checking “Keep ACL group priority ordering consistent” at the remote depot requires evidence of its own mechanism: for conflicting group actions, the lower-numbered ACL group has higher action priority; that is not the outcome measured by “Use a MAC-based VLAN security association”.

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 “Keep ACL group priority ordering consistent” at the remote depot. Checking “Keep ACL group priority ordering consistent” at the remote depot requires evidence of its own mechanism: for conflicting group actions, the lower-numbered ACL group has higher action priority; that is not the outcome measured by “Drop matched unwanted frames with an ACL action”.

Question 612

A peer review of the lab asks how the design will allow server access to a shared gateway while blocking any host-to-host communication. Which FortiSwitch technique is the correct response?

  1. Drop matched unwanted frames with an ACL action
  2. Configure a promiscuous PVLAN port for a shared gateway
  3. Match a FortiSwitch ACL by source MAC address
  4. Apply an isolated secondary PVLAN for tenant servers

Explanation

Correct Answer

D:

At this network boundary, isolated PVLAN ports can reach the promiscuous primary attachment but not one another. The operator can test this claim by the specific check: test server-to-gateway reachability and server-to-server isolation within the isolated VLAN.

Incorrect Answers

A:

Compared with the requested “Apply an isolated secondary PVLAN for tenant servers” at the lab, 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 lab, the operational proof would instead be to test server-to-gateway reachability and server-to-server isolation within the isolated VLAN, 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.

B:

For the lab, “Configure a promiscuous PVLAN port for a shared gateway” is a different type of control from “Apply an isolated secondary PVLAN for tenant servers”: the promiscuous port connects secondary VLANs to the common routed or shared service endpoint. Unlike the requested feature, that setting addresses the need to provide primary-VLAN reachability to otherwise separated PVLAN hosts, not the objective to allow server access to a shared gateway while blocking any host-to-host communication.

C:

Compared with the requested “Apply an isolated secondary PVLAN for tenant servers” at the lab, this would limit an Ethernet policy to frames from a specific hardware address instead: the layer-2 source MAC classifier selects packets by the originating address at the configured ACL stage. At the lab, the operational proof would instead be to test server-to-gateway reachability and server-to-server isolation within the isolated VLAN, whereas “Match a FortiSwitch ACL by source MAC address” is validated by a different test: compare the captured Ethernet source address with the ACL match value.

Question 613

On a production FortiSwitch fabric, “Apply an isolated secondary PVLAN for tenant servers” is configured for the staging rack. What effect should an administrator expect without assuming unrelated features are enabled?

  1. Isolated PVLAN ports can reach the promiscuous primary attachment but not one another
  2. A prelookup ACL applies available classifiers at its pipeline stage; it is not a route-table entry
  3. Protocol classification relies on a match such as EtherType rather than every frame arriving on one physical port
  4. Sampling selects a subset of matching packets for observation while forwarding rules remain in effect

Explanation

Correct Answer

A:

In this deployment, the configured operation is meant to allow server access to a shared gateway while blocking any host-to-host communication. The most relevant validation is to test server-to-gateway reachability and server-to-server isolation within the isolated VLAN for the equipment at the staging rack.

Incorrect Answers

B:

That behavior applies when engineers “Use prelookup ACL classification”; the different operation “Apply an isolated secondary PVLAN for tenant servers” is intended to allow server access to a shared gateway while blocking any host-to-host communication. That different feature is verified by check prelookup stage configuration and rule-use counters; for “Apply an isolated secondary PVLAN for tenant servers” on a production FortiSwitch fabric, the relevant evidence is to test server-to-gateway reachability and server-to-server isolation within the isolated VLAN.

C:

This outcome would be relevant to “Configure a protocol-based VLAN ACL where needed” at the staging rack, not the task “Apply an isolated secondary PVLAN for tenant servers”; the other task is to classify a defined payload type into a separate forwarding VLAN. The action “Apply an isolated secondary PVLAN for tenant servers” targets a different result: isolated PVLAN ports can reach the promiscuous primary attachment but not one another; the proposed alternative would instead be checked by inspect protocol classifier order and the VLAN ID assigned to matching traffic.

D:

That behavior applies when engineers “Use selective packet sampling where supported”; the different operation “Apply an isolated secondary PVLAN for tenant servers” is intended to allow server access to a shared gateway while blocking any host-to-host communication. That different feature is verified by check the sampling configuration and resulting observed packet frequency; for “Apply an isolated secondary PVLAN for tenant servers” on a production FortiSwitch fabric, the relevant evidence is to test server-to-gateway reachability and server-to-server isolation within the isolated VLAN.

Question 614

At the research building, a dashboard shows ordinary link-up state, but the team also needs proof for “Apply an isolated secondary PVLAN for tenant servers.” Which targeted check should be used?

  1. Compare captured source/destination IP fields and the rule's mask
  2. Capture the double-tagged frame and verify distinct S-tag and customer C-tag fields
  3. Compare current FortiSwitch time with the configured schedule and observed rule counters
  4. Test server-to-gateway reachability and server-to-server isolation within the isolated VLAN
  5. Inspect ACL usage and available hardware entries before changing rule order

Explanation

Correct Answer

D:

For the stated requirement, isolated PVLAN ports can reach the promiscuous primary attachment but not one another. Directly measuring that result demonstrates whether the step to allow server access to a shared gateway while blocking any host-to-host communication succeeded on a newly racked distribution unit.

Incorrect Answers

A:

The proposed check concerns “Match an ACL using an IP subnet” rather than “Apply an isolated secondary PVLAN for tenant servers”: an IP source or destination prefix classifier restricts the match to packets meeting the configured address condition. For “Apply an isolated secondary PVLAN for tenant servers” on a newly racked distribution unit, a better test would be to test server-to-gateway reachability and server-to-server isolation within the isolated VLAN, which targets allow server access to a shared gateway while blocking any host-to-host communication rather than the alternative diagnostic “Match an ACL using an IP subnet”.

B:

The proposed check concerns “Use an 802.1Q QinQ outer service VLAN” rather than “Apply an isolated secondary PVLAN for tenant servers”: VLAN stacking adds an outer service tag while preserving the customer's internal VLAN identifier. For “Apply an isolated secondary PVLAN for tenant servers” on a newly racked distribution unit, a better test would be to test server-to-gateway reachability and server-to-server isolation within the isolated VLAN, which targets allow server access to a shared gateway while blocking any host-to-host communication rather than the alternative diagnostic “Use an 802.1Q QinQ outer service VLAN”.

C:

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 “Apply an isolated secondary PVLAN for tenant servers” at the research building. Checking “Apply an isolated secondary PVLAN for tenant servers” at the research building requires evidence of its own mechanism: isolated PVLAN ports can reach the promiscuous primary attachment but not one another; that is not the outcome measured by “Configure an ACL schedule”.

E:

This check is suited to “Review the ACL hardware resource usage” when trying to diagnose rejection of additional switch ACL entries despite apparently valid syntax, not to verify “Apply an isolated secondary PVLAN for tenant servers” at the research building. Checking “Apply an isolated secondary PVLAN for tenant servers” at the research building requires evidence of its own mechanism: isolated PVLAN ports can reach the promiscuous primary attachment but not one another; that is not the outcome measured by “Review the ACL hardware resource usage”.

Question 615

A network architect documents a single goal for two distribution switches: allow peers within one designated group to communicate but isolate them from other groups. Which listed procedure provides that capability?

  1. Apply a community secondary PVLAN to one workgroup
  2. Match a FortiSwitch ACL by source MAC address
  3. Use a MAC-based VLAN security association
  4. Keep ACL group priority ordering consistent

Explanation

Correct Answer

A:

The deciding detail is that community PVLAN members can communicate with their own community and the promiscuous primary port. This distinction is material to the clinic, where the stated goal is to allow peers within one designated group to communicate but isolate them from other groups.

Incorrect Answers

B:

For the clinic, “Match a FortiSwitch ACL by source MAC address” is a different type of control from “Apply a community secondary PVLAN to one workgroup”: the layer-2 source MAC classifier selects packets by the originating address at the configured ACL stage. Unlike the requested feature, that setting addresses the need to limit an Ethernet policy to frames from a specific hardware address, not the objective to allow peers within one designated group to communicate but isolate them from other groups.

C:

Compared with the requested “Apply a community secondary PVLAN to one workgroup” at the clinic, this would keep a known endpoint's traffic on an assigned segment when moved among permitted ports instead: MAC-to-VLAN mapping is based on source identity and differs from general ACL drop actions. At the clinic, the operational proof would instead be to test peer reachability inside the community and deny a connection to a different community, whereas “Use a MAC-based VLAN security association” is validated by a different test: compare the source MAC with the VLAN-assignment entry and effective port VLAN membership.

D:

Compared with the requested “Apply a community secondary PVLAN to one workgroup” at the clinic, 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 clinic, the operational proof would instead be to test peer reachability inside the community and deny a connection to a different community, whereas “Keep ACL group priority ordering consistent” is validated by a different test: inspect matching rules by ACL group and compare their group numbers.

Question 616

For the data hall, an administrator applies the action “Apply a community secondary PVLAN to one workgroup.” Which effect should appear when it operates as intended?

  1. An ingress ACL classifies traffic arriving at an interface and applies permitted hardware actions
  2. Community PVLAN members can communicate with their own community and the promiscuous primary port
  3. Sampling selects a subset of matching packets for observation while forwarding rules remain in effect
  4. An EtherType comparison identifies the payload protocol without relying on TCP/UDP port numbers

Explanation

Correct Answer

B:

The relevant mechanism is: the configured operation is meant to allow peers within one designated group to communicate but isolate them from other groups. The most relevant validation is to test peer reachability inside the community and deny a connection to a different community for the equipment at the data hall.

Incorrect Answers

A:

That behavior applies when engineers “Install an ingress ACL for received traffic”; the different operation “Apply a community secondary PVLAN to one workgroup” is intended to allow peers within one designated group to communicate but isolate them from other groups. That different feature is verified by review ingress ACL match counters while sending matching test frames; for “Apply a community secondary PVLAN to one workgroup” on a staging FortiSwitch, the relevant evidence is to test peer reachability inside the community and deny a connection to a different community.

C:

That behavior applies when engineers “Use selective packet sampling where supported”; the different operation “Apply a community secondary PVLAN to one workgroup” is intended to allow peers within one designated group to communicate but isolate them from other groups. That different feature is verified by check the sampling configuration and resulting observed packet frequency; for “Apply a community secondary PVLAN to one workgroup” on a staging FortiSwitch, the relevant evidence is to test peer reachability inside the community and deny a connection to a different community.

D:

This outcome would be relevant to “Use an ACL Ethernet-type classifier” at the data hall, not the task “Apply a community secondary PVLAN to one workgroup”; the other task is to separate IPv4, IPv6 or other Ethernet frame types in a hardware policy. The action “Apply a community secondary PVLAN to one workgroup” targets a different result: community PVLAN members can communicate with their own community and the promiscuous primary port; the proposed alternative would instead be checked by read the EtherType from the frame header and inspect the ACL service match.

Question 617

A FortiSwitch engineer in the development floor is documenting successful operation of “Apply a community secondary PVLAN to one workgroup.” Which measurement or inspection confirms it?

  1. Inspect policer conformance/excess statistics alongside ACL counters
  2. Test peer reachability inside the community and deny a connection to a different community
  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
  5. Inspect ACL usage and available hardware entries before changing rule order

Explanation

Correct Answer

B:

This approach fits because community PVLAN members can communicate with their own community and the promiscuous primary port. Directly measuring that result demonstrates whether the step to allow peers within one designated group to communicate but isolate them from other groups succeeded on a carefully segmented Layer 2 network.

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 “Apply a community secondary PVLAN to one workgroup” at the development floor. Checking “Apply a community secondary PVLAN to one workgroup” at the development floor requires evidence of its own mechanism: community PVLAN members can communicate with their own community and the promiscuous primary port; that is not the outcome measured by “Apply an ACL policer to matching frames”.

C:

The proposed check concerns “Apply an isolated secondary PVLAN for tenant servers” rather than “Apply a community secondary PVLAN to one workgroup”: isolated PVLAN ports can reach the promiscuous primary attachment but not one another. For “Apply a community secondary PVLAN to one workgroup” on a carefully segmented Layer 2 network, a better test would be to test peer reachability inside the community and deny a connection to a different community, which targets allow peers within one designated group to communicate but isolate them from other groups rather than the alternative diagnostic “Apply an isolated secondary PVLAN for tenant servers”.

D:

The proposed check concerns “Match an ACL using an IP subnet” rather than “Apply a community secondary PVLAN to one workgroup”: an IP source or destination prefix classifier restricts the match to packets meeting the configured address condition. For “Apply a community secondary PVLAN to one workgroup” on a carefully segmented Layer 2 network, a better test would be to test peer reachability inside the community and deny a connection to a different community, which targets allow peers within one designated group to communicate but isolate them from other groups rather than the alternative diagnostic “Match an ACL using an IP subnet”.

E:

This check is suited to “Review the ACL hardware resource usage” when trying to diagnose rejection of additional switch ACL entries despite apparently valid syntax, not to verify “Apply a community secondary PVLAN to one workgroup” at the development floor. Checking “Apply a community secondary PVLAN to one workgroup” at the development floor requires evidence of its own mechanism: community PVLAN members can communicate with their own community and the promiscuous primary port; that is not the outcome measured by “Review the ACL hardware resource usage”.

Question 618

The operational requirement for a central switching stack at the conference venue is to provide primary-VLAN reachability to otherwise separated PVLAN hosts. Which FortiSwitch choice directly targets it?

  1. Drop matched unwanted frames with an ACL action
  2. Apply a community secondary PVLAN to one workgroup
  3. Install an ingress ACL for received traffic
  4. Configure a promiscuous PVLAN port for a shared gateway

Explanation

Correct Answer

D:

The critical distinction is that the promiscuous port connects secondary VLANs to the common routed or shared service endpoint. The operator can test this claim by the specific check: inspect gateway reachability from each secondary VLAN without direct host-to-host communication.

Incorrect Answers

A:

Compared with the requested “Configure a promiscuous PVLAN port for a shared gateway” at the conference venue, 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 conference venue, the operational proof would instead be to inspect gateway reachability from each secondary VLAN without direct host-to-host communication, 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.

B:

Compared with the requested “Configure a promiscuous PVLAN port for a shared gateway” 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 inspect gateway reachability from each secondary VLAN without direct host-to-host communication, 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, “Install an ingress ACL for received traffic” is a different type of control from “Configure a promiscuous PVLAN port for a shared gateway”: an ingress ACL classifies traffic arriving at an interface and applies permitted hardware actions. Unlike the requested feature, that setting addresses the need to filter packets as they enter a FortiSwitch forwarding pipeline, not the objective to provide primary-VLAN reachability to otherwise separated PVLAN hosts.

Question 619

On a FortiSwitch connected to the security edge, “Configure a promiscuous PVLAN port for a shared gateway” is configured for the hospital wing. What effect should an administrator expect without assuming unrelated features are enabled?

  1. A prelookup ACL applies available classifiers at its pipeline stage; it is not a route-table entry
  2. A linked policer enforces meter behavior for the matched ACL class
  3. The promiscuous port connects secondary VLANs to the common routed or shared service endpoint
  4. Protocol classification relies on a match such as EtherType rather than every frame arriving on one physical port

Explanation

Correct Answer

C:

That setting is appropriate here because the configured operation is meant to provide primary-VLAN reachability to otherwise separated PVLAN hosts. The most relevant validation is to inspect gateway reachability from each secondary VLAN without direct host-to-host communication for the equipment at the hospital wing.

Incorrect Answers

A:

This outcome would be relevant to “Use prelookup ACL classification” at the hospital wing, not the task “Configure a promiscuous PVLAN port for a shared gateway”; the other task is to match traffic in an early processing stage before subsequent forwarding decisions. The action “Configure a promiscuous PVLAN port for a shared gateway” targets a different result: the promiscuous port connects secondary VLANs to the common routed or shared service endpoint; the proposed alternative would instead be checked by check prelookup stage configuration and rule-use counters.

B:

That behavior applies when engineers “Apply an ACL policer to matching frames”; the different operation “Configure a promiscuous PVLAN port for a shared gateway” is intended to provide primary-VLAN reachability to otherwise separated PVLAN hosts. That different feature is verified by inspect policer conformance/excess statistics alongside ACL counters; for “Configure a promiscuous PVLAN port for a shared gateway” on a FortiSwitch connected to the security edge, the relevant evidence is to inspect gateway reachability from each secondary VLAN without direct host-to-host communication.

D:

That behavior applies when engineers “Configure a protocol-based VLAN ACL where needed”; the different operation “Configure a promiscuous PVLAN port for a shared gateway” is intended to provide primary-VLAN reachability to otherwise separated PVLAN hosts. That different feature is verified by inspect protocol classifier order and the VLAN ID assigned to matching traffic; for “Configure a promiscuous PVLAN port for a shared gateway” on a FortiSwitch connected to the security edge, the relevant evidence is to inspect gateway reachability from each secondary VLAN without direct host-to-host communication.

Question 620

A feature acceptance test on an access switch in routine maintenance concerns “Configure a promiscuous PVLAN port for a shared gateway.” What should be checked to establish its expected operation?

  1. Compare current FortiSwitch time with the configured schedule and observed rule counters
  2. Capture the double-tagged frame and verify distinct S-tag and customer C-tag fields
  3. Inspect gateway reachability from each secondary VLAN without direct host-to-host communication
  4. Compare captured source/destination IP fields and the rule's mask

Explanation

Correct Answer

C:

This is the precise control because the promiscuous port connects secondary VLANs to the common routed or shared service endpoint. Directly measuring that result demonstrates whether the step to provide primary-VLAN reachability to otherwise separated PVLAN hosts succeeded on an access switch in routine maintenance.

Incorrect Answers

A:

The proposed check concerns “Configure an ACL schedule” rather than “Configure a promiscuous PVLAN port for a shared gateway”: time-based ACL scheduling controls policy applicability, not the device system clock itself. For “Configure a promiscuous PVLAN port for a shared gateway” on an access switch in routine maintenance, a better test would be to inspect gateway reachability from each secondary VLAN without direct host-to-host communication, which targets provide primary-VLAN reachability to otherwise separated PVLAN hosts rather than the alternative diagnostic “Configure an ACL schedule”.

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 a promiscuous PVLAN port for a shared gateway” at the training center. Checking “Configure a promiscuous PVLAN port for a shared gateway” at the training center requires evidence of its own mechanism: the promiscuous port connects secondary VLANs to the common routed or shared service endpoint; that is not the outcome measured by “Use an 802.1Q QinQ outer service VLAN”.

D:

This check is suited to “Match an ACL using an IP subnet” when trying to filter traffic from a designated routed network range, not to verify “Configure a promiscuous PVLAN port for a shared gateway” at the training center. Checking “Configure a promiscuous PVLAN port for a shared gateway” at the training center requires evidence of its own mechanism: the promiscuous port connects secondary VLANs to the common routed or shared service endpoint; that is not the outcome measured by “Match an ACL using an IP subnet”.

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