Question 60
A FortiSwitch engineer in the training center is documenting successful operation of “Enable LLDP neighbor discovery.” Which measurement or inspection confirms it?
- Read policer statistics and compare conforming versus exceeding packet counters
- Inspect the LLDP neighbor table for the expected chassis and port IDs
- Examine which port policy accepts the PCP or DSCP markings and whether the endpoint is trusted
- Read the LLDP-MED network-policy TLV reported by the attached phone
- 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”.
Question 61
A switch rollout in the lab will be approved only if it can apply differentiated forwarding when several flows contend for a busy uplink. Which administrative action meets this acceptance criterion?
- Map traffic classes to egress queues
- Set an LLDP-MED location policy
- Classify frames using 802.1p PCP
- Remark DSCP for a marked class
Explanation
Correct Answer
A:In this deployment, a QoS queue policy controls scheduling priority or resource share at the output interface. This distinction is material to the lab, where the stated goal is to apply differentiated forwarding when several flows contend for a busy uplink.
Incorrect Answers
B:For the lab, “Set an LLDP-MED location policy” is a different type of control from “Map traffic classes to egress queues”: an LLDP-MED location TLV supplies location information; it does not route packets to emergency services. Unlike the requested feature, that setting addresses the need to provide location-identification metadata for supported media endpoints, not the objective to apply differentiated forwarding when several flows contend for a busy uplink.
C:Compared with the requested “Map traffic classes to egress queues” 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 inspect queue counters and the egress CoS queue policy during congestion, 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.
D:Compared with the requested “Map traffic classes to egress queues” at the lab, 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 lab, the operational proof would instead be to inspect queue counters and the egress CoS queue policy during congestion, whereas “Remark DSCP for a marked class” is validated by a different test: capture ingress and egress IP headers and compare their DSCP fields.
Question 62
A colleague asks about the effect of “Map traffic classes to egress queues” on a FortiLink-managed access switch. Which behavior best characterizes that feature?
- The chosen trust configuration affects classification of received markings; it does not authenticate the user
- A policer meters selected frames and can drop or mark traffic that violates its profile
- A QoS queue policy controls scheduling priority or resource share at the output interface
- DSCP in the IP header describes a forwarding class and can be mapped to switch QoS treatment
Explanation
Correct Answer
C:For the stated requirement, the configured operation is meant to apply differentiated forwarding when several flows contend for a busy uplink. The most relevant validation is to inspect queue counters and the egress CoS queue policy during congestion for the equipment at the staging rack.
Incorrect Answers
A:That behavior applies when engineers “Trust marked endpoint traffic only on a designated port”; the different operation “Map traffic classes to egress queues” is intended to apply differentiated forwarding when several flows contend for a busy uplink. That different feature is verified by examine which port policy accepts the PCP or DSCP markings and whether the endpoint is trusted; for “Map traffic classes to egress queues” on a FortiLink-managed access switch, the relevant evidence is to inspect queue counters and the egress CoS queue policy during congestion.
B:That behavior applies when engineers “Police a traffic class with an ACL policer”; the different operation “Map traffic classes to egress queues” is intended to apply differentiated forwarding when several flows contend for a busy uplink. That different feature is verified by read policer statistics and compare conforming versus exceeding packet counters; for “Map traffic classes to egress queues” on a FortiLink-managed access switch, the relevant evidence is to inspect queue counters and the egress CoS queue policy during congestion.
D:This outcome would be relevant to “Classify IP traffic by DSCP” at the staging rack, not the task “Map traffic classes to egress queues”; the other task is to preserve application classes across routed networks. The action “Map traffic classes to egress queues” targets a different result: a QoS queue policy controls scheduling priority or resource share at the output interface; the proposed alternative would instead be checked by capture a marked IP packet and compare its DSCP with the switch QoS profile.
Question 63
A feature acceptance test on a switch linked to a FortiGate running FortiOS 7.6 concerns “Map traffic classes to egress queues.” What should be checked to establish its expected operation?
- Read the LLDP-MED network-policy TLV reported by the attached phone
- Inspect the LLDP neighbor table for the expected chassis and port IDs
- Check the phone's learned voice VLAN and the switch's VLAN membership for that port
- Inspect queue counters and the egress CoS queue policy during congestion
Explanation
Correct Answer
D:The deciding detail is that a QoS queue policy controls scheduling priority or resource share at the output interface. Directly measuring that result demonstrates whether the step to apply differentiated forwarding when several flows contend for a busy uplink succeeded on a switch linked to a FortiGate running FortiOS 7.6.
Incorrect Answers
A: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 “Map traffic classes to egress queues” at the research building. Checking “Map traffic classes to egress queues” at the research building requires evidence of its own mechanism: a QoS queue policy controls scheduling priority or resource share at the output interface; that is not the outcome measured by “Advertise an LLDP-MED voice network policy”.
B:This check is suited to “Enable LLDP neighbor discovery” when trying to identify the directly attached switch or endpoint without relying on IP reachability, not to verify “Map traffic classes to egress queues” at the research building. Checking “Map traffic classes to egress queues” at the research building requires evidence of its own mechanism: a QoS queue policy controls scheduling priority or resource share at the output interface; that is not the outcome measured by “Enable LLDP neighbor discovery”.
C:The proposed check concerns “Set an explicit voice VLAN on a phone-facing port” rather than “Map traffic classes to egress queues”: the configured voice VLAN and advertised policy identify phone traffic, while data retains its intended VLAN. For “Map traffic classes to egress queues” on a switch linked to a FortiGate running FortiOS 7.6, a better test would be to inspect queue counters and the egress CoS queue policy during congestion, which targets apply differentiated forwarding when several flows contend for a busy uplink rather than the alternative diagnostic “Set an explicit voice VLAN on a phone-facing port”.
Question 64
An administrator responsible for a switch serving a high-density endpoint area in the clinic must assign frames to a service class as they arrive at an access port. Which configuration best matches that precise goal?
- Configure ingress CoS classification
- Remark DSCP for a marked class
- Set an LLDP-MED location policy
- Classify frames using 802.1p PCP
- Police a traffic class with an ACL policer
Explanation
Correct Answer
A:The relevant mechanism is: classification rules can map recognized 802.1p or DSCP values to internal priority treatment. The operator can test this claim by the specific check: compare ingress policy matches against traffic class and downstream queue assignment.
Incorrect Answers
B:For the clinic, “Remark DSCP for a marked class” is a different type of control from “Configure ingress CoS classification”: 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 assign frames to a service class as they arrive at an access port.
C:Compared with the requested “Configure ingress CoS classification” 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 compare ingress policy matches against traffic class and downstream queue assignment, 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 “Configure ingress CoS classification” at the clinic, 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 clinic, the operational proof would instead be to compare ingress policy matches against traffic class and downstream queue assignment, 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.
E:Compared with the requested “Configure ingress CoS classification” at the clinic, 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 clinic, the operational proof would instead be to compare ingress policy matches against traffic class and downstream queue assignment, 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.
Question 65
When engineers configure ingress CoS classification at the data hall, which forwarding, security, management or diagnostic outcome follows from that action?
- The switch sends a media-endpoint network policy through LLDP-MED; it does not perform client authentication
- Classification rules can map recognized 802.1p or DSCP values to internal priority treatment
- The chosen trust configuration affects classification of received markings; it does not authenticate the user
- DSCP in the IP header describes a forwarding class and can be mapped to switch QoS treatment
Explanation
Correct Answer
B:This approach fits because the configured operation is meant to assign frames to a service class as they arrive at an access port. The most relevant validation is to compare ingress policy matches against traffic class and downstream queue assignment for the equipment at the data hall.
Incorrect Answers
A:That behavior applies when engineers “Advertise an LLDP-MED voice network policy”; the different operation “Configure ingress CoS classification” is intended to assign frames to a service class as they arrive at an access port. That different feature is verified by read the LLDP-MED network-policy TLV reported by the attached phone; for “Configure ingress CoS classification” on a managed switch running FortiSwitchOS 7.6, the relevant evidence is to compare ingress policy matches against traffic class and downstream queue assignment.
C:This outcome would be relevant to “Trust marked endpoint traffic only on a designated port” at the data hall, not the task “Configure ingress CoS classification”; the other task is to avoid accepting arbitrary priority claims from untrusted user-facing ports. The action “Configure ingress CoS classification” targets a different result: classification rules can map recognized 802.1p or DSCP values to internal priority 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.
D:That behavior applies when engineers “Classify IP traffic by DSCP”; the different operation “Configure ingress CoS classification” is intended to assign frames to a service class as they arrive at an access port. That different feature is verified by capture a marked IP packet and compare its DSCP with the switch QoS profile; for “Configure ingress CoS classification” on a managed switch running FortiSwitchOS 7.6, the relevant evidence is to compare ingress policy matches against traffic class and downstream queue assignment.
Question 66
On an access switch in routine maintenance at the warehouse, the team reports that it has configured “Configure ingress CoS classification.” Which verification provides the strongest direct evidence that the intended function is working?
- Check the phone's learned voice VLAN and the switch's VLAN membership for that port
- Inspect the LLDP neighbor table for the expected chassis and port IDs
- Query the LLDP-MED neighbor detail for capabilities and device class
- Compare ingress policy matches against traffic class and downstream queue assignment
Explanation
Correct Answer
D:The critical distinction is that classification rules can map recognized 802.1p or DSCP values to internal priority treatment. Directly measuring that result demonstrates whether the step to assign frames to a service class as they arrive at an access port succeeded on an access switch in routine maintenance.
Incorrect Answers
A: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 “Configure ingress CoS classification” at the warehouse. Checking “Configure ingress CoS classification” at the warehouse requires evidence of its own mechanism: classification rules can map recognized 802.1p or DSCP values to internal priority treatment; that is not the outcome measured by “Set an explicit voice VLAN on a phone-facing port”.
B:The proposed check concerns “Enable LLDP neighbor discovery” rather than “Configure ingress CoS classification”: LLDP advertises local device identity and port metadata to directly connected neighbors. For “Configure ingress CoS classification” on an access switch in routine maintenance, a better test would be to compare ingress policy matches against traffic class and downstream queue assignment, which targets assign frames to a service class as they arrive at an access port rather than the alternative diagnostic “Enable LLDP neighbor discovery”.
C: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 “Configure ingress CoS classification” at the warehouse. Checking “Configure ingress CoS classification” at the warehouse requires evidence of its own mechanism: classification rules can map recognized 802.1p or DSCP values to internal priority treatment; that is not the outcome measured by “Use LLDP-MED device capability advertisement”.
Question 67
A peer review of the headquarters asks how the design will normalize packet priority markings across a trust boundary. Which FortiSwitch technique is the correct response?
- Remark DSCP for a marked class
- Police a traffic class with an ACL policer
- Classify frames using 802.1p PCP
- Set an LLDP-MED location policy
- Configure ingress CoS classification
Explanation
Correct Answer
A:That setting is appropriate here because remarking changes packet QoS bits for subsequent network devices rather than installing a route. This distinction is material to the headquarters, where the stated goal is to normalize packet priority markings across a trust boundary.
Incorrect Answers
B:Compared with the requested “Remark DSCP for a marked class” at the headquarters, 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 headquarters, the operational proof would instead be to capture ingress and egress IP headers and compare their DSCP fields, 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 “Remark DSCP for a marked class” at the headquarters, 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 headquarters, the operational proof would instead be to capture ingress and egress IP headers and compare their DSCP fields, 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.
D:Compared with the requested “Remark DSCP for a marked class” at the headquarters, 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 headquarters, the operational proof would instead be to capture ingress and egress IP headers and compare their DSCP fields, whereas “Set an LLDP-MED location policy” is validated by a different test: inspect the location TLV being advertised and verify endpoint acceptance.
E:For the headquarters, “Configure ingress CoS classification” is a different type of control from “Remark DSCP for a marked class”: 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 normalize packet priority markings across a trust boundary.
Question 68
A colleague asks about the effect of “Remark DSCP for a marked class” on a recently upgraded FortiSwitch. Which behavior best characterizes that feature?
- DSCP in the IP header describes a forwarding class and can be mapped to switch QoS treatment
- The chosen trust configuration affects classification of received markings; it does not authenticate the user
- The switch sends a media-endpoint network policy through LLDP-MED; it does not perform client authentication
- Remarking changes packet QoS bits for subsequent network devices rather than installing a route
Explanation
Correct Answer
D:This is the precise control because the configured operation is meant to normalize packet priority markings across a trust boundary. The most relevant validation is to capture ingress and egress IP headers and compare their DSCP fields for the equipment at the hospital wing.
Incorrect Answers
A:That behavior applies when engineers “Classify IP traffic by DSCP”; the different operation “Remark DSCP for a marked class” is intended to normalize packet priority markings across a trust boundary. That different feature is verified by capture a marked IP packet and compare its DSCP with the switch QoS profile; for “Remark DSCP for a marked class” on a recently upgraded FortiSwitch, the relevant evidence is to capture ingress and egress IP headers and compare their DSCP fields.
B:This outcome would be relevant to “Trust marked endpoint traffic only on a designated port” at the hospital wing, not the task “Remark DSCP for a marked class”; the other task is to avoid accepting arbitrary priority claims from untrusted user-facing ports. The action “Remark DSCP for a marked class” targets a different result: remarking changes packet QoS bits for subsequent network devices rather than installing a route; the proposed alternative would instead be checked by examine which port policy accepts the PCP or DSCP markings and whether the endpoint is trusted.
C:That behavior applies when engineers “Advertise an LLDP-MED voice network policy”; the different operation “Remark DSCP for a marked class” is intended to normalize packet priority markings across a trust boundary. That different feature is verified by read the LLDP-MED network-policy TLV reported by the attached phone; for “Remark DSCP for a marked class” on a recently upgraded FortiSwitch, the relevant evidence is to capture ingress and egress IP headers and compare their DSCP fields.
Question 69
A design review at the training center discusses “Remark DSCP for a marked class.” Select the TWO characteristics that belong to this feature. (Choose TWO.)
- The configured voice VLAN and advertised policy identify phone traffic, while data retains its intended VLAN
- Capture ingress and egress IP headers and compare their DSCP fields
- Remarking changes packet QoS bits for subsequent network devices rather than installing a route
- LLDP-MED capability TLVs identify supported endpoint functions independently of IP addressing
- LLDP advertises local device identity and port metadata to directly connected neighbors
Explanation
Correct Answers
B:The stated check directly tests whether the intended function is active at the training center. It provides evidence about “Remark DSCP for a marked class” beyond ordinary link-up state on a FortiLink-managed access switch.
C:The implementation works because the described mechanism corresponds to the operation that administrators use to normalize packet priority markings across a trust boundary. The result should be observable on a FortiLink-managed access switch.
Incorrect Answers
A:That characteristic reflects “Set an explicit voice VLAN on a phone-facing port” rather than “Remark DSCP for a marked class” at the training center. Its actual role is to separate voice traffic from ordinary data while an IP phone shares the link with a PC, a different configuration need.
D:That characteristic reflects “Use LLDP-MED device capability advertisement” rather than “Remark DSCP for a marked class” at the training center. Its actual role is to allow a network administrator to determine whether a neighbor supports media-endpoint extensions, a different configuration need.
E:That characteristic reflects “Enable LLDP neighbor discovery” rather than “Remark DSCP for a marked class” at the training center. Its actual role is to identify the directly attached switch or endpoint without relying on IP reachability, a different configuration need.
Question 70
A production incident in the lab reveals the need to constrain an identified flow that exceeds the permitted rate. Which targeted FortiSwitch setting or method should the team use?
- Classify IP traffic by DSCP
- Police a traffic class with an ACL policer
- Advertise an LLDP-MED voice network policy
- Trust marked endpoint traffic only on a designated port
Explanation
Correct Answer
B:Given the described goal, a policer meters selected frames and can drop or mark traffic that violates its profile. The operator can test this claim by the specific check: read policer statistics and compare conforming versus exceeding packet counters.
Incorrect Answers
A:For the lab, “Classify IP traffic by DSCP” is a different type of control from “Police a traffic class with an ACL policer”: DSCP in the IP header describes a forwarding class and can be mapped to switch QoS treatment. Unlike the requested feature, that setting addresses the need to preserve application classes across routed networks, not the objective to constrain an identified flow that exceeds the permitted rate.
C:Compared with the requested “Police a traffic class with an ACL policer” at the lab, this would tell an IP phone which voice VLAN and traffic-priority policy to use instead: the switch sends a media-endpoint network policy through LLDP-MED; it does not perform client authentication. At the lab, the operational proof would instead be to read policer statistics and compare conforming versus exceeding packet counters, whereas “Advertise an LLDP-MED voice network policy” is validated by a different test: read the LLDP-MED network-policy TLV reported by the attached phone.
D:Compared with the requested “Police a traffic class with an ACL policer” at the lab, this would avoid accepting arbitrary priority claims from untrusted user-facing ports instead: the chosen trust configuration affects classification of received markings; it does not authenticate the user. At the lab, the operational proof would instead be to read policer statistics and compare conforming versus exceeding packet counters, whereas “Trust marked endpoint traffic only on a designated port” is validated by a different test: examine which port policy accepts the PCP or DSCP markings and whether the endpoint is trusted.