Question 80
Before applying the planned operation “Use LLDP-MED device capability advertisement” at the media studio, the administrator must predict its impact. Which prediction is sound?
- A policer meters selected frames and can drop or mark traffic that violates its profile
- LLDP-MED capability TLVs identify supported endpoint functions independently of IP addressing
- DSCP in the IP header describes a forwarding class and can be mapped to switch QoS treatment
- Remarking changes packet QoS bits for subsequent network devices rather than installing a route
Explanation
Correct Answer
B:This is the precise control because the configured operation is meant to allow a network administrator to determine whether a neighbor supports media-endpoint extensions. The most relevant validation is to query the LLDP-MED neighbor detail for capabilities and device class for the equipment at the media studio.
Incorrect Answers
A:That behavior applies when engineers “Police a traffic class with an ACL policer”; the different operation “Use LLDP-MED device capability advertisement” is intended to allow a network administrator to determine whether a neighbor supports media-endpoint extensions. That different feature is verified by read policer statistics and compare conforming versus exceeding packet counters; for “Use LLDP-MED device capability advertisement” on a remote FortiSwitch installation, the relevant evidence is to query the LLDP-MED neighbor detail for capabilities and device class.
C:This outcome would be relevant to “Classify IP traffic by DSCP” at the media studio, not the task “Use LLDP-MED device capability advertisement”; the other task is to preserve application classes across routed networks. The action “Use LLDP-MED device capability advertisement” targets a different result: LLDP-MED capability TLVs identify supported endpoint functions independently of IP addressing; the proposed alternative would instead be checked by capture a marked IP packet and compare its DSCP with the switch QoS profile.
D:That behavior applies when engineers “Remark DSCP for a marked class”; the different operation “Use LLDP-MED device capability advertisement” is intended to allow a network administrator to determine whether a neighbor supports media-endpoint extensions. That different feature is verified by capture ingress and egress IP headers and compare their DSCP fields; for “Use LLDP-MED device capability advertisement” on a remote FortiSwitch installation, the relevant evidence is to query the LLDP-MED neighbor detail for capabilities and device class.
Question 81
The change-control ticket for an endpoint-facing FortiSwitch port requires one validation of the goal to allow a network administrator to determine whether a neighbor supports media-endpoint extensions. Which evidence should be collected?
- Query the LLDP-MED neighbor detail for capabilities and device class
- Examine which port policy accepts the PCP or DSCP markings and whether the endpoint is trusted
- Inspect the LLDP neighbor table for the expected chassis and port IDs
- Read the LLDP-MED network-policy TLV reported by the attached phone
Explanation
Correct Answer
A:The implementation works because LLDP-MED capability TLVs identify supported endpoint functions independently of IP addressing. Directly measuring that result demonstrates whether the step to allow a network administrator to determine whether a neighbor supports media-endpoint extensions succeeded on an endpoint-facing FortiSwitch port.
Incorrect Answers
B:The proposed check concerns “Trust marked endpoint traffic only on a designated port” rather than “Use LLDP-MED device capability advertisement”: the chosen trust configuration affects classification of received markings; it does not authenticate the user. For “Use LLDP-MED device capability advertisement” on an endpoint-facing FortiSwitch port, a better test would be to query the LLDP-MED neighbor detail for capabilities and device class, which targets allow a network administrator to determine whether a neighbor supports media-endpoint extensions rather than the alternative diagnostic “Trust marked endpoint traffic only on a designated port”.
C: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 “Use LLDP-MED device capability advertisement” at the retail site. Checking “Use LLDP-MED device capability advertisement” at the retail site requires evidence of its own mechanism: LLDP-MED capability TLVs identify supported endpoint functions independently of IP addressing; that is not the outcome measured by “Enable LLDP neighbor discovery”.
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 “Use LLDP-MED device capability advertisement” at the retail site. Checking “Use LLDP-MED device capability advertisement” at the retail site requires evidence of its own mechanism: LLDP-MED capability TLVs identify supported endpoint functions independently of IP addressing; that is not the outcome measured by “Advertise an LLDP-MED voice network policy”.
Question 82
A network architect documents a single goal for a standalone FortiSwitch appliance: provide location-identification metadata for supported media endpoints. Which listed procedure provides that capability?
- Enable LLDP neighbor discovery
- Trust marked endpoint traffic only on a designated port
- Map traffic classes to egress queues
- Set an explicit voice VLAN on a phone-facing port
- Set an LLDP-MED location policy
Explanation
Correct Answer
E:Given the described goal, an LLDP-MED location TLV supplies location information; it does not route packets to emergency services. The operator can test this claim by the specific check: inspect the location TLV being advertised and verify endpoint acceptance.
Incorrect Answers
A:For the airport office, “Enable LLDP neighbor discovery” is a different type of control from “Set an LLDP-MED location policy”: LLDP advertises local device identity and port metadata to directly connected neighbors. Unlike the requested feature, that setting addresses the need to identify the directly attached switch or endpoint without relying on IP reachability, not the objective to provide location-identification metadata for supported media endpoints.
B:Compared with the requested “Set an LLDP-MED location policy” at the airport office, 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 airport office, the operational proof would instead be to inspect the location TLV being advertised and verify endpoint acceptance, 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.
C:Compared with the requested “Set an LLDP-MED location policy” at the airport office, this would apply differentiated forwarding when several flows contend for a busy uplink instead: a QoS queue policy controls scheduling priority or resource share at the output interface. At the airport office, the operational proof would instead be to inspect the location TLV being advertised and verify endpoint acceptance, whereas “Map traffic classes to egress queues” is validated by a different test: inspect queue counters and the egress CoS queue policy during congestion.
D:Compared with the requested “Set an LLDP-MED location policy” at the airport office, this would separate voice traffic from ordinary data while an IP phone shares the link with a PC instead: the configured voice VLAN and advertised policy identify phone traffic, while data retains its intended VLAN. At the airport office, the operational proof would instead be to inspect the location TLV being advertised and verify endpoint acceptance, whereas “Set an explicit voice VLAN on a phone-facing port” is validated by a different test: check the phone's learned voice VLAN and the switch's VLAN membership for that port.
Question 83
During validation of a newly commissioned floor switch at the operations center, the team asks what the change “Set an LLDP-MED location policy” actually does. Which outcome is correct?
- An LLDP-MED location TLV supplies location information; it does not route packets to emergency services
- The 802.1Q priority field supplies a layer-2 class that can be mapped to switch egress queues
- Classification rules can map recognized 802.1p or DSCP values to internal priority treatment
- LLDP-MED capability TLVs identify supported endpoint functions independently of IP addressing
Explanation
Correct Answer
A:The switch behavior that matters is: the configured operation is meant to provide location-identification metadata for supported media endpoints. The most relevant validation is to inspect the location TLV being advertised and verify endpoint acceptance for the equipment at the operations center.
Incorrect Answers
B:That behavior applies when engineers “Classify frames using 802.1p PCP”; the different operation “Set an LLDP-MED location policy” is intended to provide location-identification metadata for supported media endpoints. That different feature is verified by inspect ingress PCP markings and the configured CoS-to-queue mapping for the affected ports; for “Set an LLDP-MED location policy” on a newly commissioned floor switch, the relevant evidence is to inspect the location TLV being advertised and verify endpoint acceptance.
C:This outcome would be relevant to “Configure ingress CoS classification” at the operations center, not the task “Set an LLDP-MED location policy”; the other task is to assign frames to a service class as they arrive at an access port. The action “Set an LLDP-MED location policy” targets a different result: an LLDP-MED location TLV supplies location information; it does not route packets to emergency services; the proposed alternative would instead be checked by compare ingress policy matches against traffic class and downstream queue assignment.
D:That behavior applies when engineers “Use LLDP-MED device capability advertisement”; the different operation “Set an LLDP-MED location policy” is intended to provide location-identification metadata for supported media endpoints. That different feature is verified by query the LLDP-MED neighbor detail for capabilities and device class; for “Set an LLDP-MED location policy” on a newly commissioned floor switch, the relevant evidence is to inspect the location TLV being advertised and verify endpoint acceptance.
Question 84
During a change window in the warehouse, engineers are asked to manage several downstream FortiSwitch units through one upstream connected device. What should they configure rather than using a feature for an adjacent purpose?
- Establish redundant interchassis links for MCLAG
- Keep MCLAG peer hardware and software aligned
- Form a FortiLink-managed switch cascade
- Create a switch inter-switch link for FortiLink discovery
Explanation
Correct Answer
C:At this network boundary, an inter-switch link carries discovery and management traffic onward to additional managed switches. The operator can test this claim by the specific check: inspect the topology tree and confirm downstream serial numbers appear beneath the uplink switch.
Incorrect Answers
A:Compared with the requested “Form a FortiLink-managed switch cascade” at the warehouse, this would avoid losing the peer relationship when one cross-connect fails instead: the interchassis link communicates peer state; at least two links are recommended for ICL resilience. At the warehouse, the operational proof would instead be to inspect the topology tree and confirm downstream serial numbers appear beneath the uplink switch, whereas “Establish redundant interchassis links for MCLAG” is validated by a different test: check the ICL member status on both switches and verify a remaining path after a member fails.
B:Compared with the requested “Form a FortiLink-managed switch cascade” at the warehouse, this would avoid unsupported mismatches in a redundant switch pair instead: Fortinet recommends the same peer model and software version for a supported MCLAG design. At the warehouse, the operational proof would instead be to inspect the topology tree and confirm downstream serial numbers appear beneath the uplink switch, whereas “Keep MCLAG peer hardware and software aligned” is validated by a different test: compare model IDs and installed firmware versions before enabling the peer group.
D:For the warehouse, “Create a switch inter-switch link for FortiLink discovery” is a different type of control from “Form a FortiLink-managed switch cascade”: an ISL carries the FortiLink control reachability across the switch chain. Unlike the requested feature, that setting addresses the need to allow managed descendants to be discovered beyond the directly connected switch, not the objective to manage several downstream FortiSwitch units through one upstream connected device.
Question 85
During validation of a switch used by multiple office teams at the headquarters, the team asks what the change “Form a FortiLink-managed switch cascade” actually does. Which outcome is correct?
- Split-brain safeguards determine which peer should enter a dormant state under a detected isolation event
- Two peer FortiSwitch units present an aggregated logical attachment to dual-homed devices
- An inter-switch link carries discovery and management traffic onward to additional managed switches
- A supported HA/FortiLink wiring design provides connectivity to the FortiGate cluster rather than a single appliance
Explanation
Correct Answer
C:In this deployment, the configured operation is meant to manage several downstream FortiSwitch units through one upstream connected device. The most relevant validation is to inspect the topology tree and confirm downstream serial numbers appear beneath the uplink switch for the equipment at the headquarters.
Incorrect Answers
A:This outcome would be relevant to “Enable MCLAG split-brain detection on both peers” at the headquarters, not the task “Form a FortiLink-managed switch cascade”; the other task is to avoid both surviving switches independently claiming active service when the ICL is severed. The action “Form a FortiLink-managed switch cascade” targets a different result: an inter-switch link carries discovery and management traffic onward to additional managed switches; the proposed alternative would instead be checked by inspect peer split-brain state and configured priorities on each member.
B:That behavior applies when engineers “Build a two-peer MCLAG core”; the different operation “Form a FortiLink-managed switch cascade” is intended to manage several downstream FortiSwitch units through one upstream connected device. That different feature is verified by verify both peer states and the dual-homed trunk membership in the MCLAG monitor; for “Form a FortiLink-managed switch cascade” on a switch used by multiple office teams, the relevant evidence is to inspect the topology tree and confirm downstream serial numbers appear beneath the uplink switch.
D:That behavior applies when engineers “Connect FortiGate HA to a FortiLink stack”; the different operation “Form a FortiLink-managed switch cascade” is intended to manage several downstream FortiSwitch units through one upstream connected device. That different feature is verified by test an HA failover and monitor FortiSwitch authorization and control-plane reachability; for “Form a FortiLink-managed switch cascade” on a switch used by multiple office teams, the relevant evidence is to inspect the topology tree and confirm downstream serial numbers appear beneath the uplink switch.
Question 86
After the team configures “Form a FortiLink-managed switch cascade” on a production FortiSwitch fabric, which TWO claims about the configuration are valid? (Choose TWO.)
- Inspect the topology tree and confirm downstream serial numbers appear beneath the uplink switch
- MCLAG STP awareness coordinates the spanning-tree view of the aggregated downstream attachment
- An MCLAG presents the pair as a logical LACP partner for the access switch
- An inter-switch link carries discovery and management traffic onward to additional managed switches
- A logical aggregate can carry FortiLink when the topology and split-interface settings match its design
Explanation
Correct Answers
A:The stated check directly tests whether the intended function is active at the hospital wing. It provides evidence about “Form a FortiLink-managed switch cascade” beyond ordinary link-up state on a production FortiSwitch fabric.
D:For the stated requirement, the described mechanism corresponds to the operation that administrators use to manage several downstream FortiSwitch units through one upstream connected device. The result should be observable on a production FortiSwitch fabric.
Incorrect Answers
B:That characteristic reflects “Enable STP-aware MCLAG behavior where required” rather than “Form a FortiLink-managed switch cascade” at the hospital wing. Its actual role is to keep bridge-loop protection consistent when LAGs span peer switches, a different configuration need.
C:That characteristic reflects “Dual-home an access switch with LACP to MCLAG peers” rather than “Form a FortiLink-managed switch cascade” at the hospital wing. Its actual role is to provide two physical upstream switches without creating separate spanning-tree forwarding paths, a different configuration need.
E:That characteristic reflects “Use a FortiLink LAG with suitable member ports” rather than “Form a FortiLink-managed switch cascade” at the hospital wing. Its actual role is to increase resiliency of the FortiGate-to-switch management and data connection, a different configuration need.
Question 87
A deployment review at the factory identifies this objective: maintain data forwarding when one distribution switch stops responding. Which FortiSwitch operation should be selected?
- Build a two-peer MCLAG core
- Use a second-tier MCLAG pair
- Keep MCLAG peer hardware and software aligned
- Design a three-tier FortiLink stack within supported topologies
Explanation
Correct Answer
A:The deciding detail is that two peer FortiSwitch units present an aggregated logical attachment to dual-homed devices. This distinction is material to the factory, where the stated goal is to maintain data forwarding when one distribution switch stops responding.
Incorrect Answers
B:Compared with the requested “Build a two-peer MCLAG core” at the factory, this would preserve redundant distribution to switches deeper in a hierarchical access design instead: a lower tier MCLAG peer group connects with upper-tier switching through approved inter-switch arrangements. At the factory, the operational proof would instead be to verify both peer states and the dual-homed trunk membership in the MCLAG monitor, whereas “Use a second-tier MCLAG pair” is validated by a different test: inspect both tier topologies and the cross-tier trunk state during peer-failure testing.
C:For the factory, “Keep MCLAG peer hardware and software aligned” is a different type of control from “Build a two-peer MCLAG core”: Fortinet recommends the same peer model and software version for a supported MCLAG design. Unlike the requested feature, that setting addresses the need to avoid unsupported mismatches in a redundant switch pair, not the objective to maintain data forwarding when one distribution switch stops responding.
D:Compared with the requested “Build a two-peer MCLAG core” at the factory, this would provide hierarchical aggregation, distribution and access while retaining centralized discovery instead: multiple managed tiers require correctly placed ISLs and MCLAGs where redundancy is needed. At the factory, the operational proof would instead be to verify both peer states and the dual-homed trunk membership in the MCLAG monitor, whereas “Design a three-tier FortiLink stack within supported topologies” is validated by a different test: inspect the complete three-tier FortiSwitch topology and unauthorized downstream devices.
Question 88
The operator has decided to build a two-peer MCLAG core on two distribution switches at the distribution floor. Which operational behavior is the most reasonable expectation of that specific feature?
- Two peer FortiSwitch units present an aggregated logical attachment to dual-homed devices
- A supported HA/FortiLink wiring design provides connectivity to the FortiGate cluster rather than a single appliance
- An ISL carries the FortiLink control reachability across the switch chain
- LACP identifies and maintains logical members; independent ports are not a substitute for a bundled attachment
Explanation
Correct Answer
A:The relevant mechanism is: the configured operation is meant to maintain data forwarding when one distribution switch stops responding. The most relevant validation is to verify both peer states and the dual-homed trunk membership in the MCLAG monitor for the equipment at the distribution floor.
Incorrect Answers
B:That behavior applies when engineers “Connect FortiGate HA to a FortiLink stack”; the different operation “Build a two-peer MCLAG core” is intended to maintain data forwarding when one distribution switch stops responding. That different feature is verified by test an HA failover and monitor FortiSwitch authorization and control-plane reachability; for “Build a two-peer MCLAG core” on two distribution switches, the relevant evidence is to verify both peer states and the dual-homed trunk membership in the MCLAG monitor.
C:That behavior applies when engineers “Create a switch inter-switch link for FortiLink discovery”; the different operation “Build a two-peer MCLAG core” is intended to maintain data forwarding when one distribution switch stops responding. That different feature is verified by examine ISL status and whether the expected descendant switch appears in discovery; for “Build a two-peer MCLAG core” on two distribution switches, the relevant evidence is to verify both peer states and the dual-homed trunk membership in the MCLAG monitor.
D:This outcome would be relevant to “Use an active LACP trunk for a dual-homed attachment” at the distribution floor, not the task “Build a two-peer MCLAG core”; the other task is to negotiate port bundling with an access device attached to MCLAG peers. The action “Build a two-peer MCLAG core” targets a different result: two peer FortiSwitch units present an aggregated logical attachment to dual-homed devices; the proposed alternative would instead be checked by check LACP actor/partner state on every participating interface.
Question 89
A technician says “Build a two-peer MCLAG core” has solved the issue at the media studio. Which diagnostic step would substantiate that claim?
- Inspect the access switch LACP partner identity and the MCLAG trunk operational state
- Verify both first-tier peers are represented and their shared trunk is synchronized
- Inspect MCLAG-STP settings and bridge information on both peers
- Verify both peer states and the dual-homed trunk membership in the MCLAG monitor
- Inspect the topology tree and confirm downstream serial numbers appear beneath the uplink switch
Explanation
Correct Answer
D:This approach fits because two peer FortiSwitch units present an aggregated logical attachment to dual-homed devices. Directly measuring that result demonstrates whether the step to maintain data forwarding when one distribution switch stops responding succeeded on a staging FortiSwitch.
Incorrect Answers
A:The proposed check concerns “Dual-home an access switch with LACP to MCLAG peers” rather than “Build a two-peer MCLAG core”: an MCLAG presents the pair as a logical LACP partner for the access switch. For “Build a two-peer MCLAG core” on a staging FortiSwitch, a better test would be to verify both peer states and the dual-homed trunk membership in the MCLAG monitor, which targets maintain data forwarding when one distribution switch stops responding rather than the alternative diagnostic “Dual-home an access switch with LACP to MCLAG peers”.
B:The proposed check concerns “Use a first-tier MCLAG peer group” rather than “Build a two-peer MCLAG core”: the first pair presents a resilient attachment upstream while serving one or more downstream switches. For “Build a two-peer MCLAG core” on a staging FortiSwitch, a better test would be to verify both peer states and the dual-homed trunk membership in the MCLAG monitor, which targets maintain data forwarding when one distribution switch stops responding rather than the alternative diagnostic “Use a first-tier MCLAG peer group”.
C:This check is suited to “Enable STP-aware MCLAG behavior where required” when trying to keep bridge-loop protection consistent when LAGs span peer switches, not to verify “Build a two-peer MCLAG core” at the media studio. Checking “Build a two-peer MCLAG core” at the media studio requires evidence of its own mechanism: two peer FortiSwitch units present an aggregated logical attachment to dual-homed devices; that is not the outcome measured by “Enable STP-aware MCLAG behavior where required”.
E:This check is suited to “Form a FortiLink-managed switch cascade” when trying to manage several downstream FortiSwitch units through one upstream connected device, not to verify “Build a two-peer MCLAG core” at the media studio. Checking “Build a two-peer MCLAG core” at the media studio requires evidence of its own mechanism: two peer FortiSwitch units present an aggregated logical attachment to dual-homed devices; that is not the outcome measured by “Form a FortiLink-managed switch cascade”.
Question 90
On a carefully segmented Layer 2 network in the retail site, the next task is to avoid losing the peer relationship when one cross-connect fails. What is the appropriate configuration decision?
- Establish redundant interchassis links for MCLAG
- Build a two-peer MCLAG core
- Keep MCLAG peer hardware and software aligned
- Create a switch inter-switch link for FortiLink discovery
Explanation
Correct Answer
A:The critical distinction is that the interchassis link communicates peer state; at least two links are recommended for ICL resilience. The operator can test this claim by the specific check: check the ICL member status on both switches and verify a remaining path after a member fails.
Incorrect Answers
B:Compared with the requested “Establish redundant interchassis links for MCLAG” at the retail site, this would maintain data forwarding when one distribution switch stops responding instead: two peer FortiSwitch units present an aggregated logical attachment to dual-homed devices. At the retail site, the operational proof would instead be to check the ICL member status on both switches and verify a remaining path after a member fails, whereas “Build a two-peer MCLAG core” is validated by a different test: verify both peer states and the dual-homed trunk membership in the MCLAG monitor.
C:Compared with the requested “Establish redundant interchassis links for MCLAG” at the retail site, this would avoid unsupported mismatches in a redundant switch pair instead: Fortinet recommends the same peer model and software version for a supported MCLAG design. At the retail site, the operational proof would instead be to check the ICL member status on both switches and verify a remaining path after a member fails, whereas “Keep MCLAG peer hardware and software aligned” is validated by a different test: compare model IDs and installed firmware versions before enabling the peer group.
D:For the retail site, “Create a switch inter-switch link for FortiLink discovery” is a different type of control from “Establish redundant interchassis links for MCLAG”: an ISL carries the FortiLink control reachability across the switch chain. Unlike the requested feature, that setting addresses the need to allow managed descendants to be discovered beyond the directly connected switch, not the objective to avoid losing the peer relationship when one cross-connect fails.