CCNA Network Infrastructure and Connectivity Practice Test 5 — 15 Questions

Question 1

Drag and drop the OSI layer names on the left to the correct PDU names and example protocols on the right.

Accepted Answer

Physical: Bits, Ethernet; Data Link: Frames, MAC; Network: Packets, IP; Transport: Segments, TCP; Session: Data, NetBIOS; Presentation: Data, SSL/TLS. Both options A and D correctly map each OSI layer to its correct PDU and example protocol(s). Physical layer: Bits, Ethernet; Data Link: Frames, MAC; Network: Packets, IP; Transport: Segments, TCP; Session: Data, NetBIOS; Presentation: Data, SSL/TLS. Option B incorrectly swaps the PDUs for Data Link and Network (should be frames and packets). Option C incorrectly swaps the PDUs for Network and Transport (should be packets and segments).

Answer

Physical: Bits, Ethernet; Data Link: Packets, IP; Network: Frames, MAC; Transport: Segments, TCP; Session: Data, NetBIOS; Presentation: Data, SSL/TLS

Answer

Physical: Bits, Ethernet; Data Link: Frames, MAC; Network: Segments, TCP; Transport: Packets, IP; Session: Data, NetBIOS; Presentation: Data, SSL/TLS

Question 2

Drag and drop the following steps into the correct order to troubleshoot a suspected duplex mismatch and CRC errors on an interface using Cisco IOS-XE CLI commands.

Accepted Answer

1. Connect to the device via console or SSH
2. Enter privileged EXEC mode
3. Use 'show interfaces' to check for CRC errors and duplex mismatch
4. Enter global configuration mode
5. Use 'interface' command to enter the specific interface
6. Use 'speed 100' to set speed manually
7. Use 'duplex full' to set duplex manually
8. Use 'end' to exit configuration mode
9. Use 'copy running-config startup-config' to save. To troubleshoot duplex mismatch and CRC errors, the correct order is: first connect to the device and enter privileged EXEC mode, then use 'show interfaces' to diagnose the issue. Next, enter global configuration mode, select the interface, set the speed manually (e.g., 'speed 100'), then set the duplex manually (e.g., 'duplex full') to prevent the duplex from reverting to auto-negotiation. Finally, exit configuration mode with 'end' and save the running configuration with 'copy running-config startup-config'. Only option C follows this sequence exactly. Option A incorrectly sets duplex before speed. Option B performs the show command after making changes, which defeats the troubleshooting purpose. Option D sets duplex before speed and saves before exiting configuration mode, which is incorrect.

Answer

1. Connect to the device via console or SSH
2. Enter privileged EXEC mode
3. Use 'show interfaces' to check for CRC errors and duplex mismatch
4. Enter global configuration mode
5. Use 'interface' command to enter the specific interface
6. Use 'duplex full' to set duplex manually
7. Use 'speed 100' to set speed manually
8. Use 'end' to exit configuration mode
9. Use 'copy running-config startup-config' to save

Answer

1. Connect to the device via console or SSH
2. Enter privileged EXEC mode
3. Enter global configuration mode
4. Use 'interface' command to enter the specific interface
5. Use 'duplex full' to set duplex manually
6. Use 'speed 100' to set speed manually
7. Use 'end' to exit configuration mode
8. Use 'show interfaces' to check for CRC errors and duplex mismatch
9. Use 'copy running-config startup-config' to save

Answer

1. Connect to the device via console or SSH
2. Enter privileged EXEC mode
3. Use 'show interfaces' to check for CRC errors and duplex mismatch
4. Enter global configuration mode
5. Use 'interface' command to enter the specific interface
6. Use 'duplex full' to set duplex manually
7. Use 'speed 100' to set speed manually
8. Use 'copy running-config startup-config' to save
9. Use 'end' to exit configuration mode

Question 3

Drag and drop the following steps into the correct order to troubleshoot a suspected duplex mismatch and CRC errors on a Cisco switch interface.

Accepted Answer

Enter privileged EXEC mode using the 'enable' command.. The correct troubleshooting sequence starts with entering privileged EXEC mode (step A) because 'show' and 'configure' commands require it. Next, use the 'show interfaces' command (step B) to check for CRC errors and duplex mismatch on the interface. Then, enter global configuration mode (step D) to access interface configuration. Finally, configure the interface with the 'duplex full' command (step C) to fix the mismatch. Placing step C before step D would be invalid because you must be in global configuration mode before you can configure an interface.

Question 4

Drag and drop the following steps into the correct order to configure an IPv4 address on a Cisco IOS-XE router interface, then verify the configuration with a ping to a host that uses an IPv6 EUI-64 address.

Accepted Answer

Enter global configuration mode, enter interface configuration mode, assign IPv4 address, exit to enable mode, ping IPv6 host. Although the order in option A is the required sequence for configuring an IPv4 address, the final step of pinging an IPv6 EUI-64 address does not verify that the IPv4 configuration is working. The router would need IPv6 explicitly configured and the ping command would need to specify IPv6. Therefore, the marked answer is not correct as written.

Answer

Enter interface configuration mode, assign IPv4 address, enter global configuration mode, exit to enable mode, ping IPv6 host

Answer

Enter global configuration mode, assign IPv4 address, enter interface configuration mode, exit to enable mode, ping IPv6 host

Answer

Enter global configuration mode, enter interface configuration mode, assign IPv4 address, ping IPv6 host, exit to enable mode

Question 5

Drag and drop the following steps into the correct order to configure an IPv4 static address on a Windows host, generate an IPv6 EUI-64 address on a Cisco router, verify the router's IPv6 EUI-64 address, and confirm connectivity from the Windows host.

Accepted Answer

Set static IPv4 address on Windows host. The correct order is: first set a static IPv4 address on the Windows host to establish its network settings, then configure the IPv6 EUI-64 address on the Cisco router to enable IPv6, then verify the generated EUI-64 address on the router to ensure correct configuration, and finally confirm connectivity from the Windows host to the router to validate end-to-end communication. This sequence logically progresses from configuration to verification to testing.

Question 6

Drag and drop the steps into the correct order to generate an IPv6 EUI-64 address from a MAC address.

Accepted Answer

Obtain the MAC address of the host interface.. The process to generate an IPv6 EUI-64 address from a MAC address is: first, obtain the MAC address of the host interface. Then, flip the U/L bit (7th bit) of the first byte and insert FFFE between the OUI and NIC portions. These two steps may be performed in either order; they do not affect each other. Finally, combine the resulting 64-bit interface identifier with the IPv6 prefix (e.g., FE80::/10 for link-local) to form the full IPv6 address.

Question 7

Drag and drop the following steps into the correct order to configure an IPv4 static address on a Windows host, generate an IPv6 EUI-64 address on a Cisco router, and verify the static IP assignment on Windows.

Accepted Answer

Configure static IPv4 address on Windows → Generate IPv6 EUI-64 address on router → Verify static IP on Windows. Configuring a static IPv4 address on Windows and generating an IPv6 EUI-64 address on a Cisco router are independent tasks with no dependency between them. Verification of the Windows static IP only requires that the Windows configuration has been completed before verification. Therefore, any order that places the Windows configuration before verification is acceptable. Both A (Windows → Router → Verify) and B (Router → Windows → Verify) satisfy this condition. The original explanation's claim that 'host tasks should precede router tasks' is not a technical requirement.

Answer

Configure static IPv4 address on Windows → Verify static IP on Windows → Generate IPv6 EUI-64 address on router

Answer

Generate IPv6 EUI-64 address on router → Verify static IP on Windows → Configure static IPv4 address on Windows

Question 8

Drag and drop the IPv6 address types on the left to their corresponding scope and prefix on the right.

Accepted Answer

Global Unicast: 2000::/3, Internet scope. The correct matches are as follows: Global Unicast has prefix 2000::/3 and Internet scope (Option A). Link-Local has prefix FE80::/10 and link-local scope, automatically assigned (Option B). Unique Local has prefix FC00::/7 and unique local scope, private and not routable on the Internet (Option C). Multicast has prefix FF00::/8 and multicast scope, used for one-to-many communication (Option D). All four options are correctly paired. Note that the scope for multicast is defined within the prefix, but the description is accurate.

Answer

FE80::/10; link-local scope, automatically assigned on each interface

Answer

FC00::/7; unique local scope, private, not routable on the Internet

Answer

FF00::/8; multicast scope, one-to-many communication

Question 9

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 10

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 11

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 12

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 13

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 14

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 15

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.