Question 230
An auditor wants operational evidence for the switch action “Set supported speed and duplex consistently” at the retail site. Which check is relevant?
- Remove members in a test and observe when the logical trunk is considered operational
- Review recognized module identity, optical power and relevant port error counters
- Inspect member utilization with multiple flows and verify the configured hash fields
- Check negotiated link speed, duplex and error counters at both ends
Explanation
Correct Answer
D:For the stated requirement, both connected endpoints must agree on operational link characteristics supported by their hardware. Directly measuring that result demonstrates whether the step to restore a physical link with incompatible manual interface negotiation succeeded on an access switch in routine maintenance.
Incorrect Answers
A:The proposed check concerns “Confirm minimum LAG members for service” rather than “Set supported speed and duplex consistently”: the aggregate minimum-member condition constrains availability as members fail. For “Set supported speed and duplex consistently” on an access switch in routine maintenance, a better test would be to check negotiated link speed, duplex and error counters at both ends, which targets restore a physical link with incompatible manual interface negotiation rather than the alternative diagnostic “Confirm minimum LAG members for service”.
B:This check is suited to “Inspect transceiver DOM and module information” when trying to diagnose an optical link that fails intermittently despite correct VLAN settings, not to verify “Set supported speed and duplex consistently” at the retail site. Checking “Set supported speed and duplex consistently” at the retail site requires evidence of its own mechanism: both connected endpoints must agree on operational link characteristics supported by their hardware; that is not the outcome measured by “Inspect transceiver DOM and module information”.
C:This check is suited to “Select appropriate LACP load-balancing criteria” when trying to spread different traffic flows across the members of an existing trunk, not to verify “Set supported speed and duplex consistently” at the retail site. Checking “Set supported speed and duplex consistently” at the retail site requires evidence of its own mechanism: both connected endpoints must agree on operational link characteristics supported by their hardware; that is not the outcome measured by “Select appropriate LACP load-balancing criteria”.
Question 231
A deployment review at the airport office identifies this objective: limit disruption caused by a port repeatedly transitioning up and down. Which FortiSwitch operation should be selected?
- Split a supported high-speed physical port into subports
- Enable flap guard on an unstable interface
- Constrain PoE to available power capacity
- Use an auto-ISL trunk where supported
Explanation
Correct Answer
B:The deciding detail is that flap guard monitors link-state changes and can place an unstable port into a protective state. This distinction is material to the airport office, where the stated goal is to limit disruption caused by a port repeatedly transitioning up and down.
Incorrect Answers
A:Compared with the requested “Enable flap guard on an unstable interface” at the airport office, this would create several lower-rate interfaces from a supported switch port instead: split-port phy-mode changes how the underlying physical lanes are exposed as separate interfaces. At the airport office, the operational proof would instead be to inspect flap events and the interface's automatic disable or recovery status, whereas “Split a supported high-speed physical port into subports” is validated by a different test: check the port's supported phy-mode choices and resulting interface inventory.
C:For the airport office, “Constrain PoE to available power capacity” is a different type of control from “Enable flap guard on an unstable interface”: power delivery is constrained by per-port hardware capability and the switch's aggregate PoE budget. Unlike the requested feature, that setting addresses the need to prevent a new powered endpoint from exceeding the switch power budget, not the objective to limit disruption caused by a port repeatedly transitioning up and down.
D:Compared with the requested “Enable flap guard on an unstable interface” at the airport office, this would automatically maintain eligible links between managed FortiSwitch units instead: auto-inter-switch-link mechanisms simplify eligible uplink bundling in supported FortiLink designs. At the airport office, the operational proof would instead be to inspect flap events and the interface's automatic disable or recovery status, whereas “Use an auto-ISL trunk where supported” is validated by a different test: inspect discovered ISL membership and active trunk status.
Question 232
A colleague asks about the effect of “Enable flap guard on an unstable interface” on a recently upgraded FortiSwitch. Which behavior best characterizes that feature?
- Power delivery is constrained by per-port hardware capability and the switch's aggregate PoE budget
- Flap guard monitors link-state changes and can place an unstable port into a protective state
- Optic inventory and diagnostics expose module type and supported optical measurements when the transceiver provides them
- Auto-inter-switch-link mechanisms simplify eligible uplink bundling in supported FortiLink designs
- Split-port phy-mode changes how the underlying physical lanes are exposed as separate interfaces
Explanation
Correct Answer
B:The relevant mechanism is: the configured operation is meant to limit disruption caused by a port repeatedly transitioning up and down. The most relevant validation is to inspect flap events and the interface's automatic disable or recovery status for the equipment at the operations center.
Incorrect Answers
A:That behavior applies when engineers “Constrain PoE to available power capacity”; the different operation “Enable flap guard on an unstable interface” is intended to limit disruption caused by a port repeatedly transitioning up and down. That different feature is verified by compare the connected device's requested class with free PoE budget and port allocation; for “Enable flap guard on an unstable interface” on a recently upgraded FortiSwitch, the relevant evidence is to inspect flap events and the interface's automatic disable or recovery status.
C:That behavior applies when engineers “Inspect transceiver DOM and module information”; the different operation “Enable flap guard on an unstable interface” is intended to limit disruption caused by a port repeatedly transitioning up and down. That different feature is verified by review recognized module identity, optical power and relevant port error counters; for “Enable flap guard on an unstable interface” on a recently upgraded FortiSwitch, the relevant evidence is to inspect flap events and the interface's automatic disable or recovery status.
D:This outcome would be relevant to “Use an auto-ISL trunk where supported” at the operations center, not the task “Enable flap guard on an unstable interface”; the other task is to automatically maintain eligible links between managed FortiSwitch units. The action “Enable flap guard on an unstable interface” targets a different result: flap guard monitors link-state changes and can place an unstable port into a protective state; the proposed alternative would instead be checked by inspect discovered ISL membership and active trunk status.
E:That behavior applies when engineers “Split a supported high-speed physical port into subports”; the different operation “Enable flap guard on an unstable interface” is intended to limit disruption caused by a port repeatedly transitioning up and down. That different feature is verified by check the port's supported phy-mode choices and resulting interface inventory; for “Enable flap guard on an unstable interface” on a recently upgraded FortiSwitch, the relevant evidence is to inspect flap events and the interface's automatic disable or recovery status.
Question 233
After implementing “Enable flap guard on an unstable interface,” the site engineer needs to assess its actual effect on a FortiLink-managed access switch. Which test is the best match?
- Compare the connected device's requested class with free PoE budget and port allocation
- Inspect discovered ISL membership and active trunk status
- Inspect flap events and the interface's automatic disable or recovery status
- Check the port's supported phy-mode choices and resulting interface inventory
Explanation
Correct Answer
C:This approach fits because flap guard monitors link-state changes and can place an unstable port into a protective state. Directly measuring that result demonstrates whether the step to limit disruption caused by a port repeatedly transitioning up and down succeeded on a FortiLink-managed access switch.
Incorrect Answers
A:This check is suited to “Constrain PoE to available power capacity” when trying to prevent a new powered endpoint from exceeding the switch power budget, not to verify “Enable flap guard on an unstable interface” at the warehouse. Checking “Enable flap guard on an unstable interface” at the warehouse requires evidence of its own mechanism: flap guard monitors link-state changes and can place an unstable port into a protective state; that is not the outcome measured by “Constrain PoE to available power capacity”.
B:The proposed check concerns “Use an auto-ISL trunk where supported” rather than “Enable flap guard on an unstable interface”: auto-inter-switch-link mechanisms simplify eligible uplink bundling in supported FortiLink designs. For “Enable flap guard on an unstable interface” on a FortiLink-managed access switch, a better test would be to inspect flap events and the interface's automatic disable or recovery status, which targets limit disruption caused by a port repeatedly transitioning up and down rather than the alternative diagnostic “Use an auto-ISL trunk where supported”.
D:This check is suited to “Split a supported high-speed physical port into subports” when trying to create several lower-rate interfaces from a supported switch port, not to verify “Enable flap guard on an unstable interface” at the warehouse. Checking “Enable flap guard on an unstable interface” at the warehouse requires evidence of its own mechanism: flap guard monitors link-state changes and can place an unstable port into a protective state; that is not the outcome measured by “Split a supported high-speed physical port into subports”.
Question 234
On a switch linked to a FortiGate running FortiOS 7.6 in the remote depot, the next task is to prevent a new powered endpoint from exceeding the switch power budget. What is the appropriate configuration decision?
- Select appropriate LACP load-balancing criteria
- Constrain PoE to available power capacity
- Confirm minimum LAG members for service
- Set supported speed and duplex consistently
Explanation
Correct Answer
B:The critical distinction is that power delivery is constrained by per-port hardware capability and the switch's aggregate PoE budget. The operator can test this claim by the specific check: compare the connected device's requested class with free PoE budget and port allocation.
Incorrect Answers
A:Compared with the requested “Constrain PoE to available power capacity” at the remote depot, this would spread different traffic flows across the members of an existing trunk instead: trunk hashing chooses a member based on header fields and typically keeps each flow on one link. At the remote depot, the operational proof would instead be to compare the connected device's requested class with free PoE budget and port allocation, whereas “Select appropriate LACP load-balancing criteria” is validated by a different test: inspect member utilization with multiple flows and verify the configured hash fields.
C:Compared with the requested “Constrain PoE to available power capacity” at the remote depot, this would require sufficient healthy physical links before allowing an aggregate to remain usable instead: the aggregate minimum-member condition constrains availability as members fail. At the remote depot, the operational proof would instead be to compare the connected device's requested class with free PoE budget and port allocation, whereas “Confirm minimum LAG members for service” is validated by a different test: remove members in a test and observe when the logical trunk is considered operational.
D:For the remote depot, “Set supported speed and duplex consistently” is a different type of control from “Constrain PoE to available power capacity”: both connected endpoints must agree on operational link characteristics supported by their hardware. Unlike the requested feature, that setting addresses the need to restore a physical link with incompatible manual interface negotiation, not the objective to prevent a new powered endpoint from exceeding the switch power budget.
Question 235
When engineers constrain PoE to available power capacity at the branch office, which forwarding, security, management or diagnostic outcome follows from that action?
- Both connected endpoints must agree on operational link characteristics supported by their hardware
- Power delivery is constrained by per-port hardware capability and the switch's aggregate PoE budget
- Trunk hashing chooses a member based on header fields and typically keeps each flow on one link
- The aggregate minimum-member condition constrains availability as members fail
Explanation
Correct Answer
B:That setting is appropriate here because the configured operation is meant to prevent a new powered endpoint from exceeding the switch power budget. The most relevant validation is to compare the connected device's requested class with free PoE budget and port allocation for the equipment at the branch office.
Incorrect Answers
A:That behavior applies when engineers “Set supported speed and duplex consistently”; the different operation “Constrain PoE to available power capacity” is intended to prevent a new powered endpoint from exceeding the switch power budget. That different feature is verified by check negotiated link speed, duplex and error counters at both ends; for “Constrain PoE to available power capacity” on a central switching stack, the relevant evidence is to compare the connected device's requested class with free PoE budget and port allocation.
C:This outcome would be relevant to “Select appropriate LACP load-balancing criteria” at the branch office, not the task “Constrain PoE to available power capacity”; the other task is to spread different traffic flows across the members of an existing trunk. The action “Constrain PoE to available power capacity” targets a different result: power delivery is constrained by per-port hardware capability and the switch's aggregate PoE budget; the proposed alternative would instead be checked by inspect member utilization with multiple flows and verify the configured hash fields.
D:That behavior applies when engineers “Confirm minimum LAG members for service”; the different operation “Constrain PoE to available power capacity” is intended to prevent a new powered endpoint from exceeding the switch power budget. That different feature is verified by remove members in a test and observe when the logical trunk is considered operational; for “Constrain PoE to available power capacity” on a central switching stack, the relevant evidence is to compare the connected device's requested class with free PoE budget and port allocation.
Question 236
At the factory, a dashboard shows ordinary link-up state, but the team also needs proof for “Constrain PoE to available power capacity.” Which targeted check should be used?
- Check the port's supported phy-mode choices and resulting interface inventory
- Check negotiated link speed, duplex and error counters at both ends
- Inspect member utilization with multiple flows and verify the configured hash fields
- Remove members in a test and observe when the logical trunk is considered operational
- Compare the connected device's requested class with free PoE budget and port allocation
Explanation
Correct Answer
E:This is the precise control because power delivery is constrained by per-port hardware capability and the switch's aggregate PoE budget. Directly measuring that result demonstrates whether the step to prevent a new powered endpoint from exceeding the switch power budget succeeded on a FortiSwitch connected to the security edge.
Incorrect Answers
A:The proposed check concerns “Split a supported high-speed physical port into subports” rather than “Constrain PoE to available power capacity”: split-port phy-mode changes how the underlying physical lanes are exposed as separate interfaces. For “Constrain PoE to available power capacity” on a FortiSwitch connected to the security edge, a better test would be to compare the connected device's requested class with free PoE budget and port allocation, which targets prevent a new powered endpoint from exceeding the switch power budget rather than the alternative diagnostic “Split a supported high-speed physical port into subports”.
B:This check is suited to “Set supported speed and duplex consistently” when trying to restore a physical link with incompatible manual interface negotiation, not to verify “Constrain PoE to available power capacity” at the factory. Checking “Constrain PoE to available power capacity” at the factory requires evidence of its own mechanism: power delivery is constrained by per-port hardware capability and the switch's aggregate PoE budget; that is not the outcome measured by “Set supported speed and duplex consistently”.
C:The proposed check concerns “Select appropriate LACP load-balancing criteria” rather than “Constrain PoE to available power capacity”: trunk hashing chooses a member based on header fields and typically keeps each flow on one link. For “Constrain PoE to available power capacity” on a FortiSwitch connected to the security edge, a better test would be to compare the connected device's requested class with free PoE budget and port allocation, which targets prevent a new powered endpoint from exceeding the switch power budget rather than the alternative diagnostic “Select appropriate LACP load-balancing criteria”.
D:This check is suited to “Confirm minimum LAG members for service” when trying to require sufficient healthy physical links before allowing an aggregate to remain usable, not to verify “Constrain PoE to available power capacity” at the factory. Checking “Constrain PoE to available power capacity” at the factory requires evidence of its own mechanism: power delivery is constrained by per-port hardware capability and the switch's aggregate PoE budget; that is not the outcome measured by “Confirm minimum LAG members for service”.
Question 237
At the distribution floor, a technician is choosing between several switching features to spread different traffic flows across the members of an existing trunk. Which one belongs in the implementation plan?
- Use an auto-ISL trunk where supported
- Inspect transceiver DOM and module information
- Select appropriate LACP load-balancing criteria
- Enable flap guard on an unstable interface
Explanation
Correct Answer
C:The implementation works because trunk hashing chooses a member based on header fields and typically keeps each flow on one link. This distinction is material to the distribution floor, where the stated goal is to spread different traffic flows across the members of an existing trunk.
Incorrect Answers
A:Compared with the requested “Select appropriate LACP load-balancing criteria” at the distribution floor, this would automatically maintain eligible links between managed FortiSwitch units instead: auto-inter-switch-link mechanisms simplify eligible uplink bundling in supported FortiLink designs. At the distribution floor, the operational proof would instead be to inspect member utilization with multiple flows and verify the configured hash fields, whereas “Use an auto-ISL trunk where supported” is validated by a different test: inspect discovered ISL membership and active trunk status.
B:For the distribution floor, “Inspect transceiver DOM and module information” is a different type of control from “Select appropriate LACP load-balancing criteria”: optic inventory and diagnostics expose module type and supported optical measurements when the transceiver provides them. Unlike the requested feature, that setting addresses the need to diagnose an optical link that fails intermittently despite correct VLAN settings, not the objective to spread different traffic flows across the members of an existing trunk.
D:Compared with the requested “Select appropriate LACP load-balancing criteria” at the distribution floor, this would limit disruption caused by a port repeatedly transitioning up and down instead: flap guard monitors link-state changes and can place an unstable port into a protective state. At the distribution floor, the operational proof would instead be to inspect member utilization with multiple flows and verify the configured hash fields, whereas “Enable flap guard on an unstable interface” is validated by a different test: inspect flap events and the interface's automatic disable or recovery status.
Question 238
A colleague asks about the effect of “Select appropriate LACP load-balancing criteria” on a managed campus switch. Which behavior best characterizes that feature?
- Trunk hashing chooses a member based on header fields and typically keeps each flow on one link
- Flap guard monitors link-state changes and can place an unstable port into a protective state
- Auto-inter-switch-link mechanisms simplify eligible uplink bundling in supported FortiLink designs
- Optic inventory and diagnostics expose module type and supported optical measurements when the transceiver provides them
Explanation
Correct Answer
A:Given the described goal, the configured operation is meant to spread different traffic flows across the members of an existing trunk. The most relevant validation is to inspect member utilization with multiple flows and verify the configured hash fields for the equipment at the media studio.
Incorrect Answers
B:This outcome would be relevant to “Enable flap guard on an unstable interface” at the media studio, not the task “Select appropriate LACP load-balancing criteria”; the other task is to limit disruption caused by a port repeatedly transitioning up and down. The action “Select appropriate LACP load-balancing criteria” targets a different result: trunk hashing chooses a member based on header fields and typically keeps each flow on one link; the proposed alternative would instead be checked by inspect flap events and the interface's automatic disable or recovery status.
C:That behavior applies when engineers “Use an auto-ISL trunk where supported”; the different operation “Select appropriate LACP load-balancing criteria” is intended to spread different traffic flows across the members of an existing trunk. That different feature is verified by inspect discovered ISL membership and active trunk status; for “Select appropriate LACP load-balancing criteria” on a managed campus switch, the relevant evidence is to inspect member utilization with multiple flows and verify the configured hash fields.
D:That behavior applies when engineers “Inspect transceiver DOM and module information”; the different operation “Select appropriate LACP load-balancing criteria” is intended to spread different traffic flows across the members of an existing trunk. That different feature is verified by review recognized module identity, optical power and relevant port error counters; for “Select appropriate LACP load-balancing criteria” on a managed campus switch, the relevant evidence is to inspect member utilization with multiple flows and verify the configured hash fields.
Question 239
After the team configures “Select appropriate LACP load-balancing criteria” on a recently upgraded FortiSwitch, which TWO claims about the configuration are valid? (Choose TWO.)
- Optic inventory and diagnostics expose module type and supported optical measurements when the transceiver provides them
- Inspect member utilization with multiple flows and verify the configured hash fields
- Auto-inter-switch-link mechanisms simplify eligible uplink bundling in supported FortiLink designs
- Flap guard monitors link-state changes and can place an unstable port into a protective state
- Trunk hashing chooses a member based on header fields and typically keeps each flow on one link
Explanation
Correct Answers
B:The stated check directly tests whether the intended function is active at the retail site. It provides evidence about “Select appropriate LACP load-balancing criteria” beyond ordinary link-up state on a recently upgraded FortiSwitch.
E:The switch behavior that matters is: the described mechanism corresponds to the operation that administrators use to spread different traffic flows across the members of an existing trunk. The result should be observable on a recently upgraded FortiSwitch.
Incorrect Answers
A:That characteristic reflects “Inspect transceiver DOM and module information” rather than “Select appropriate LACP load-balancing criteria” at the retail site. Its actual role is to diagnose an optical link that fails intermittently despite correct VLAN settings, a different configuration need.
C:That characteristic reflects “Use an auto-ISL trunk where supported” rather than “Select appropriate LACP load-balancing criteria” at the retail site. Its actual role is to automatically maintain eligible links between managed FortiSwitch units, a different configuration need.
D:That characteristic reflects “Enable flap guard on an unstable interface” rather than “Select appropriate LACP load-balancing criteria” at the retail site. Its actual role is to limit disruption caused by a port repeatedly transitioning up and down, a different configuration need.
Question 240
The accepted design for the airport office requires the ability to automatically maintain eligible links between managed FortiSwitch units. Which switch feature is the closest fit?
- Enable flap guard on an unstable interface
- Select appropriate LACP load-balancing criteria
- Set supported speed and duplex consistently
- Split a supported high-speed physical port into subports
- Use an auto-ISL trunk where supported
Explanation
Correct Answer
E:At this network boundary, auto-inter-switch-link mechanisms simplify eligible uplink bundling in supported FortiLink designs. The operator can test this claim by the specific check: inspect discovered ISL membership and active trunk status.
Incorrect Answers
A:Compared with the requested “Use an auto-ISL trunk where supported” at the airport office, this would limit disruption caused by a port repeatedly transitioning up and down instead: flap guard monitors link-state changes and can place an unstable port into a protective state. At the airport office, the operational proof would instead be to inspect discovered ISL membership and active trunk status, whereas “Enable flap guard on an unstable interface” is validated by a different test: inspect flap events and the interface's automatic disable or recovery status.
B:For the airport office, “Select appropriate LACP load-balancing criteria” is a different type of control from “Use an auto-ISL trunk where supported”: trunk hashing chooses a member based on header fields and typically keeps each flow on one link. Unlike the requested feature, that setting addresses the need to spread different traffic flows across the members of an existing trunk, not the objective to automatically maintain eligible links between managed FortiSwitch units.
C:Compared with the requested “Use an auto-ISL trunk where supported” at the airport office, this would restore a physical link with incompatible manual interface negotiation instead: both connected endpoints must agree on operational link characteristics supported by their hardware. At the airport office, the operational proof would instead be to inspect discovered ISL membership and active trunk status, whereas “Set supported speed and duplex consistently” is validated by a different test: check negotiated link speed, duplex and error counters at both ends.
D:Compared with the requested “Use an auto-ISL trunk where supported” at the airport office, this would create several lower-rate interfaces from a supported switch port instead: split-port phy-mode changes how the underlying physical lanes are exposed as separate interfaces. At the airport office, the operational proof would instead be to inspect discovered ISL membership and active trunk status, whereas “Split a supported high-speed physical port into subports” is validated by a different test: check the port's supported phy-mode choices and resulting interface inventory.