Question 630
A change record for a FortiLink-managed access switch states “Review the ACL hardware resource usage.” Which description correctly explains what this will accomplish?
- An ingress ACL classifies traffic arriving at an interface and applies permitted hardware actions
- Community PVLAN members can communicate with their own community and the promiscuous primary port
- An EtherType comparison identifies the payload protocol without relying on TCP/UDP port numbers
- Switch ACL classifiers, groups and counters consume finite hardware resources that can be fragmented
Explanation
Correct Answer
D:The critical distinction is that the configured operation is meant to diagnose rejection of additional switch ACL entries despite apparently valid syntax. The most relevant validation is to inspect ACL usage and available hardware entries before changing rule order for the equipment at the lab.
Incorrect Answers
A:This outcome would be relevant to “Install an ingress ACL for received traffic” at the lab, not the task “Review the ACL hardware resource usage”; the other task is to filter packets as they enter a FortiSwitch forwarding pipeline. The action “Review the ACL hardware resource usage” targets a different result: switch ACL classifiers, groups and counters consume finite hardware resources that can be fragmented; the proposed alternative would instead be checked by review ingress ACL match counters while sending matching test frames.
B:That behavior applies when engineers “Apply a community secondary PVLAN to one workgroup”; the different operation “Review the ACL hardware resource usage” is intended to diagnose rejection of additional switch ACL entries despite apparently valid syntax. That different feature is verified by test peer reachability inside the community and deny a connection to a different community; for “Review the ACL hardware resource usage” on a FortiLink-managed access switch, the relevant evidence is to inspect ACL usage and available hardware entries before changing rule order.
C:That behavior applies when engineers “Use an ACL Ethernet-type classifier”; the different operation “Review the ACL hardware resource usage” is intended to diagnose rejection of additional switch ACL entries despite apparently valid syntax. That different feature is verified by read the EtherType from the frame header and inspect the ACL service match; for “Review the ACL hardware resource usage” on a FortiLink-managed access switch, the relevant evidence is to inspect ACL usage and available hardware entries before changing rule order.
Question 631
On a switch linked to a FortiGate running FortiOS 7.6 in the staging rack, the next task is to limit local FortiSwitch capture to packets relevant to a particular troubleshooting investigation. What is the appropriate configuration decision?
- Configure an ERSPAN mirror for an IP-reachable analyzer
- Configure a local SPAN mirror
- Check packet capture storage and profile capacity
- Create a packet capture profile with a filter
Explanation
Correct Answer
D:That setting is appropriate here because a capture profile defines the observed interface and packet selection before capture starts. This distinction is material to the staging rack, where the stated goal is to limit local FortiSwitch capture to packets relevant to a particular troubleshooting investigation.
Incorrect Answers
A:Compared with the requested “Create a packet capture profile with a filter” at the staging rack, this would send mirrored traffic to a collector reached across a routed network instead: ERSPAN encapsulates mirrored frames for transport over an IP network to a remote destination. At the staging rack, the operational proof would instead be to review captured headers and verify the chosen filter matches the targeted flow, whereas “Configure an ERSPAN mirror for an IP-reachable analyzer” is validated by a different test: check routed collector reachability and ERSPAN encapsulation on arriving packets.
B:Compared with the requested “Create a packet capture profile with a filter” at the staging rack, this would send copies of a source port's traffic to a diagnostic port on the same switch instead: SPAN duplicates selected ingress or egress traffic locally for a connected analyzer. At the staging rack, the operational proof would instead be to review captured headers and verify the chosen filter matches the targeted flow, whereas “Configure a local SPAN mirror” is validated by a different test: inspect the configured mirror source/destination and analyzer's received frames.
C:For the staging rack, “Check packet capture storage and profile capacity” is a different type of control from “Create a packet capture profile with a filter”: switch model determines capture-profile capacity and RAM-disk space for retained packets. Unlike the requested feature, that setting addresses the need to avoid losing captures on a busy switch with limited capture resources, not the objective to limit local FortiSwitch capture to packets relevant to a particular troubleshooting investigation.
Question 632
A change record for a switch serving a high-density endpoint area states “Create a packet capture profile with a filter.” Which description correctly explains what this will accomplish?
- Ingress mirror direction copies traffic entering the selected interface
- A capture profile defines the observed interface and packet selection before capture starts
- ERSPAN encapsulates mirrored frames for transport over an IP network to a remote destination
- SPAN duplicates selected ingress or egress traffic locally for a connected analyzer
- Switch model determines capture-profile capacity and RAM-disk space for retained packets
Explanation
Correct Answer
B:This is the precise control because the configured operation is meant to limit local FortiSwitch capture to packets relevant to a particular troubleshooting investigation. The most relevant validation is to review captured headers and verify the chosen filter matches the targeted flow for the equipment at the research building.
Incorrect Answers
A:That behavior applies when engineers “Choose ingress mirroring for arriving frames”; the different operation “Create a packet capture profile with a filter” is intended to limit local FortiSwitch capture to packets relevant to a particular troubleshooting investigation. That different feature is verified by verify the source packet is visible on ingress even when later filtering prevents forwarding; for “Create a packet capture profile with a filter” on a switch serving a high-density endpoint area, the relevant evidence is to review captured headers and verify the chosen filter matches the targeted flow.
C:That behavior applies when engineers “Configure an ERSPAN mirror for an IP-reachable analyzer”; the different operation “Create a packet capture profile with a filter” is intended to limit local FortiSwitch capture to packets relevant to a particular troubleshooting investigation. That different feature is verified by check routed collector reachability and ERSPAN encapsulation on arriving packets; for “Create a packet capture profile with a filter” on a switch serving a high-density endpoint area, the relevant evidence is to review captured headers and verify the chosen filter matches the targeted flow.
D:This outcome would be relevant to “Configure a local SPAN mirror” at the research building, not the task “Create a packet capture profile with a filter”; the other task is to send copies of a source port's traffic to a diagnostic port on the same switch. The action “Create a packet capture profile with a filter” targets a different result: a capture profile defines the observed interface and packet selection before capture starts; the proposed alternative would instead be checked by inspect the configured mirror source/destination and analyzer's received frames.
E:That behavior applies when engineers “Check packet capture storage and profile capacity”; the different operation “Create a packet capture profile with a filter” is intended to limit local FortiSwitch capture to packets relevant to a particular troubleshooting investigation. That different feature is verified by inspect capture file size, platform allocation and whether the profile can still record; for “Create a packet capture profile with a filter” on a switch serving a high-density endpoint area, the relevant evidence is to review captured headers and verify the chosen filter matches the targeted flow.
Question 633
A post-change review at the airport office must validate the implementation of “Create a packet capture profile with a filter.” What should the reviewer inspect first?
- Review captured headers and verify the chosen filter matches the targeted flow
- Inspect capture file size, platform allocation and whether the profile can still record
- Inspect the configured mirror source/destination and analyzer's received frames
- Check routed collector reachability and ERSPAN encapsulation on arriving packets
Explanation
Correct Answer
A:The implementation works because a capture profile defines the observed interface and packet selection before capture starts. Directly measuring that result demonstrates whether the step to limit local FortiSwitch capture to packets relevant to a particular troubleshooting investigation succeeded on a managed switch running FortiSwitchOS 7.6.
Incorrect Answers
B:This check is suited to “Check packet capture storage and profile capacity” when trying to avoid losing captures on a busy switch with limited capture resources, not to verify “Create a packet capture profile with a filter” at the airport office. Checking “Create a packet capture profile with a filter” at the airport office requires evidence of its own mechanism: a capture profile defines the observed interface and packet selection before capture starts; that is not the outcome measured by “Check packet capture storage and profile capacity”.
C:The proposed check concerns “Configure a local SPAN mirror” rather than “Create a packet capture profile with a filter”: SPAN duplicates selected ingress or egress traffic locally for a connected analyzer. For “Create a packet capture profile with a filter” on a managed switch running FortiSwitchOS 7.6, a better test would be to review captured headers and verify the chosen filter matches the targeted flow, which targets limit local FortiSwitch capture to packets relevant to a particular troubleshooting investigation rather than the alternative diagnostic “Configure a local SPAN mirror”.
D:This check is suited to “Configure an ERSPAN mirror for an IP-reachable analyzer” when trying to send mirrored traffic to a collector reached across a routed network, not to verify “Create a packet capture profile with a filter” at the airport office. Checking “Create a packet capture profile with a filter” at the airport office requires evidence of its own mechanism: a capture profile defines the observed interface and packet selection before capture starts; that is not the outcome measured by “Configure an ERSPAN mirror for an IP-reachable analyzer”.
Question 634
At the operations center, a technician is choosing between several switching features to inspect a short-lived protocol exchange at a switch control or data interface. Which one belongs in the implementation plan?
- Choose ingress mirroring for arriving frames
- Create a packet capture profile with a filter
- Configure an RSPAN remote mirror
- Run an appropriate FortiSwitch sniffer command
Explanation
Correct Answer
D:Given the described goal, a CLI sniffer can display or collect matching packets without installing a permanent forwarding rule. The operator can test this claim by the specific check: repeat the transaction and confirm the expected frame types appear in sniffer output.
Incorrect Answers
A:Compared with the requested “Run an appropriate FortiSwitch sniffer command” 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 repeat the transaction and confirm the expected frame types appear in sniffer output, 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.
B:For the operations center, “Create a packet capture profile with a filter” is a different type of control from “Run an appropriate FortiSwitch sniffer command”: a capture profile defines the observed interface and packet selection before capture starts. Unlike the requested feature, that setting addresses the need to limit local FortiSwitch capture to packets relevant to a particular troubleshooting investigation, not the objective to inspect a short-lived protocol exchange at a switch control or data interface.
C:Compared with the requested “Run an appropriate FortiSwitch sniffer command” at the operations center, this would monitor source traffic from another switch across a VLAN transport path instead: RSPAN carries mirrored Ethernet traffic over an appropriate remote mirror VLAN. At the operations center, the operational proof would instead be to repeat the transaction and confirm the expected frame types appear in sniffer output, whereas “Configure an RSPAN remote mirror” is validated by a different test: inspect RSPAN VLAN membership on intermediate trunks and packets arriving at the remote analyzer.
Question 635
An operations log records this activity at the warehouse: run an appropriate FortiSwitch sniffer command. Which result is specifically attributable to that action?
- RSPAN carries mirrored Ethernet traffic over an appropriate remote mirror VLAN
- Ingress mirror direction copies traffic entering the selected interface
- A CLI sniffer can display or collect matching packets without installing a permanent forwarding rule
- A capture profile defines the observed interface and packet selection before capture starts
Explanation
Correct Answer
C:The switch behavior that matters is: the configured operation is meant to inspect a short-lived protocol exchange at a switch control or data interface. The most relevant validation is to repeat the transaction and confirm the expected frame types appear in sniffer output for the equipment at the warehouse.
Incorrect Answers
A:This outcome would be relevant to “Configure an RSPAN remote mirror” at the warehouse, not the task “Run an appropriate FortiSwitch sniffer command”; the other task is to monitor source traffic from another switch across a VLAN transport path. The action “Run an appropriate FortiSwitch sniffer command” targets a different result: a CLI sniffer can display or collect matching packets without installing a permanent forwarding rule; the proposed alternative would instead be checked by inspect RSPAN VLAN membership on intermediate trunks and packets arriving at the remote analyzer.
B:That behavior applies when engineers “Choose ingress mirroring for arriving frames”; the different operation “Run an appropriate FortiSwitch sniffer command” is intended to inspect a short-lived protocol exchange at a switch control or data interface. That different feature is verified by verify the source packet is visible on ingress even when later filtering prevents forwarding; for “Run an appropriate FortiSwitch sniffer command” on an endpoint-facing FortiSwitch port, the relevant evidence is to repeat the transaction and confirm the expected frame types appear in sniffer output.
D:That behavior applies when engineers “Create a packet capture profile with a filter”; the different operation “Run an appropriate FortiSwitch sniffer command” is intended to inspect a short-lived protocol exchange at a switch control or data interface. That different feature is verified by review captured headers and verify the chosen filter matches the targeted flow; for “Run an appropriate FortiSwitch sniffer command” on an endpoint-facing FortiSwitch port, the relevant evidence is to repeat the transaction and confirm the expected frame types appear in sniffer output.
Question 636
The work order to inspect a short-lived protocol exchange at a switch control or data interface is marked complete on a standalone FortiSwitch appliance. Which observation most directly tests the completed configuration?
- 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
- Repeat the transaction and confirm the expected frame types appear in sniffer output
- Inspect RSPAN VLAN membership on intermediate trunks and packets arriving at the remote analyzer
- Compare the analyzer's egress trace with destination port counters
Explanation
Correct Answer
C:At this network boundary, a CLI sniffer can display or collect matching packets without installing a permanent forwarding rule. Directly measuring that result demonstrates whether the step to inspect a short-lived protocol exchange at a switch control or data interface succeeded on a standalone FortiSwitch appliance.
Incorrect Answers
A:This check is suited to “Choose ingress mirroring for arriving frames” when trying to diagnose whether a switch receives packets before its forwarding decisions, not to verify “Run an appropriate FortiSwitch sniffer command” at the headquarters. Checking “Run an appropriate FortiSwitch sniffer command” at the headquarters requires evidence of its own mechanism: a CLI sniffer can display or collect matching packets without installing a permanent forwarding rule; that is not the outcome measured by “Choose ingress mirroring for arriving frames”.
B: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 “Run an appropriate FortiSwitch sniffer command” at the headquarters. Checking “Run an appropriate FortiSwitch sniffer command” at the headquarters requires evidence of its own mechanism: a CLI sniffer can display or collect matching packets without installing a permanent forwarding rule; that is not the outcome measured by “Create a packet capture profile with a filter”.
D:The proposed check concerns “Configure an RSPAN remote mirror” rather than “Run an appropriate FortiSwitch sniffer command”: RSPAN carries mirrored Ethernet traffic over an appropriate remote mirror VLAN. For “Run an appropriate FortiSwitch sniffer command” on a standalone FortiSwitch appliance, a better test would be to repeat the transaction and confirm the expected frame types appear in sniffer output, which targets inspect a short-lived protocol exchange at a switch control or data interface rather than the alternative diagnostic “Configure an RSPAN remote mirror”.
E:The proposed check concerns “Choose egress mirroring for leaving frames” rather than “Run an appropriate FortiSwitch sniffer command”: egress mirror direction observes packets chosen for output after relevant forwarding steps. For “Run an appropriate FortiSwitch sniffer command” on a standalone FortiSwitch appliance, a better test would be to repeat the transaction and confirm the expected frame types appear in sniffer output, which targets inspect a short-lived protocol exchange at a switch control or data interface rather than the alternative diagnostic “Choose egress mirroring for leaving frames”.
Question 637
A switch rollout in the hospital wing will be approved only if it can send copies of a source port's traffic to a diagnostic port on the same switch. Which administrative action meets this acceptance criterion?
- Run an appropriate FortiSwitch sniffer command
- Configure a local SPAN mirror
- Check packet capture storage and profile capacity
- Choose ingress mirroring for arriving frames
Explanation
Correct Answer
B:In this deployment, SPAN duplicates selected ingress or egress traffic locally for a connected analyzer. This distinction is material to the hospital wing, where the stated goal is to send copies of a source port's traffic to a diagnostic port on the same switch.
Incorrect Answers
A:Compared with the requested “Configure a local SPAN mirror” at the hospital wing, this would inspect a short-lived protocol exchange at a switch control or data interface instead: a CLI sniffer can display or collect matching packets without installing a permanent forwarding rule. At the hospital wing, the operational proof would instead be to inspect the configured mirror source/destination and analyzer's received frames, whereas “Run an appropriate FortiSwitch sniffer command” is validated by a different test: repeat the transaction and confirm the expected frame types appear in sniffer output.
C:Compared with the requested “Configure a local SPAN mirror” at the hospital wing, this would avoid losing captures on a busy switch with limited capture resources instead: switch model determines capture-profile capacity and RAM-disk space for retained packets. At the hospital wing, the operational proof would instead be to inspect the configured mirror source/destination and analyzer's received frames, whereas “Check packet capture storage and profile capacity” is validated by a different test: inspect capture file size, platform allocation and whether the profile can still record.
D:For the hospital wing, “Choose ingress mirroring for arriving frames” is a different type of control from “Configure a local SPAN mirror”: ingress mirror direction copies traffic entering the selected interface. Unlike the requested feature, that setting addresses the need to diagnose whether a switch receives packets before its forwarding decisions, not the objective to send copies of a source port's traffic to a diagnostic port on the same switch.
Question 638
A change record for a switch linked to a FortiGate running FortiOS 7.6 states “Configure a local SPAN mirror.” Which description correctly explains what this will accomplish?
- Ingress mirror direction copies traffic entering the selected interface
- SPAN duplicates selected ingress or egress traffic locally for a connected analyzer
- Switch model determines capture-profile capacity and RAM-disk space for retained packets
- A CLI sniffer can display or collect matching packets without installing a permanent forwarding rule
Explanation
Correct Answer
B:For the stated requirement, the configured operation is meant to send copies of a source port's traffic to a diagnostic port on the same switch. The most relevant validation is to inspect the configured mirror source/destination and analyzer's received frames for the equipment at the training center.
Incorrect Answers
A:That behavior applies when engineers “Choose ingress mirroring for arriving frames”; the different operation “Configure a local SPAN mirror” is intended to send copies of a source port's traffic to a diagnostic port on the same switch. That different feature is verified by verify the source packet is visible on ingress even when later filtering prevents forwarding; for “Configure a local SPAN mirror” on a switch linked to a FortiGate running FortiOS 7.6, the relevant evidence is to inspect the configured mirror source/destination and analyzer's received frames.
C:This outcome would be relevant to “Check packet capture storage and profile capacity” at the training center, not the task “Configure a local SPAN mirror”; the other task is to avoid losing captures on a busy switch with limited capture resources. The action “Configure a local SPAN mirror” targets a different result: SPAN duplicates selected ingress or egress traffic locally for a connected analyzer; the proposed alternative would instead be checked by inspect capture file size, platform allocation and whether the profile can still record.
D:That behavior applies when engineers “Run an appropriate FortiSwitch sniffer command”; the different operation “Configure a local SPAN mirror” is intended to send copies of a source port's traffic to a diagnostic port on the same switch. That different feature is verified by repeat the transaction and confirm the expected frame types appear in sniffer output; for “Configure a local SPAN mirror” on a switch linked to a FortiGate running FortiOS 7.6, the relevant evidence is to inspect the configured mirror source/destination and analyzer's received frames.
Question 639
A technician says “Configure a local SPAN mirror” has solved the issue at the lab. Which diagnostic step would substantiate that claim?
- Inspect RSPAN VLAN membership on intermediate trunks and packets arriving at the remote analyzer
- Inspect capture file size, platform allocation and whether the profile can still record
- Inspect the configured mirror source/destination and analyzer's received frames
- Verify the source packet is visible on ingress even when later filtering prevents forwarding
- Repeat the transaction and confirm the expected frame types appear in sniffer output
- Review captured headers and verify the chosen filter matches the targeted flow
Explanation
Correct Answer
C:The deciding detail is that SPAN duplicates selected ingress or egress traffic locally for a connected analyzer. Directly measuring that result demonstrates whether the step to send copies of a source port's traffic to a diagnostic port on the same switch succeeded on a switch serving a high-density endpoint area.
Incorrect Answers
A:The proposed check concerns “Configure an RSPAN remote mirror” rather than “Configure a local SPAN mirror”: RSPAN carries mirrored Ethernet traffic over an appropriate remote mirror VLAN. For “Configure a local SPAN mirror” on a switch serving a high-density endpoint area, a better test would be to inspect the configured mirror source/destination and analyzer's received frames, which targets send copies of a source port's traffic to a diagnostic port on the same switch rather than the alternative diagnostic “Configure an RSPAN remote mirror”.
B:The proposed check concerns “Check packet capture storage and profile capacity” rather than “Configure a local SPAN mirror”: switch model determines capture-profile capacity and RAM-disk space for retained packets. For “Configure a local SPAN mirror” on a switch serving a high-density endpoint area, a better test would be to inspect the configured mirror source/destination and analyzer's received frames, which targets send copies of a source port's traffic to a diagnostic port on the same switch rather than the alternative diagnostic “Check packet capture storage and profile capacity”.
D:This check is suited to “Choose ingress mirroring for arriving frames” when trying to diagnose whether a switch receives packets before its forwarding decisions, not to verify “Configure a local SPAN mirror” at the lab. Checking “Configure a local SPAN mirror” at the lab requires evidence of its own mechanism: SPAN duplicates selected ingress or egress traffic locally for a connected analyzer; that is not the outcome measured by “Choose ingress mirroring for arriving frames”.
E:This check is suited to “Run an appropriate FortiSwitch sniffer command” when trying to inspect a short-lived protocol exchange at a switch control or data interface, not to verify “Configure a local SPAN mirror” at the lab. Checking “Configure a local SPAN mirror” at the lab requires evidence of its own mechanism: SPAN duplicates selected ingress or egress traffic locally for a connected analyzer; that is not the outcome measured by “Run an appropriate FortiSwitch sniffer command”.
F: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 “Configure a local SPAN mirror” at the lab. Checking “Configure a local SPAN mirror” at the lab requires evidence of its own mechanism: SPAN duplicates selected ingress or egress traffic locally for a connected analyzer; that is not the outcome measured by “Create a packet capture profile with a filter”.
Question 640
An administrator responsible for a managed switch running FortiSwitchOS 7.6 in the media studio must monitor source traffic from another switch across a VLAN transport path. Which configuration best matches that precise goal?
- Create a packet capture profile with a filter
- Configure a local SPAN mirror
- Configure an RSPAN remote mirror
- Choose ingress mirroring for arriving frames
Explanation
Correct Answer
C:The relevant mechanism is: RSPAN carries mirrored Ethernet traffic over an appropriate remote mirror VLAN. The operator can test this claim by the specific check: inspect RSPAN VLAN membership on intermediate trunks and packets arriving at the remote analyzer.
Incorrect Answers
A:For the media studio, “Create a packet capture profile with a filter” is a different type of control from “Configure an RSPAN remote mirror”: a capture profile defines the observed interface and packet selection before capture starts. Unlike the requested feature, that setting addresses the need to limit local FortiSwitch capture to packets relevant to a particular troubleshooting investigation, not the objective to monitor source traffic from another switch across a VLAN transport path.
B:Compared with the requested “Configure an RSPAN remote mirror” at the media studio, this would send copies of a source port's traffic to a diagnostic port on the same switch instead: SPAN duplicates selected ingress or egress traffic locally for a connected analyzer. At the media studio, the operational proof would instead be to inspect RSPAN VLAN membership on intermediate trunks and packets arriving at the remote analyzer, whereas “Configure a local SPAN mirror” is validated by a different test: inspect the configured mirror source/destination and analyzer's received frames.
D:Compared with the requested “Configure an RSPAN remote mirror” at the media studio, this would diagnose whether a switch receives packets before its forwarding decisions instead: ingress mirror direction copies traffic entering the selected interface. At the media studio, the operational proof would instead be to inspect RSPAN VLAN membership on intermediate trunks and packets arriving at the remote analyzer, 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.