Question 650
When engineers choose egress mirroring for leaving frames at the retail site, which forwarding, security, management or diagnostic outcome follows from that action?
- A CLI sniffer can display or collect matching packets without installing a permanent forwarding rule
- Ingress mirror direction copies traffic entering the selected interface
- A capture profile defines the observed interface and packet selection before capture starts
- Egress mirror direction observes packets chosen for output after relevant forwarding steps
- RSPAN carries mirrored Ethernet traffic over an appropriate remote mirror VLAN
Explanation
Correct Answer
D:For the stated requirement, the configured operation is meant to confirm which frames the switch actually transmits toward a downstream device. The most relevant validation is to compare the analyzer's egress trace with destination port counters for the equipment at the retail site.
Incorrect Answers
A:That behavior applies when engineers “Run an appropriate FortiSwitch sniffer command”; the different operation “Choose egress mirroring for leaving frames” is intended to confirm which frames the switch actually transmits toward a downstream device. That different feature is verified by repeat the transaction and confirm the expected frame types appear in sniffer output; for “Choose egress mirroring for leaving frames” on a staging FortiSwitch, the relevant evidence is to compare the analyzer's egress trace with destination port counters.
B:This outcome would be relevant to “Choose ingress mirroring for arriving frames” at the retail site, not the task “Choose egress mirroring for leaving frames”; the other task is to diagnose whether a switch receives packets before its forwarding decisions. The action “Choose egress mirroring for leaving frames” targets a different result: egress mirror direction observes packets chosen for output after relevant forwarding steps; the proposed alternative would instead be checked by verify the source packet is visible on ingress even when later filtering prevents forwarding.
C:That behavior applies when engineers “Create a packet capture profile with a filter”; the different operation “Choose egress mirroring for leaving frames” is intended to confirm which frames the switch actually transmits toward a downstream device. That different feature is verified by review captured headers and verify the chosen filter matches the targeted flow; for “Choose egress mirroring for leaving frames” on a staging FortiSwitch, the relevant evidence is to compare the analyzer's egress trace with destination port counters.
E:That behavior applies when engineers “Configure an RSPAN remote mirror”; the different operation “Choose egress mirroring for leaving frames” is intended to confirm which frames the switch actually transmits toward a downstream device. That different feature is verified by inspect RSPAN VLAN membership on intermediate trunks and packets arriving at the remote analyzer; for “Choose egress mirroring for leaving frames” on a staging FortiSwitch, the relevant evidence is to compare the analyzer's egress trace with destination port counters.
Question 651
A feature acceptance test on a newly commissioned floor switch concerns “Choose egress mirroring for leaving frames.” What should be checked to establish its expected operation?
- Compare the analyzer's egress trace with destination port counters
- Inspect RSPAN VLAN membership on intermediate trunks and packets arriving at the remote analyzer
- Verify the source packet is visible on ingress even when later filtering prevents forwarding
- Review captured headers and verify the chosen filter matches the targeted flow
Explanation
Correct Answer
A:The deciding detail is that egress mirror direction observes packets chosen for output after relevant forwarding steps. Directly measuring that result demonstrates whether the step to confirm which frames the switch actually transmits toward a downstream device succeeded on a newly commissioned floor switch.
Incorrect Answers
B:This check is suited to “Configure an RSPAN remote mirror” when trying to monitor source traffic from another switch across a VLAN transport path, not to verify “Choose egress mirroring for leaving frames” at the airport office. Checking “Choose egress mirroring for leaving frames” at the airport office requires evidence of its own mechanism: egress mirror direction observes packets chosen for output after relevant forwarding steps; that is not the outcome measured by “Configure an RSPAN remote mirror”.
C:The proposed check concerns “Choose ingress mirroring for arriving frames” rather than “Choose egress mirroring for leaving frames”: ingress mirror direction copies traffic entering the selected interface. For “Choose egress mirroring for leaving frames” on a newly commissioned floor switch, a better test would be to compare the analyzer's egress trace with destination port counters, which targets confirm which frames the switch actually transmits toward a downstream device rather than the alternative diagnostic “Choose ingress mirroring for arriving frames”.
D:This check is suited to “Create a packet capture profile with a filter” when trying to limit local FortiSwitch capture to packets relevant to a particular troubleshooting investigation, not to verify “Choose egress mirroring for leaving frames” at the airport office. Checking “Choose egress mirroring for leaving frames” at the airport office requires evidence of its own mechanism: egress mirror direction observes packets chosen for output after relevant forwarding steps; that is not the outcome measured by “Create a packet capture profile with a filter”.
Question 652
During a change window in the operations center, engineers are asked to avoid losing captures on a busy switch with limited capture resources. What should they configure rather than using a feature for an adjacent purpose?
- Create a packet capture profile with a filter
- Choose ingress mirroring for arriving frames
- Configure an RSPAN remote mirror
- Check packet capture storage and profile capacity
Explanation
Correct Answer
D:The relevant mechanism is: switch model determines capture-profile capacity and RAM-disk space for retained packets. The operator can test this claim by the specific check: inspect capture file size, platform allocation and whether the profile can still record.
Incorrect Answers
A:Compared with the requested “Check packet capture storage and profile capacity” at the operations center, this would limit local FortiSwitch capture to packets relevant to a particular troubleshooting investigation instead: a capture profile defines the observed interface and packet selection before capture starts. At the operations center, the operational proof would instead be to inspect capture file size, platform allocation and whether the profile can still record, whereas “Create a packet capture profile with a filter” is validated by a different test: review captured headers and verify the chosen filter matches the targeted flow.
B:Compared with the requested “Check packet capture storage and profile capacity” at the operations center, this would diagnose whether a switch receives packets before its forwarding decisions instead: ingress mirror direction copies traffic entering the selected interface. At the operations center, the operational proof would instead be to inspect capture file size, platform allocation and whether the profile can still record, whereas “Choose ingress mirroring for arriving frames” is validated by a different test: verify the source packet is visible on ingress even when later filtering prevents forwarding.
C:For the operations center, “Configure an RSPAN remote mirror” is a different type of control from “Check packet capture storage and profile capacity”: RSPAN carries mirrored Ethernet traffic over an appropriate remote mirror VLAN. Unlike the requested feature, that setting addresses the need to monitor source traffic from another switch across a VLAN transport path, not the objective to avoid losing captures on a busy switch with limited capture resources.
Question 653
A colleague asks about the effect of “Check packet capture storage and profile capacity” on a switch used by multiple office teams. Which behavior best characterizes that feature?
- RSPAN carries mirrored Ethernet traffic over an appropriate remote mirror VLAN
- Switch model determines capture-profile capacity and RAM-disk space for retained packets
- Ingress mirror direction copies traffic entering the selected interface
- A capture profile defines the observed interface and packet selection before capture starts
Explanation
Correct Answer
B:This approach fits because the configured operation is meant to avoid losing captures on a busy switch with limited capture resources. The most relevant validation is to inspect capture file size, platform allocation and whether the profile can still record for the equipment at the warehouse.
Incorrect Answers
A:That behavior applies when engineers “Configure an RSPAN remote mirror”; the different operation “Check packet capture storage and profile capacity” is intended to avoid losing captures on a busy switch with limited capture resources. That different feature is verified by inspect RSPAN VLAN membership on intermediate trunks and packets arriving at the remote analyzer; for “Check packet capture storage and profile capacity” on a switch used by multiple office teams, the relevant evidence is to inspect capture file size, platform allocation and whether the profile can still record.
C:This outcome would be relevant to “Choose ingress mirroring for arriving frames” at the warehouse, not the task “Check packet capture storage and profile capacity”; the other task is to diagnose whether a switch receives packets before its forwarding decisions. The action “Check packet capture storage and profile capacity” targets a different result: switch model determines capture-profile capacity and RAM-disk space for retained packets; the proposed alternative would instead be checked by verify the source packet is visible on ingress even when later filtering prevents forwarding.
D:That behavior applies when engineers “Create a packet capture profile with a filter”; the different operation “Check packet capture storage and profile capacity” is intended to avoid losing captures on a busy switch with limited capture resources. That different feature is verified by review captured headers and verify the chosen filter matches the targeted flow; for “Check packet capture storage and profile capacity” on a switch used by multiple office teams, the relevant evidence is to inspect capture file size, platform allocation and whether the profile can still record.
Question 654
A network architect documents a single goal for a production FortiSwitch fabric: explain why a physically connected new switch does not receive central configuration. Which listed procedure provides that capability?
- Check FortiSwitch discovery and authorization state
- Confirm FortiLink physical and logical interface status
- Check the switch-controller management process
- Inspect topology view for a missing descendant
- Check FortiLink control traffic with a sniffer
Explanation
Correct Answer
A:The critical distinction is that discovery detects the unit; authorization controls whether it becomes a managed device. The operator can test this claim by the specific check: compare detected serials with authorized managed-switch inventory.
Incorrect Answers
B:For the remote depot, “Confirm FortiLink physical and logical interface status” is a different type of control from “Check FortiSwitch discovery and authorization state”: operational link members and FortiLink interface status must be healthy before management can synchronize. Unlike the requested feature, that setting addresses the need to distinguish a dead uplink from a controller configuration problem, not the objective to explain why a physically connected new switch does not receive central configuration.
C:Compared with the requested “Check FortiSwitch discovery and authorization state” at the remote depot, this would investigate a control-plane problem despite working ordinary Ethernet links instead: controller and managed-switch processes operate separately from basic Layer 2 forwarding. At the remote depot, the operational proof would instead be to compare detected serials with authorized managed-switch inventory, whereas “Check the switch-controller management process” is validated by a different test: review controller process health and device management daemon logs.
D:Compared with the requested “Check FortiSwitch discovery and authorization state” at the remote depot, this would locate the ISL segment that interrupts downstream FortiSwitch discovery instead: the stack topology identifies parent and child switch relationships and intermediate uplinks. At the remote depot, the operational proof would instead be to compare detected serials with authorized managed-switch inventory, whereas “Inspect topology view for a missing descendant” is validated by a different test: trace the missing switch's upstream path and each intervening ISL state.
E:Compared with the requested “Check FortiSwitch discovery and authorization state” at the remote depot, this would distinguish absent discovery packets from failed authorization or policy processing instead: a targeted capture can show whether expected controller/discovery exchanges traverse the selected interface. At the remote depot, the operational proof would instead be to compare detected serials with authorized managed-switch inventory, whereas “Check FortiLink control traffic with a sniffer” is validated by a different test: observe control-plane packets at both ends while restarting discovery.
Question 655
A colleague asks about the effect of “Check FortiSwitch discovery and authorization state” on a newly racked distribution unit. Which behavior best characterizes that feature?
- Controller and switch versions and model support affect feature provisioning and synchronization
- Discovery detects the unit; authorization controls whether it becomes a managed device
- The stack topology identifies parent and child switch relationships and intermediate uplinks
- The controller's desired configuration may not have been successfully delivered or accepted
Explanation
Correct Answer
B:That setting is appropriate here because the configured operation is meant to explain why a physically connected new switch does not receive central configuration. The most relevant validation is to compare detected serials with authorized managed-switch inventory for the equipment at the branch office.
Incorrect Answers
A:That behavior applies when engineers “Check firmware compatibility and supported switch model”; the different operation “Check FortiSwitch discovery and authorization state” is intended to explain why a physically connected new switch does not receive central configuration. That different feature is verified by compare exact releases and model against the applicable FortiLink compatibility information; for “Check FortiSwitch discovery and authorization state” on a newly racked distribution unit, the relevant evidence is to compare detected serials with authorized managed-switch inventory.
C:That behavior applies when engineers “Inspect topology view for a missing descendant”; the different operation “Check FortiSwitch discovery and authorization state” is intended to explain why a physically connected new switch does not receive central configuration. That different feature is verified by trace the missing switch's upstream path and each intervening ISL state; for “Check FortiSwitch discovery and authorization state” on a newly racked distribution unit, the relevant evidence is to compare detected serials with authorized managed-switch inventory.
D:This outcome would be relevant to “Inspect FortiSwitch configuration synchronization” at the branch office, not the task “Check FortiSwitch discovery and authorization state”; the other task is to explain why a VLAN edit appears on FortiGate but not on a managed switch. The action “Check FortiSwitch discovery and authorization state” targets a different result: discovery detects the unit; authorization controls whether it becomes a managed device; the proposed alternative would instead be checked by compare synchronization state and intended versus applied port properties.
Question 656
A technician says “Check FortiSwitch discovery and authorization state” has solved the issue at the factory. Which diagnostic step would substantiate that claim?
- Observe control-plane packets at both ends while restarting discovery
- Compare detected serials with authorized managed-switch inventory
- Test management-path connectivity and inspect assigned addresses
- Compare actual switch/controller time and NTP association status
Explanation
Correct Answer
B:This is the precise control because discovery detects the unit; authorization controls whether it becomes a managed device. Directly measuring that result demonstrates whether the step to explain why a physically connected new switch does not receive central configuration succeeded on two distribution switches.
Incorrect Answers
A:This check is suited to “Check FortiLink control traffic with a sniffer” when trying to distinguish absent discovery packets from failed authorization or policy processing, not to verify “Check FortiSwitch discovery and authorization state” at the factory. Checking “Check FortiSwitch discovery and authorization state” at the factory requires evidence of its own mechanism: discovery detects the unit; authorization controls whether it becomes a managed device; that is not the outcome measured by “Check FortiLink control traffic with a sniffer”.
C:The proposed check concerns “Verify FortiLink management address reachability” rather than “Check FortiSwitch discovery and authorization state”: controller communication depends on valid IP settings or the supported Layer 2 FortiLink path. For “Check FortiSwitch discovery and authorization state” on two distribution switches, a better test would be to compare detected serials with authorized managed-switch inventory, which targets explain why a physically connected new switch does not receive central configuration rather than the alternative diagnostic “Verify FortiLink management address reachability”.
D:This check is suited to “Verify NTP and clock consistency” when trying to understand authentication failures or event timestamps that do not align with controller records, not to verify “Check FortiSwitch discovery and authorization state” at the factory. Checking “Check FortiSwitch discovery and authorization state” at the factory requires evidence of its own mechanism: discovery detects the unit; authorization controls whether it becomes a managed device; that is not the outcome measured by “Verify NTP and clock consistency”.
Question 657
The operational requirement for a staging FortiSwitch at the distribution floor is to distinguish a dead uplink from a controller configuration problem. Which FortiSwitch choice directly targets it?
- Check FortiSwitch discovery and authorization state
- Check FortiLink control traffic with a sniffer
- Confirm FortiLink physical and logical interface status
- Check the switch-controller management process
Explanation
Correct Answer
C:The implementation works because operational link members and FortiLink interface status must be healthy before management can synchronize. This distinction is material to the distribution floor, where the stated goal is to distinguish a dead uplink from a controller configuration problem.
Incorrect Answers
A:For the distribution floor, “Check FortiSwitch discovery and authorization state” is a different type of control from “Confirm FortiLink physical and logical interface status”: discovery detects the unit; authorization controls whether it becomes a managed device. Unlike the requested feature, that setting addresses the need to explain why a physically connected new switch does not receive central configuration, not the objective to distinguish a dead uplink from a controller configuration problem.
B:Compared with the requested “Confirm FortiLink physical and logical interface status” at the distribution floor, this would distinguish absent discovery packets from failed authorization or policy processing instead: a targeted capture can show whether expected controller/discovery exchanges traverse the selected interface. At the distribution floor, the operational proof would instead be to inspect FortiGate member links and the corresponding switch-facing ports, whereas “Check FortiLink control traffic with a sniffer” is validated by a different test: observe control-plane packets at both ends while restarting discovery.
D:Compared with the requested “Confirm FortiLink physical and logical interface status” at the distribution floor, this would investigate a control-plane problem despite working ordinary Ethernet links instead: controller and managed-switch processes operate separately from basic Layer 2 forwarding. At the distribution floor, the operational proof would instead be to inspect FortiGate member links and the corresponding switch-facing ports, whereas “Check the switch-controller management process” is validated by a different test: review controller process health and device management daemon logs.
Question 658
When engineers confirm FortiLink physical and logical interface status at the media studio, which forwarding, security, management or diagnostic outcome follows from that action?
- The controller's desired configuration may not have been successfully delivered or accepted
- Controller and switch versions and model support affect feature provisioning and synchronization
- Operational link members and FortiLink interface status must be healthy before management can synchronize
- Clock synchronization is important for time-sensitive authentication and interpreting management logs
- The stack topology identifies parent and child switch relationships and intermediate uplinks
Explanation
Correct Answer
C:Given the described goal, the configured operation is meant to distinguish a dead uplink from a controller configuration problem. The most relevant validation is to inspect FortiGate member links and the corresponding switch-facing ports for the equipment at the media studio.
Incorrect Answers
A:This outcome would be relevant to “Inspect FortiSwitch configuration synchronization” at the media studio, not the task “Confirm FortiLink physical and logical interface status”; the other task is to explain why a VLAN edit appears on FortiGate but not on a managed switch. The action “Confirm FortiLink physical and logical interface status” targets a different result: operational link members and FortiLink interface status must be healthy before management can synchronize; the proposed alternative would instead be checked by compare synchronization state and intended versus applied port properties.
B:That behavior applies when engineers “Check firmware compatibility and supported switch model”; the different operation “Confirm FortiLink physical and logical interface status” is intended to distinguish a dead uplink from a controller configuration problem. That different feature is verified by compare exact releases and model against the applicable FortiLink compatibility information; for “Confirm FortiLink physical and logical interface status” on a carefully segmented Layer 2 network, the relevant evidence is to inspect FortiGate member links and the corresponding switch-facing ports.
D:That behavior applies when engineers “Verify NTP and clock consistency”; the different operation “Confirm FortiLink physical and logical interface status” is intended to distinguish a dead uplink from a controller configuration problem. That different feature is verified by compare actual switch/controller time and NTP association status; for “Confirm FortiLink physical and logical interface status” on a carefully segmented Layer 2 network, the relevant evidence is to inspect FortiGate member links and the corresponding switch-facing ports.
E:That behavior applies when engineers “Inspect topology view for a missing descendant”; the different operation “Confirm FortiLink physical and logical interface status” is intended to distinguish a dead uplink from a controller configuration problem. That different feature is verified by trace the missing switch's upstream path and each intervening ISL state; for “Confirm FortiLink physical and logical interface status” on a carefully segmented Layer 2 network, the relevant evidence is to inspect FortiGate member links and the corresponding switch-facing ports.
Question 659
After implementing “Confirm FortiLink physical and logical interface status,” the site engineer needs to assess its actual effect on a central switching stack. Which test is the best match?
- Inspect FortiGate member links and the corresponding switch-facing ports
- Observe control-plane packets at both ends while restarting discovery
- Test management-path connectivity and inspect assigned addresses
- Compare actual switch/controller time and NTP association status
Explanation
Correct Answer
A:The switch behavior that matters is: operational link members and FortiLink interface status must be healthy before management can synchronize. Directly measuring that result demonstrates whether the step to distinguish a dead uplink from a controller configuration problem succeeded on a central switching stack.
Incorrect Answers
B:This check is suited to “Check FortiLink control traffic with a sniffer” when trying to distinguish absent discovery packets from failed authorization or policy processing, not to verify “Confirm FortiLink physical and logical interface status” at the retail site. Checking “Confirm FortiLink physical and logical interface status” at the retail site requires evidence of its own mechanism: operational link members and FortiLink interface status must be healthy before management can synchronize; that is not the outcome measured by “Check FortiLink control traffic with a sniffer”.
C:The proposed check concerns “Verify FortiLink management address reachability” rather than “Confirm FortiLink physical and logical interface status”: controller communication depends on valid IP settings or the supported Layer 2 FortiLink path. For “Confirm FortiLink physical and logical interface status” on a central switching stack, a better test would be to inspect FortiGate member links and the corresponding switch-facing ports, which targets distinguish a dead uplink from a controller configuration problem rather than the alternative diagnostic “Verify FortiLink management address reachability”.
D:This check is suited to “Verify NTP and clock consistency” when trying to understand authentication failures or event timestamps that do not align with controller records, not to verify “Confirm FortiLink physical and logical interface status” at the retail site. Checking “Confirm FortiLink physical and logical interface status” at the retail site requires evidence of its own mechanism: operational link members and FortiLink interface status must be healthy before management can synchronize; that is not the outcome measured by “Verify NTP and clock consistency”.
Question 660
During a change window in the airport office, engineers are asked to determine whether switch control messages can reach the FortiGate. What should they configure rather than using a feature for an adjacent purpose?
- Verify FortiLink management address reachability
- Check FortiSwitch discovery and authorization state
- Inspect topology view for a missing descendant
- Check the switch-controller management process
Explanation
Correct Answer
A:At this network boundary, controller communication depends on valid IP settings or the supported Layer 2 FortiLink path. The operator can test this claim by the specific check: test management-path connectivity and inspect assigned addresses.
Incorrect Answers
B:Compared with the requested “Verify FortiLink management address reachability” at the airport office, this would explain why a physically connected new switch does not receive central configuration instead: discovery detects the unit; authorization controls whether it becomes a managed device. At the airport office, the operational proof would instead be to test management-path connectivity and inspect assigned addresses, whereas “Check FortiSwitch discovery and authorization state” is validated by a different test: compare detected serials with authorized managed-switch inventory.
C:For the airport office, “Inspect topology view for a missing descendant” is a different type of control from “Verify FortiLink management address reachability”: the stack topology identifies parent and child switch relationships and intermediate uplinks. Unlike the requested feature, that setting addresses the need to locate the ISL segment that interrupts downstream FortiSwitch discovery, not the objective to determine whether switch control messages can reach the FortiGate.
D:Compared with the requested “Verify FortiLink management address reachability” at the airport office, this would investigate a control-plane problem despite working ordinary Ethernet links instead: controller and managed-switch processes operate separately from basic Layer 2 forwarding. At the airport office, the operational proof would instead be to test management-path connectivity and inspect assigned addresses, whereas “Check the switch-controller management process” is validated by a different test: review controller process health and device management daemon logs.