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

Question 50

An operations log records this activity at the campus: classify frames using 802.1p PCP. Which result is specifically attributable to that action?

  1. DSCP in the IP header describes a forwarding class and can be mapped to switch QoS treatment
  2. The switch sends a media-endpoint network policy through LLDP-MED; it does not perform client authentication
  3. A policer meters selected frames and can drop or mark traffic that violates its profile
  4. The 802.1Q priority field supplies a layer-2 class that can be mapped to switch egress queues

Explanation

Correct Answer

D:

For the stated requirement, the configured operation is meant to distinguish priority of traffic at Ethernet VLAN-tag level. The most relevant validation is to inspect ingress PCP markings and the configured CoS-to-queue mapping for the affected ports for the equipment at the campus.

Incorrect Answers

A:

That behavior applies when engineers “Classify IP traffic by DSCP”; the different operation “Classify frames using 802.1p PCP” is intended to distinguish priority of traffic at Ethernet VLAN-tag level. That different feature is verified by capture a marked IP packet and compare its DSCP with the switch QoS profile; for “Classify frames using 802.1p PCP” on a central switching stack, the relevant evidence is to inspect ingress PCP markings and the configured CoS-to-queue mapping for the affected ports.

B:

That behavior applies when engineers “Advertise an LLDP-MED voice network policy”; the different operation “Classify frames using 802.1p PCP” is intended to distinguish priority of traffic at Ethernet VLAN-tag level. That different feature is verified by read the LLDP-MED network-policy TLV reported by the attached phone; for “Classify frames using 802.1p PCP” on a central switching stack, the relevant evidence is to inspect ingress PCP markings and the configured CoS-to-queue mapping for the affected ports.

C:

This outcome would be relevant to “Police a traffic class with an ACL policer” at the campus, not the task “Classify frames using 802.1p PCP”; the other task is to constrain an identified flow that exceeds the permitted rate. The action “Classify frames using 802.1p PCP” targets a different result: the 802.1Q priority field supplies a layer-2 class that can be mapped to switch egress queues; the proposed alternative would instead be checked by read policer statistics and compare conforming versus exceeding packet counters.

Question 51

A technician says “Classify frames using 802.1p PCP” has solved the issue at the remote depot. Which diagnostic step would substantiate that claim?

  1. Examine which port policy accepts the PCP or DSCP markings and whether the endpoint is trusted
  2. Inspect ingress PCP markings and the configured CoS-to-queue mapping for the affected ports
  3. Check the phone's learned voice VLAN and the switch's VLAN membership for that port
  4. Inspect the LLDP neighbor table for the expected chassis and port IDs

Explanation

Correct Answer

B:

The deciding detail is that the 802.1Q priority field supplies a layer-2 class that can be mapped to switch egress queues. Directly measuring that result demonstrates whether the step to distinguish priority of traffic at Ethernet VLAN-tag level succeeded on a FortiSwitch connected to the security edge.

Incorrect Answers

A:

This check is suited to “Trust marked endpoint traffic only on a designated port” when trying to avoid accepting arbitrary priority claims from untrusted user-facing ports, not to verify “Classify frames using 802.1p PCP” at the remote depot. Checking “Classify frames using 802.1p PCP” at the remote depot requires evidence of its own mechanism: the 802.1Q priority field supplies a layer-2 class that can be mapped to switch egress queues; that is not the outcome measured by “Trust marked endpoint traffic only on a designated port”.

C:

This check is suited to “Set an explicit voice VLAN on a phone-facing port” when trying to separate voice traffic from ordinary data while an IP phone shares the link with a PC, not to verify “Classify frames using 802.1p PCP” at the remote depot. Checking “Classify frames using 802.1p PCP” at the remote depot requires evidence of its own mechanism: the 802.1Q priority field supplies a layer-2 class that can be mapped to switch egress queues; that is not the outcome measured by “Set an explicit voice VLAN on a phone-facing port”.

D:

The proposed check concerns “Enable LLDP neighbor discovery” rather than “Classify frames using 802.1p PCP”: LLDP advertises local device identity and port metadata to directly connected neighbors. For “Classify frames using 802.1p PCP” on a FortiSwitch connected to the security edge, a better test would be to inspect ingress PCP markings and the configured CoS-to-queue mapping for the affected ports, which targets distinguish priority of traffic at Ethernet VLAN-tag level rather than the alternative diagnostic “Enable LLDP neighbor discovery”.

Question 52

A deployment review at the lab identifies this objective: preserve application classes across routed networks. Which FortiSwitch operation should be selected?

  1. Remark DSCP for a marked class
  2. Police a traffic class with an ACL policer
  3. Classify frames using 802.1p PCP
  4. Classify IP traffic by DSCP

Explanation

Correct Answer

D:

The relevant mechanism is: DSCP in the IP header describes a forwarding class and can be mapped to switch QoS treatment. The operator can test this claim by the specific check: capture a marked IP packet and compare its DSCP with the switch QoS profile.

Incorrect Answers

A:

For the lab, “Remark DSCP for a marked class” is a different type of control from “Classify IP traffic by DSCP”: remarking changes packet QoS bits for subsequent network devices rather than installing a route. Unlike the requested feature, that setting addresses the need to normalize packet priority markings across a trust boundary, not the objective to preserve application classes across routed networks.

B:

Compared with the requested “Classify IP traffic by DSCP” at the lab, this would constrain an identified flow that exceeds the permitted rate instead: a policer meters selected frames and can drop or mark traffic that violates its profile. At the lab, the operational proof would instead be to capture a marked IP packet and compare its DSCP with the switch QoS profile, whereas “Police a traffic class with an ACL policer” is validated by a different test: read policer statistics and compare conforming versus exceeding packet counters.

C:

Compared with the requested “Classify IP traffic by DSCP” at the lab, this would distinguish priority of traffic at Ethernet VLAN-tag level instead: the 802.1Q priority field supplies a layer-2 class that can be mapped to switch egress queues. At the lab, the operational proof would instead be to capture a marked IP packet and compare its DSCP with the switch QoS profile, whereas “Classify frames using 802.1p PCP” is validated by a different test: inspect ingress PCP markings and the configured CoS-to-queue mapping for the affected ports.

Question 53

When engineers classify IP traffic by DSCP at the staging rack, which forwarding, security, management or diagnostic outcome follows from that action?

  1. The chosen trust configuration affects classification of received markings; it does not authenticate the user
  2. A policer meters selected frames and can drop or mark traffic that violates its profile
  3. LLDP advertises local device identity and port metadata to directly connected neighbors
  4. DSCP in the IP header describes a forwarding class and can be mapped to switch QoS treatment
  5. The switch sends a media-endpoint network policy through LLDP-MED; it does not perform client authentication

Explanation

Correct Answer

D:

This approach fits because the configured operation is meant to preserve application classes across routed networks. The most relevant validation is to capture a marked IP packet and compare its DSCP with the switch QoS profile for the equipment at the staging rack.

Incorrect Answers

A:

This outcome would be relevant to “Trust marked endpoint traffic only on a designated port” at the staging rack, not the task “Classify IP traffic by DSCP”; the other task is to avoid accepting arbitrary priority claims from untrusted user-facing ports. The action “Classify IP traffic by DSCP” targets a different result: DSCP in the IP header describes a forwarding class and can be mapped to switch QoS treatment; the proposed alternative would instead be checked by examine which port policy accepts the PCP or DSCP markings and whether the endpoint is trusted.

B:

That behavior applies when engineers “Police a traffic class with an ACL policer”; the different operation “Classify IP traffic by DSCP” is intended to preserve application classes across routed networks. That different feature is verified by read policer statistics and compare conforming versus exceeding packet counters; for “Classify IP traffic by DSCP” on a newly racked distribution unit, the relevant evidence is to capture a marked IP packet and compare its DSCP with the switch QoS profile.

C:

That behavior applies when engineers “Enable LLDP neighbor discovery”; the different operation “Classify IP traffic by DSCP” is intended to preserve application classes across routed networks. That different feature is verified by inspect the LLDP neighbor table for the expected chassis and port IDs; for “Classify IP traffic by DSCP” on a newly racked distribution unit, the relevant evidence is to capture a marked IP packet and compare its DSCP with the switch QoS profile.

E:

That behavior applies when engineers “Advertise an LLDP-MED voice network policy”; the different operation “Classify IP traffic by DSCP” is intended to preserve application classes across routed networks. That different feature is verified by read the LLDP-MED network-policy TLV reported by the attached phone; for “Classify IP traffic by DSCP” on a newly racked distribution unit, the relevant evidence is to capture a marked IP packet and compare its DSCP with the switch QoS profile.

Question 54

After implementing “Classify IP traffic by DSCP,” the site engineer needs to assess its actual effect on two distribution switches. Which test is the best match?

  1. Query the LLDP-MED neighbor detail for capabilities and device class
  2. Inspect queue counters and the egress CoS queue policy during congestion
  3. Capture a marked IP packet and compare its DSCP with the switch QoS profile
  4. Check the phone's learned voice VLAN and the switch's VLAN membership for that port

Explanation

Correct Answer

C:

The critical distinction is that DSCP in the IP header describes a forwarding class and can be mapped to switch QoS treatment. Directly measuring that result demonstrates whether the step to preserve application classes across routed networks succeeded on two distribution switches.

Incorrect Answers

A:

This check is suited to “Use LLDP-MED device capability advertisement” when trying to allow a network administrator to determine whether a neighbor supports media-endpoint extensions, not to verify “Classify IP traffic by DSCP” at the research building. Checking “Classify IP traffic by DSCP” at the research building requires evidence of its own mechanism: DSCP in the IP header describes a forwarding class and can be mapped to switch QoS treatment; that is not the outcome measured by “Use LLDP-MED device capability advertisement”.

B:

The proposed check concerns “Map traffic classes to egress queues” rather than “Classify IP traffic by DSCP”: a QoS queue policy controls scheduling priority or resource share at the output interface. For “Classify IP traffic by DSCP” on two distribution switches, a better test would be to capture a marked IP packet and compare its DSCP with the switch QoS profile, which targets preserve application classes across routed networks rather than the alternative diagnostic “Map traffic classes to egress queues”.

D:

This check is suited to “Set an explicit voice VLAN on a phone-facing port” when trying to separate voice traffic from ordinary data while an IP phone shares the link with a PC, not to verify “Classify IP traffic by DSCP” at the research building. Checking “Classify IP traffic by DSCP” at the research building requires evidence of its own mechanism: DSCP in the IP header describes a forwarding class and can be mapped to switch QoS treatment; that is not the outcome measured by “Set an explicit voice VLAN on a phone-facing port”.

Question 55

On a staging FortiSwitch in the clinic, the next task is to tell an IP phone which voice VLAN and traffic-priority policy to use. What is the appropriate configuration decision?

  1. Advertise an LLDP-MED voice network policy
  2. Remark DSCP for a marked class
  3. Configure ingress CoS classification
  4. Set an LLDP-MED location policy

Explanation

Correct Answer

A:

That setting is appropriate here because the switch sends a media-endpoint network policy through LLDP-MED; it does not perform client authentication. This distinction is material to the clinic, where the stated goal is to tell an IP phone which voice VLAN and traffic-priority policy to use.

Incorrect Answers

B:

Compared with the requested “Advertise an LLDP-MED voice network policy” at the clinic, this would normalize packet priority markings across a trust boundary instead: remarking changes packet QoS bits for subsequent network devices rather than installing a route. At the clinic, the operational proof would instead be to read the LLDP-MED network-policy TLV reported by the attached phone, whereas “Remark DSCP for a marked class” is validated by a different test: capture ingress and egress IP headers and compare their DSCP fields.

C:

For the clinic, “Configure ingress CoS classification” is a different type of control from “Advertise an LLDP-MED voice network policy”: classification rules can map recognized 802.1p or DSCP values to internal priority treatment. Unlike the requested feature, that setting addresses the need to assign frames to a service class as they arrive at an access port, not the objective to tell an IP phone which voice VLAN and traffic-priority policy to use.

D:

Compared with the requested “Advertise an LLDP-MED voice network policy” at the clinic, this would provide location-identification metadata for supported media endpoints instead: an LLDP-MED location TLV supplies location information; it does not route packets to emergency services. At the clinic, the operational proof would instead be to read the LLDP-MED network-policy TLV reported by the attached phone, whereas “Set an LLDP-MED location policy” is validated by a different test: inspect the location TLV being advertised and verify endpoint acceptance.

Question 56

A colleague asks about the effect of “Advertise an LLDP-MED voice network policy” on a carefully segmented Layer 2 network. Which behavior best characterizes that feature?

  1. The 802.1Q priority field supplies a layer-2 class that can be mapped to switch egress queues
  2. A policer meters selected frames and can drop or mark traffic that violates its profile
  3. The switch sends a media-endpoint network policy through LLDP-MED; it does not perform client authentication
  4. Remarking changes packet QoS bits for subsequent network devices rather than installing a route
  5. DSCP in the IP header describes a forwarding class and can be mapped to switch QoS treatment

Explanation

Correct Answer

C:

This is the precise control because the configured operation is meant to tell an IP phone which voice VLAN and traffic-priority policy to use. The most relevant validation is to read the LLDP-MED network-policy TLV reported by the attached phone for the equipment at the data hall.

Incorrect Answers

A:

That behavior applies when engineers “Classify frames using 802.1p PCP”; the different operation “Advertise an LLDP-MED voice network policy” is intended to tell an IP phone which voice VLAN and traffic-priority policy to use. That different feature is verified by inspect ingress PCP markings and the configured CoS-to-queue mapping for the affected ports; for “Advertise an LLDP-MED voice network policy” on a carefully segmented Layer 2 network, the relevant evidence is to read the LLDP-MED network-policy TLV reported by the attached phone.

B:

This outcome would be relevant to “Police a traffic class with an ACL policer” at the data hall, not the task “Advertise an LLDP-MED voice network policy”; the other task is to constrain an identified flow that exceeds the permitted rate. The action “Advertise an LLDP-MED voice network policy” targets a different result: the switch sends a media-endpoint network policy through LLDP-MED; it does not perform client authentication; the proposed alternative would instead be checked by read policer statistics and compare conforming versus exceeding packet counters.

D:

That behavior applies when engineers “Remark DSCP for a marked class”; the different operation “Advertise an LLDP-MED voice network policy” is intended to tell an IP phone which voice VLAN and traffic-priority policy to use. That different feature is verified by capture ingress and egress IP headers and compare their DSCP fields; for “Advertise an LLDP-MED voice network policy” on a carefully segmented Layer 2 network, the relevant evidence is to read the LLDP-MED network-policy TLV reported by the attached phone.

E:

That behavior applies when engineers “Classify IP traffic by DSCP”; the different operation “Advertise an LLDP-MED voice network policy” is intended to tell an IP phone which voice VLAN and traffic-priority policy to use. That different feature is verified by capture a marked IP packet and compare its DSCP with the switch QoS profile; for “Advertise an LLDP-MED voice network policy” on a carefully segmented Layer 2 network, the relevant evidence is to read the LLDP-MED network-policy TLV reported by the attached phone.

Question 57

The change-control ticket for a central switching stack requires one validation of the goal to tell an IP phone which voice VLAN and traffic-priority policy to use. Which evidence should be collected?

  1. Examine which port policy accepts the PCP or DSCP markings and whether the endpoint is trusted
  2. Check the phone's learned voice VLAN and the switch's VLAN membership for that port
  3. Read the LLDP-MED network-policy TLV reported by the attached phone
  4. Inspect the LLDP neighbor table for the expected chassis and port IDs

Explanation

Correct Answer

C:

The implementation works because the switch sends a media-endpoint network policy through LLDP-MED; it does not perform client authentication. Directly measuring that result demonstrates whether the step to tell an IP phone which voice VLAN and traffic-priority policy to use succeeded on a central switching stack.

Incorrect Answers

A:

This check is suited to “Trust marked endpoint traffic only on a designated port” when trying to avoid accepting arbitrary priority claims from untrusted user-facing ports, not to verify “Advertise an LLDP-MED voice network policy” at the development floor. Checking “Advertise an LLDP-MED voice network policy” at the development floor requires evidence of its own mechanism: the switch sends a media-endpoint network policy through LLDP-MED; it does not perform client authentication; that is not the outcome measured by “Trust marked endpoint traffic only on a designated port”.

B:

This check is suited to “Set an explicit voice VLAN on a phone-facing port” when trying to separate voice traffic from ordinary data while an IP phone shares the link with a PC, not to verify “Advertise an LLDP-MED voice network policy” at the development floor. Checking “Advertise an LLDP-MED voice network policy” at the development floor requires evidence of its own mechanism: the switch sends a media-endpoint network policy through LLDP-MED; it does not perform client authentication; that is not the outcome measured by “Set an explicit voice VLAN on a phone-facing port”.

D:

The proposed check concerns “Enable LLDP neighbor discovery” rather than “Advertise an LLDP-MED voice network policy”: LLDP advertises local device identity and port metadata to directly connected neighbors. For “Advertise an LLDP-MED voice network policy” on a central switching stack, a better test would be to read the LLDP-MED network-policy TLV reported by the attached phone, which targets tell an IP phone which voice VLAN and traffic-priority policy to use rather than the alternative diagnostic “Enable LLDP neighbor discovery”.

Question 58

At the conference venue, a technician is choosing between several switching features to identify the directly attached switch or endpoint without relying on IP reachability. Which one belongs in the implementation plan?

  1. Use LLDP-MED device capability advertisement
  2. Set an LLDP-MED location policy
  3. Enable LLDP neighbor discovery
  4. Configure ingress CoS classification

Explanation

Correct Answer

C:

Given the described goal, LLDP advertises local device identity and port metadata to directly connected neighbors. The operator can test this claim by the specific check: inspect the LLDP neighbor table for the expected chassis and port IDs.

Incorrect Answers

A:

For the conference venue, “Use LLDP-MED device capability advertisement” is a different type of control from “Enable LLDP neighbor discovery”: LLDP-MED capability TLVs identify supported endpoint functions independently of IP addressing. Unlike the requested feature, that setting addresses the need to allow a network administrator to determine whether a neighbor supports media-endpoint extensions, not the objective to identify the directly attached switch or endpoint without relying on IP reachability.

B:

Compared with the requested “Enable LLDP neighbor discovery” at the conference venue, this would provide location-identification metadata for supported media endpoints instead: an LLDP-MED location TLV supplies location information; it does not route packets to emergency services. At the conference venue, the operational proof would instead be to inspect the LLDP neighbor table for the expected chassis and port IDs, whereas “Set an LLDP-MED location policy” is validated by a different test: inspect the location TLV being advertised and verify endpoint acceptance.

D:

Compared with the requested “Enable LLDP neighbor discovery” at the conference venue, this would assign frames to a service class as they arrive at an access port instead: classification rules can map recognized 802.1p or DSCP values to internal priority treatment. At the conference venue, the operational proof would instead be to inspect the LLDP neighbor table for the expected chassis and port IDs, whereas “Configure ingress CoS classification” is validated by a different test: compare ingress policy matches against traffic class and downstream queue assignment.

Question 59

When engineers enable LLDP neighbor discovery at the hospital wing, which forwarding, security, management or diagnostic outcome follows from that action?

  1. LLDP advertises local device identity and port metadata to directly connected neighbors
  2. The 802.1Q priority field supplies a layer-2 class that can be mapped to switch egress queues
  3. A policer meters selected frames and can drop or mark traffic that violates its profile
  4. Remarking changes packet QoS bits for subsequent network devices rather than installing a route

Explanation

Correct Answer

A:

The switch behavior that matters is: the configured operation is meant to identify the directly attached switch or endpoint without relying on IP reachability. The most relevant validation is to inspect the LLDP neighbor table for the expected chassis and port IDs for the equipment at the hospital wing.

Incorrect Answers

B:

This outcome would be relevant to “Classify frames using 802.1p PCP” at the hospital wing, not the task “Enable LLDP neighbor discovery”; the other task is to distinguish priority of traffic at Ethernet VLAN-tag level. The action “Enable LLDP neighbor discovery” targets a different result: LLDP advertises local device identity and port metadata to directly connected neighbors; the proposed alternative would instead be checked by inspect ingress PCP markings and the configured CoS-to-queue mapping for the affected ports.

C:

That behavior applies when engineers “Police a traffic class with an ACL policer”; the different operation “Enable LLDP neighbor discovery” is intended to identify the directly attached switch or endpoint without relying on IP reachability. That different feature is verified by read policer statistics and compare conforming versus exceeding packet counters; for “Enable LLDP neighbor discovery” on an access switch in routine maintenance, the relevant evidence is to inspect the LLDP neighbor table for the expected chassis and port IDs.

D:

That behavior applies when engineers “Remark DSCP for a marked class”; the different operation “Enable LLDP neighbor discovery” is intended to identify the directly attached switch or endpoint without relying on IP reachability. That different feature is verified by capture ingress and egress IP headers and compare their DSCP fields; for “Enable LLDP neighbor discovery” on an access switch in routine maintenance, the relevant evidence is to inspect the LLDP neighbor table for the expected chassis and port IDs.

Question 60

A FortiSwitch engineer in the training center is documenting successful operation of “Enable LLDP neighbor discovery.” Which measurement or inspection confirms it?

  1. Read policer statistics and compare conforming versus exceeding packet counters
  2. Inspect the LLDP neighbor table for the expected chassis and port IDs
  3. Examine which port policy accepts the PCP or DSCP markings and whether the endpoint is trusted
  4. Read the LLDP-MED network-policy TLV reported by the attached phone
  5. Capture a marked IP packet and compare its DSCP with the switch QoS profile

Explanation

Correct Answer

B:

At this network boundary, LLDP advertises local device identity and port metadata to directly connected neighbors. Directly measuring that result demonstrates whether the step to identify the directly attached switch or endpoint without relying on IP reachability succeeded on a managed campus switch.

Incorrect Answers

A:

The proposed check concerns “Police a traffic class with an ACL policer” rather than “Enable LLDP neighbor discovery”: a policer meters selected frames and can drop or mark traffic that violates its profile. For “Enable LLDP neighbor discovery” on a managed campus switch, a better test would be to inspect the LLDP neighbor table for the expected chassis and port IDs, which targets identify the directly attached switch or endpoint without relying on IP reachability rather than the alternative diagnostic “Police a traffic class with an ACL policer”.

C:

The proposed check concerns “Trust marked endpoint traffic only on a designated port” rather than “Enable LLDP neighbor discovery”: the chosen trust configuration affects classification of received markings; it does not authenticate the user. For “Enable LLDP neighbor discovery” on a managed campus switch, a better test would be to inspect the LLDP neighbor table for the expected chassis and port IDs, which targets identify the directly attached switch or endpoint without relying on IP reachability rather than the alternative diagnostic “Trust marked endpoint traffic only on a designated port”.

D:

This check is suited to “Advertise an LLDP-MED voice network policy” when trying to tell an IP phone which voice VLAN and traffic-priority policy to use, not to verify “Enable LLDP neighbor discovery” at the training center. Checking “Enable LLDP neighbor discovery” at the training center requires evidence of its own mechanism: LLDP advertises local device identity and port metadata to directly connected neighbors; that is not the outcome measured by “Advertise an LLDP-MED voice network policy”.

E:

This check is suited to “Classify IP traffic by DSCP” when trying to preserve application classes across routed networks, not to verify “Enable LLDP neighbor discovery” at the training center. Checking “Enable LLDP neighbor discovery” at the training center requires evidence of its own mechanism: LLDP advertises local device identity and port metadata to directly connected neighbors; that is not the outcome measured by “Classify IP traffic by DSCP”.

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