CCNA Switching and Network Access Practice Test 17 — 15 Questions

Question 1

Drag and drop the STP port roles on the left to their descriptions on the right.

Accepted Answer

Root port: Provides the best path to the root bridge from a non-root switch.. In STP/RSTP, root ports provide best path to root; designated ports are the forwarding ports per segment; alternate ports back up root ports; backup ports back up designated ports; blocking ports prevent loops; disabled ports are shut down.

Answer

Designated port: Provides a backup path to the root bridge in case the root port fails.

Answer

Alternate port: Provides a backup path to the root bridge when the root port fails.

Answer

Backup port: Provides a backup path for the root port when the root port fails.

Question 2

Drag and drop the following steps into the correct order to capture and analyze traffic on IOS-XE using the embedded packet capture feature, then export the capture for analysis in Wireshark to isolate a Layer 2 or Layer 3 fault.

Accepted Answer

Define the capture point specifying the interface and direction (monitor capture point command). Embedded Packet Capture (EPC) on IOS-XE uses exec-mode monitor capture commands without needing global configuration mode. First, define the capture point specifying the interface and direction. Then start the capture to collect packets. Stop the capture after gathering sufficient data, and finally export the file to a TFTP server for analysis in Wireshark.

Question 3

Drag and drop the following steps into the correct order to capture and analyze traffic on IOS-XE using the embedded packet capture feature, and in Wireshark to isolate a Layer 2 or Layer 3 fault.

Accepted Answer

Enter privileged EXEC mode, enable capture on the interface, define buffer and filter, start capture, then export for Wireshark analysis.. After entering privileged EXEC mode, enable capture on the interface, define buffer/filter, start capture, then export for Wireshark analysis; starting before configuring buffer would fail.

Question 4

A network troubleshooter is using Cisco IOS-XE's embedded packet capture feature to capture traffic on an interface and then analyze it in Wireshark to isolate a Layer 2 or Layer 3 fault. Which of the following sequences represents the correct order of steps?

Accepted Answer

Define the capture point with interface and optional filter, start the capture, stop the capture, export the capture file, then analyze in Wireshark.. The correct workflow is to first define the capture point (interface and any filters), then start the capture, stop it when sufficient data is collected, export the captured packets to a file, and finally open that file in Wireshark for analysis. Starting the capture before defining the point, exporting before stopping, or defining the point after stopping all result in an invalid or incomplete capture process.

Answer

Start the capture, define the capture point with interface and filter, stop the capture, export the capture file, then analyze in Wireshark.

Answer

Define the capture point, start the capture, export the capture file, stop the capture, then analyze in Wireshark.

Answer

Start the capture, stop the capture, define the capture point, export the capture file, then analyze in Wireshark.

Question 5

Drag and drop the following steps into the correct order to capture and analyze traffic on IOS-XE using the embedded packet capture feature, and in Wireshark to isolate a Layer 2 or Layer 3 fault.

Accepted Answer

Access privileged EXEC mode, create a capture buffer, associate a capture point, start the capture, stop and export the capture, analyze in Wireshark. For IOS‑XE embedded packet capture, the correct order is: 1) Access privileged EXEC mode (required for all monitor commands), 2) Create a capture buffer, 3) Associate a capture point, 4) Start the capture, 5) Stop the capture, 6) Export the capture, 7) Analyze in Wireshark. Options B, C, and D each violate the required sequence: B starts buffer creation before entering privileged mode, C associates the point before creating the buffer, and D omits the critical 'start' step entirely.

Answer

Create a capture buffer, access privileged EXEC mode, associate a capture point, start the capture, stop and export the capture, analyze in Wireshark

Answer

Access privileged EXEC mode, associate a capture point, create a capture buffer, start the capture, stop and export the capture, analyze in Wireshark

Answer

Access privileged EXEC mode, create a capture buffer, associate a capture point, stop and export the capture, analyze in Wireshark

Question 6

Drag and drop the following steps into the correct order to capture and analyze traffic on IOS-XE using the embedded packet capture feature, and in Wireshark to isolate a Layer 2 or Layer 3 fault.

Accepted Answer

Define the capture interface, apply a filter, start capture, stop capture, export for analysis in Wireshark.. First define the capture interface, then apply a filter, start capture, stop it, and finally export for analysis in Wireshark.

Answer

Apply a filter, define the capture interface, start capture, export for analysis, stop capture.

Answer

Define the capture interface, start capture, apply a filter, stop capture, export for analysis.

Answer

Apply a filter, start capture, define the capture interface, stop capture, export for analysis.

Question 7

Drag and drop the following steps into the correct order to capture and analyze traffic on IOS-XE using the embedded packet capture feature, and in Wireshark to isolate a Layer 2 or Layer 3 fault.

Accepted Answer

Configure the capture point, define the capture buffer, start the capture, stop the capture, export the capture. The correct order for embedded packet capture on IOS-XE is: configure the capture point first (to define the traffic filter), then define the capture buffer, start the capture, stop the capture, and finally export the capture. Starting the capture after configuring both the point and buffer ensures that traffic is captured correctly. Exporting before stopping may result in incomplete data.

Question 8

Drag and drop the following steps into the correct order to capture and analyze traffic on IOS-XE using the embedded packet capture feature, then export to Wireshark to isolate a Layer 2 or Layer 3 fault.

Accepted Answer

Enter privileged EXEC mode, define the capture buffer, specify the interface and direction, start the capture, stop the capture, export the capture to a .pcap file, transfer the file, and analyze in Wireshark.. First enter privileged mode, then define the capture buffer, specify the interface and direction, start the capture, stop it after collecting data, export to a .pcap file, then transfer and analyze in Wireshark.

Answer

Enter global configuration mode, define the capture buffer, specify the interface and direction, start the capture, stop the capture, export the capture to a .pcap file, transfer the file, and analyze in Wireshark.

Answer

Enter privileged EXEC mode, specify the interface and direction, define the capture buffer, start the capture, stop the capture, export the capture to a .pcap file, transfer the file, and analyze in Wireshark.

Answer

Enter privileged EXEC mode, define the capture buffer, specify the interface and direction, start the capture, export the capture to a .pcap file, stop the capture, transfer the file, and analyze in Wireshark.

Question 9

What is the correct order of steps to capture and analyze traffic on IOS-XE using the embedded packet capture feature, and in Wireshark to isolate a Layer 2 or Layer 3 fault?

Accepted Answer

Define the capture point with interface and optional filter, then start the capture, stop it, and export the capture file for analysis in Wireshark.. The correct order for embedded packet capture on IOS-XE is to first define the capture point with the desired interface and optional filter, then start the capture, stop it after capturing the needed traffic, and finally export the file for analysis in Wireshark. Option A accurately reflects this sequence. Option B fails because the capture must be defined before starting. Option C fails because exporting should occur after stopping the capture. Option D fails because analysis is performed externally, not on the router.

Answer

Start the capture immediately, then define the capture point with interface and filter, stop the capture, and export the file for analysis.

Answer

Define the capture point, start the capture, export the file, and then stop the capture.

Answer

Define the capture point, start the capture, stop it, then analyze the capture directly on the router without exporting.

Question 10

Which TWO statements accurately describe the use of packet capture tools for troubleshooting Layer 2/3 issues?

Accepted Answer

A packet capture that shows frames with the same source and destination MAC addresses but different 802.1Q VLAN tags indicates a possible trunk misconfiguration.. Option B is correct because frames with identical source and destination MAC addresses but different 802.1Q VLAN tags indicate the same device is reachable on multiple VLANs, which commonly results from a misconfigured trunk (e.g., native VLAN mismatch or inconsistent allowed VLAN lists). Option D is correct because seeing ICMP echo requests leave a router but no echo replies return suggests the reply is blocked or dropped at some intermediate Layer 3 hop, pointing to a routing problem rather than a Layer 2 issue. Option A is wrong: ARP requests without replies point to a Layer 2 problem (e.g., unreachable destination or filtering), not a Layer 3 routing issue. Option C is wrong: ICMP echo requests without replies could have many causes (ACLs, firewalls, routing) – a switching loop would typically generate excessive broadcasts, not just missing replies. Option E is wrong: TCP SYN without SYN-ACK typically indicates a Layer 4 filtering or unreachable server issue, or possibly a Layer 3 routing problem, not a pure Layer 1 physical fault.

Answer

A packet capture that shows ARP requests with no ARP replies indicates a Layer 3 routing issue.

Answer

A packet capture that shows ICMP echo requests but no echo replies confirms a Layer 2 switching loop.

Answer

A packet capture that shows TCP SYN packets with no SYN-ACK replies indicates a Layer 1 physical issue.

Question 11

Drag and drop the following steps into the correct order to configure Root Guard on designated ports, Loop Guard on non-designated ports, and BPDU Guard on PortFast ports, including the recovery steps when a port enters err-disabled.

Accepted Answer

1. Configure Root Guard on designated ports. 2. Configure Loop Guard on non-designated ports. 3. Configure BPDU Guard on PortFast ports. 4. Enable errdisable recovery globally. 5. Manually re-enable the err-disabled port.. The correct order is Option A because: 1) Root Guard is applied to designated ports to protect the root bridge election; 2) Loop Guard is applied to non-designated ports to prevent loops caused by unidirectional links; 3) BPDU Guard is applied to PortFast-enabled ports to shut down ports that receive BPDUs unexpectedly. Options B, C, and D incorrectly assign these guards to the wrong port roles (e.g., Option B places BPDU Guard on designated ports and Root Guard on non-designated ports, which violates the intended protection). Steps 4 and 5 apply only to BPDU Guard, as it transitions the port to err-disabled state upon BPDU reception; Root Guard and Loop Guard cause blocking states (root-inconsistent or loop-inconsistent), not err-disabled. Therefore, the recovery steps (errdisable recovery and manual re-enable) are only relevant for ports configured with BPDU Guard.

Question 12

Drag and drop the following steps into the correct order to configure Root Guard on designated ports, Loop Guard on non-designated ports, and BPDU Guard on PortFast ports, and to recover a port that enters err-disabled due to a BPDU guard violation.

Accepted Answer

1. Configure Root Guard on designated ports. 2. Configure Loop Guard on non-designated ports. 3. Configure BPDU Guard on PortFast ports. 4. To recover a port that enters err-disabled due to BPDU Guard violation, manually shut and no shut the interface.. Root Guard on designated, Loop Guard on non-designated, then BPDU Guard on PortFast; recovery requires interface reset after violation.

Answer

1. Configure BPDU Guard on PortFast ports. 2. Configure Loop Guard on non-designated ports. 3. Configure Root Guard on designated ports. 4. To recover a port that enters err-disabled due to BPDU Guard violation, re-enable BPDU Guard on the port.

Answer

1. Configure Loop Guard on non-designated ports. 2. Configure Root Guard on designated ports. 3. Configure BPDU Guard on PortFast ports. 4. To recover a port that enters err-disabled due to BPDU Guard violation, configure errdisable recovery cause bpduguard.

Answer

1. Configure Root Guard on designated ports. 2. Configure BPDU Guard on PortFast ports. 3. Configure Loop Guard on non-designated ports. 4. To recover a port that enters err-disabled due to BPDU Guard violation, remove BPDU Guard from the port.

Question 13

Drag and drop the following steps into the correct order to configure Root Guard on designated ports, Loop Guard on non-designated ports, and BPDU Guard on PortFast ports, and then recover a port that enters err-disabled state.

Accepted Answer

1. Configure Root Guard on designated ports. 2. Configure Loop Guard on non-designated ports. 3. Configure BPDU Guard on PortFast ports. 4. Enable errdisable recovery globally. 5. Re-enable the err-disabled port manually.. The correct sequence applies STP protections to their proper port roles: Root Guard on designated ports to prevent unexpected superior BPDUs, Loop Guard on non-designated ports to prevent unidirectional link failure from causing loops, and BPDU Guard on PortFast ports to block rogue switches. Distractors B and D are wrong because they mismatch the guard types to port roles (e.g., B puts Loop Guard on designated, Root Guard on non-designated; D does the opposite). Distractor C incorrectly reverses the recovery steps by re-enabling the port before enabling errdisable recovery globally, and it also reorders protection configuration without logical benefit.

Question 14

Drag and drop the following steps into the correct order to configure Root Guard on designated ports, Loop Guard on non-designated ports, and BPDU Guard on PortFast ports, including recovery steps when a port enters err-disabled.

Accepted Answer

1. Configure Root Guard on designated ports. 2. Configure Loop Guard on non-designated ports. 3. Configure BPDU Guard on PortFast ports. 4. Configure errdisable recovery for the cause (e.g., bpduguard).. Root Guard must be applied first on designated ports to prevent unwanted root bridge changes, then Loop Guard on non-designated ports to prevent loops, followed by BPDU Guard on PortFast ports. Recovery steps are last because they apply after a violation occurs.

Question 15

Drag and drop the following steps into the correct order to configure Root Guard on a designated port, Loop Guard on a non-designated port, and BPDU Guard on a PortFast port, along with the recovery steps when a port enters err-disabled state.

Accepted Answer

1. Enter global configuration mode. 2. Configure Root Guard on the designated port. 3. Configure Loop Guard on the non-designated port. 4. Configure BPDU Guard on the PortFast-enabled port. 5. Configure errdisable recovery for BPDU Guard.. The order follows the logical sequence: enter config mode, then configure each guard feature on its respective port, and finally set the errdisable recovery to automatically re-enable ports after a BPDU Guard violation.

Answer

1. Enter global configuration mode. 2. Configure BPDU Guard on the PortFast-enabled port. 3. Configure Root Guard on the designated port. 4. Configure Loop Guard on the non-designated port. 5. Configure errdisable recovery for BPDU Guard.

Answer

1. Enter global configuration mode. 2. Configure Loop Guard on the non-designated port. 3. Configure Root Guard on the designated port. 4. Configure BPDU Guard on the PortFast-enabled port. 5. Configure errdisable recovery for BPDU Guard.

Answer

1. Enter global configuration mode. 2. Configure Root Guard on the designated port. 3. Configure BPDU Guard on the PortFast-enabled port. 4. Configure Loop Guard on the non-designated port. 5. Configure errdisable recovery for BPDU Guard.