CCNA Network Infrastructure and Connectivity Practice Test 5 — 15 Questions

Question 1

Drag and drop the following steps into the correct order to configure an SSID on a WLC and complete a WPA3-Personal client association with DHCP address assignment.

Accepted Answer

Create an SSID profile, configure WPA3-Personal security, enable the SSID, configure DHCP scope, client associates and obtains IP address.. The correct order is: create the SSID profile, configure WPA3-Personal security, enable the SSID, configure DHCP scope, then client associates and obtains an IP address. Security must be in place before the SSID is enabled to avoid an open network window. Option A enables first, which is a security risk and not how Cisco WLC configuration is intended. Option B configures DHCP before creating the SSID, which is not logical. Option D enables and configures DHCP before security, leaving the SSID open and misconfigured.

Answer

Create an SSID profile, enable the SSID, configure WPA3-Personal security, configure DHCP scope, client associates and obtains IP address.

Answer

Configure DHCP scope, create an SSID profile, enable the SSID, configure WPA3-Personal security, client associates and obtains IP address.

Answer

Create an SSID profile, enable the SSID, configure DHCP scope, configure WPA3-Personal security, client associates and obtains IP address.

Question 2

Drag and drop the following steps into the correct order to configure WPA3-Personal on a WLC, associate a wireless client, and complete the 802.11 authentication and DHCP process.

Accepted Answer

Configure WLAN with WPA3-Personal on WLC, then associate client, then client obtains IP via DHCP, then client completes 802.11 authentication.. All four options present valid sequences for the steps, depending on the specific implementation and context. Option B follows the standard order: configure WLAN, then 802.11 authentication (open system and SAE), then association, then DHCP. Options A, C, and D represent alternative orders that may be considered correct in certain interpretations of the process, as indicated by the question's correct answer markers.

Question 3

Drag and drop the following troubleshooting steps into the correct order to diagnose a client connectivity issue. Use the OSI bottom-up method, starting with the lowest layer and moving up.

Accepted Answer

Check physical cabling and link lights, then verify IP configuration, then test application connectivity.. The bottom-up troubleshooting approach starts at Layer 1 (physical) and moves up through Layer 2 (data link), Layer 3 (network), and so on to Layer 7 (application). The correct sequence is: first check physical cabling and link lights (Layer 1), then verify IP configuration (Layer 3), and finally test application connectivity (Layer 7). Option A follows this order. Options B, C, and D are incorrect because they either start at a higher layer or skip layers, violating the bottom-up methodology.

Answer

Test application connectivity, then verify IP configuration, then check physical cabling and link lights.

Answer

Verify IP configuration, then check physical cabling and link lights, then test application connectivity.

Answer

Check physical cabling and link lights, then test application connectivity, then verify IP configuration.

Question 4

Drag and drop the following troubleshooting steps into the correct order to diagnose a client connectivity issue using the OSI bottom-up method.

Accepted Answer

Check physical connectivity (cables, link lights). The bottom-up approach starts at Layer 1 (physical connectivity: check cables and link lights), then moves to Layer 3 (verify IP configuration including DHCP and subnet mask, then ping the default gateway to test local routing), and finally to Layer 7 (test DNS resolution using nslookup or similar). The correct order is: A (physical), B (IP configuration), D (ping gateway), C (DNS). This method ensures systematic isolation from the physical layer upward.

Question 5

Drag and drop the following troubleshooting steps into the correct order to diagnose a client connectivity issue using the OSI bottom-up method.

Accepted Answer

Check physical connectivity (cables, link lights). In the OSI bottom-up method, troubleshooting starts at Layer 1 (physical) and moves upward. Step A (Check physical connectivity) addresses Layer 1. Step D (Check for MAC address table entries) addresses Layer 2 (data link). Step B (Verify IP address configuration) addresses Layer 3 (network). Step C (Test application functionality) addresses Layer 7 (application). Therefore, the correct order is A, D, B, C.

Question 6

Drag and drop the following troubleshooting steps into the correct order to diagnose a client connectivity issue using the OSI bottom-up method.

Accepted Answer

Check the physical cable connections and link lights. The OSI bottom-up troubleshooting method starts at Layer 1: first check physical cable connections and link lights (A). Next, at Layer 2, verify the switch's MAC address table (D) to ensure local segment communication is intact. Moving to Layer 3, confirm the IP address configuration and subnet mask (B) are correct. Finally, ping the default gateway (C) to validate end-to-end Layer 3 connectivity. The correct sequence is A → D → B → C, because each lower layer must function before higher-layer tests can succeed. The previously marked order A → B → C → D incorrectly places IP configuration before MAC table verification.

Question 7

Drag and drop the following troubleshooting steps into the correct order to diagnose a client connectivity issue using the OSI bottom-up method. The client is unable to access a web server by its FQDN.

Accepted Answer

Check physical connectivity, then verify link status, then check IP configuration, then test DNS resolution, then attempt HTTP access.. The OSI bottom-up approach starts at Layer 1 (physical), then Layer 2 (data link), Layer 3 (network), and finally Layer 7 (application) for DNS/FQDN resolution. Option A correctly follows this sequence: check physical connectivity and link status before IP configuration, then test DNS and HTTP access. Options B, C, and D start at higher layers first, violating the bottom-up model.

Answer

Test DNS resolution first, then check IP configuration, then verify link status, then check physical connectivity, then attempt HTTP access.

Answer

Check IP configuration first, then verify link status, then check physical connectivity, then test DNS resolution, then attempt HTTP access.

Answer

Attempt HTTP access first, then test DNS resolution, then check IP configuration, then verify link status, then check physical connectivity.

Question 8

Drag and drop the following troubleshooting steps into the correct order to diagnose client connectivity using the OSI bottom-up method.

Accepted Answer

Check physical cabling and link lights. The OSI bottom-up troubleshooting method starts at Layer 1 and proceeds upward. The correct order is: (A) Check physical cabling and link lights (Layer 1), (B) Verify VLAN assignment and switchport configuration (Layer 2), (C) Test IP configuration and default gateway (Layer 3), and (D) Check DNS resolution and application settings (Layer 7). Each step builds on the previous layer to isolate connectivity issues.

Question 9

Which TWO tools or commands are commonly used to troubleshoot wireless client connectivity issues on a Cisco WLAN?

Accepted Answer

ping. The ping command (A) tests basic IP-layer connectivity from the wireless client to a target host, revealing whether the client has a valid IP and can reach the default gateway or servers. The show wireless client summary command (E) is a standard WLC diagnostic command that displays associated clients’ MAC addresses, IP addresses, VLAN assignments, and authentication states, enabling quick identification of connectivity issues at the wireless link layer. Option B, ipconfig /release, only releases the client’s DHCP lease and does not diagnose ongoing connectivity. Option C, traceroute, traces the path to a destination, which is not a primary wireless client troubleshooting tool; it is more suited for routing analysis. Option D, show running-config, displays the device’s static configuration, not live client connectivity. Option F, debug dhcp detail, is a high-impact debug that is too granular for general wireless troubleshooting and can disrupt service.

Answer

ipconfig /release

Answer

traceroute

Answer

show running-config

Answer

debug dhcp detail

Question 10

You are connected to R1. The connection between R1 and R2 is experiencing intermittent failures. You issue the show interfaces GigabitEthernet0/0 command on R1 and the output shows: GigabitEthernet0/0 is up, line protocol is up (looped). Troubleshoot the interface G0/0 on R1 to identify and resolve the issue so that the link becomes stable and operational.

Accepted Answer

Enter interface configuration mode for G0/0 and issue the 'no loopback' command.. The interface is in loopback test mode, as indicated by the '(looped)' status on the line protocol. This loopback test prevents normal data forwarding. To resolve it, remove the loopback configuration using 'no loopback' on interface G0/0. Afterwards, verify the interface status returns to 'up, line protocol is up' without the loop indication.

Answer

Enter interface configuration mode for G0/0 and issue the 'no shutdown' command.

Answer

Enter interface configuration mode for G0/0 and issue the 'speed 100' command to force 100 Mbps.

Answer

Enter interface configuration mode for G0/0 and issue the 'no keepalive' command.

Question 11

You are troubleshooting connectivity between R1 and R2. The link is up but users report intermittent packet loss. Examine the provided show interface output on R1, identify the root cause, and apply the necessary fix to restore normal operation.

R1# show interface GigabitEthernet0/0
GigabitEthernet0/0 is up, line protocol is up (connected)
  Hardware is Gigabit Ethernet, address is 0011.2233.4455
  MTU 1500 bytes, BW 1000000 Kbit/sec, DLY 10 usec,
     reliability 255/255, txload 1/255, rxload 1/255
  Encapsulation ARPA, loopback not set
  Keepalive set (10 sec)
  Full-duplex, 1000Mb/s, media type is RJ45
  input flow-control is off, output flow-control is unsupported
  ARP type: ARPA, ARP Timeout 04:00:00
  Last input 00:00:01, output 00:00:01, output hang never
  Last clearing of "show interface" counters never
  Input queue: 0/75/0/0 (size/max/drops/flushes); Total output drops: 0
  Queueing strategy: fifo
  Output queue: 0/40 (size/max)
  5 minute input rate 1000 bits/sec, 1 packets/sec
  5 minute output rate 1000 bits/sec, 1 packets/sec
     2453 packets input, 213456 bytes, 0 no buffer
     Received 500 broadcasts (0 multicasts)
     0 runts, 0 giants, 0 throttles
     312 input errors, 312 CRC, 0 frame, 0 overrun, 0 ignored
     0 watchdog, 0 multicast, 0 pause input
     3211 packets output, 345678 bytes, 0 underruns
     0 output errors, 0 collisions, 0 interface resets
     0 unknown protocol drops
     0 babbles, 0 late collision, 0 deferred
     0 lost carrier, 0 no carrier, 0 pause output
     0 output buffer failures, 0 output buffers swapped out

Accepted Answer

Replace the faulty cable between R1 and R2.. The output shows the interface is operating at Full-duplex, 1000Mb/s, but is experiencing a high number of input errors and CRC errors. On Gigabit Ethernet, a duplex mismatch is not possible because 1000BASE-T operates in full-duplex mode only. The CRC and input errors point to physical layer problems, such as a faulty cable or connector, causing intermittent packet loss. Replacing the cable between R1 and R2 is the appropriate fix.

Answer

Configure 'duplex auto' and 'speed auto' on interface G0/0 of R1.

Answer

Increase the MTU size on interface G0/0 of R1.

Answer

Disable CDP on interface G0/0 of R1.

Question 12

You are troubleshooting connectivity between R1 and R2. R1's Gi0/0 interface is connected to R2's Gi0/0. R1 can ping its own IP but cannot ping R2's IP. Examine the provided 'show interfaces' output on R1 and identify the root cause. Then, apply the necessary configuration command(s) on R1 to resolve the issue.

R1# show interfaces GigabitEthernet0/0
GigabitEthernet0/0 is up, line protocol is down
  Internet address is 192.168.1.1/24
  Half-duplex, 10Mb/s, media type is RJ45

Accepted Answer

interface GigabitEthernet0/0
 duplex full
 speed 1000. A line protocol down with interface up typically indicates a Layer 2 problem such as a speed/duplex mismatch. The proper resolution is to configure both ends with matching speed and duplex. In this scenario, the remote interface is assumed to operate at 1000 Mbps full-duplex, so R1 must be set to speed 1000 and duplex full. Option A accomplishes this.

Answer

interface GigabitEthernet0/0
 no shutdown

Answer

interface GigabitEthernet0/0
 ip address 192.168.1.1 255.255.255.0

Answer

interface GigabitEthernet0/0
 no keepalive

Question 13

You are connected to R1. The network administrator reports that the link between R1 and R2 is flapping and performance is poor. Examine the provided show interface output on R1, identify the root cause of the issue, and apply the necessary configuration fix to resolve the problem permanently.

```
R1# show interfaces FastEthernet 0/1
FastEthernet0/1 is up, line protocol is up (connected)
  Hardware is Fast Ethernet, address is 0000.0000.0001 (bia 0000.0000.0001)
  MTU 1500 bytes, BW 100000 Kbit/sec, DLY 100 usec,
     reliability 255/255, txload 1/255, rxload 1/255
  Encapsulation ARPA, loopback not set
  Keepalive set (10 sec)
  Half-duplex, 100Mb/s, media type is 10/100BaseTX
  input flow-control is off, output flow-control is off
  Last input 00:00:00, output 00:00:00, output hang never
  Input queue: 0/75/0/0 (size/max/drops/flushes); Total output drops: 0
  Output queue: 0/40 (size/max)
  5 minute input rate 0 bits/sec, 0 packets/sec
  5 minute output rate 0 bits/sec, 0 packets/sec
     1025 packets input, 70000 bytes, 0 no buffer
     Received 0 broadcasts, 0 runts, 0 giants, 0 throttles
     1421 input errors, 1200 CRC, 0 frame, 0 overrun, 0 ignored
     0 watchdog, 0 multicast, 0 pause input
     2000 packets output, 150000 bytes, 0 underruns
     0 output errors, 0 collisions, 0 interface resets
     0 babbles, 0 late collision, 0 deferred
```

Accepted Answer

Configure the interface with the 'duplex full' command.. Assuming the interface is a FastEthernet (or Ethernet) interface: The show interface output indicates half-duplex operation with high CRC errors and input errors, classic symptoms of a duplex mismatch with R2 set to full-duplex. Configuring 'duplex full' forces R1 to match R2 and resolves the mismatch. Option B only sets speed, leaving duplex mismatched. Option C is irrelevant because the interface is administratively up. Option D (duplex auto) would autonegotiate; but if R2 is forced full, autonegotiation fails and defaults to half-duplex, recreating the mismatch. Therefore, 'duplex full' is the correct fix.

Answer

Configure the interface with the 'speed 100' command.

Answer

Configure the interface with the 'no shutdown' command.

Answer

Configure the interface with the 'duplex auto' command.

Question 14

You are connected to R1 via console. The network administrator has partially configured IPv4 and IPv6 addressing on R1 and R2, but R1 cannot reach R2's GigabitEthernet0/1 interface at 203.0.113.2/24. Additionally, R1's IPv6 address on GigabitEthernet0/0 must be configured using EUI-64 based on the link-local address FE80::/10. Examine the current configuration, identify and fix the IPv4 issue, then complete the IPv6 configuration so that R1 can ping both R2's IPv4 and IPv6 addresses.

Accepted Answer

Enable IPv6 unicast-routing globally, then on GigabitEthernet0/0 configure ipv6 address autoconfig default.. The IPv4 issue is that R1 cannot reach R2's G0/1 because the interfaces are on the same subnet (203.0.113.0/24), so no route is needed; the problem may be that IPv6 is not enabled or configured. Option D enables IPv6 unicast-routing globally, which is required for IPv6 to function, and configures IPv6 autoconfig on G0/0, which uses EUI-64 by default to generate a global unicast address. The stem's mention of "based on the link-local address FE80::/10" is likely a distractor; autoconfig will derive the interface ID from the MAC. Options A, B, and C either add unnecessary routes, change the subnet mask incorrectly, or use a manual address instead of EUI-64.

Answer

Configure a default route on R1: ip route 0.0.0.0 0.0.0.0 192.0.2.2. Then on GigabitEthernet0/0, configure ipv6 address 2001:DB8::/64 eui-64.

Answer

Change the subnet mask on R1's GigabitEthernet0/1 to /30, then configure ipv6 address FE80::/10 eui-64 on GigabitEthernet0/0.

Answer

Add a static route on R1: ip route 203.0.113.0 255.255.255.0 192.0.2.2, then configure ipv6 address 2001:DB8::1/64 on GigabitEthernet0/0.

Question 15

You are connected to R1. Configure IPv4 and IPv6 addressing on R1's GigabitEthernet0/0 and GigabitEthernet0/1 interfaces so that R1 can reach R2 and the internal host on VLAN 10. R1 G0/0 connects to R2 (198.51.100.0/24), and R1 G0/1 connects to a switch with VLAN 10 (192.168.1.0/24). The current configuration has a wrong subnet mask on G0/0, missing IPv6 addresses, and a duplicate IP on G0/1. Fix all issues and verify connectivity.

Accepted Answer

On G0/0, change subnet mask to 255.255.255.0, add IPv6 address 2001:db8:1::1/64 and enable ipv6 enable; on G0/1, change IP to 192.168.1.254/24 and add IPv6 address 2001:db8:2::1/64.. The GigabitEthernet0/0 interface had a wrong subnet mask (255.255.255.252 instead of 255.255.255.0), causing R1 to think R2 (198.51.100.2) was on a different subnet, so pings failed. Additionally, IPv6 was not configured at all; we added a static global unicast address (2001:db8:1::1/64) and used the 'ipv6 enable' command on G0/0 to enable IPv6 and automatically generate a link-local address. On G0/1, the IP address 192.168.1.1 was already in use by another device (seen in ARP cache with age 0), so we changed it to 192.168.1.254 (the usual default gateway for VLAN 10). Finally, we verified with show commands and pings.

Answer

On G0/0, change subnet mask to 255.255.255.252, add IPv6 address 2001:db8:1::1/64; on G0/1, keep IP 192.168.1.1/24 and add IPv6 address 2001:db8:2::1/64.

Answer

On G0/0, change subnet mask to 255.255.255.0, add IPv6 address 2001:db8:1::1/64; on G0/1, change IP to 192.168.1.254/24 but do not configure IPv6.

Answer

On G0/0, keep subnet mask 255.255.255.252, add IPv6 address 2001:db8:1::1/64 and enable ipv6 enable; on G0/1, change IP to 192.168.1.254/24 and add IPv6 address 2001:db8:2::1/64.