CCNA Network Infrastructure and Connectivity Practice Test 11 — 15 Questions

Question 1

Drag and drop the PDU names on the left to the correct OSI model layers on the right.

Accepted Answer

Application: Message, Transport: Segment, Network: Packet, Data Link: Frame, Physical: Bit, Session: Data. In the OSI model, each layer processes a specific Protocol Data Unit (PDU): Data is the term for application information at Layer 7, a segment is the Transport layer (Layer 4) PDU, a packet belongs to the Network layer (Layer 3), a frame is the Data Link layer (Layer 2) PDU, and bits are transmitted at the Physical layer (Layer 1). This pairing follows the standard OSI terminology without involving other layers.

Answer

Application: Data, Transport: Segment, Network: Packet, Data Link: Frame, Physical: Bit, Session: Message

Answer

Application: Message, Transport: Packet, Network: Segment, Data Link: Frame, Physical: Bit, Session: Data

Answer

Application: Data, Transport: Segment, Network: Packet, Data Link: Frame, Physical: Bit, Session: Message

Question 2

A network administrator notices that a workstation connected to a Cisco switch port cannot communicate with other devices on the same VLAN. The switch port is up/up, but the workstation reports slow performance and intermittent connectivity. What is the most likely cause of this issue?

Accepted Answer

A duplex mismatch between the switch port and the workstation.. A duplex mismatch occurs when one end of the link is set to full-duplex and the other to half-duplex. The half-duplex end detects collisions and the full-duplex end does not, causing late collisions, CRC errors, and retransmissions. This results in slow performance and intermittent connectivity even though the port is operationally up.

Answer

Replace the faulty Ethernet cable between the switch and the workstation.

Answer

Assign the switch port to the correct VLAN.

Answer

Disable spanning-tree on the port to prevent frequent topology changes.

Question 3

A network technician is troubleshooting connectivity between two directly connected Cisco switches. Hosts on VLAN 10 connected to SwitchA cannot ping the default gateway on SwitchB. The interface on SwitchB shows up/up, but the interface on SwitchA shows up/down. The technician examines the interface configuration and status on SwitchA. What is the most likely cause of this issue?

Accepted Answer

Configure both interfaces with the same duplex and speed settings, either both auto or both manually set to full-duplex and 1000 Mbps.. The interface on SwitchA shows up/down, meaning Layer 1 is active but the line protocol is down. This is commonly caused by a speed mismatch between the two ends. A duplex mismatch, in contrast, typically results in both interfaces showing up/up with CRC errors. Therefore, the most likely cause is that the speed settings differ—for example, one interface is set to auto-negotiate while the other is hard-coded to a specific speed. Configuring both interfaces with identical speed and duplex settings, either both auto or both manually configured, resolves the issue.

Answer

Replace the Ethernet cable because it is faulty.

Answer

Issue the 'shutdown' and 'no shutdown' commands on the interface to recover from err-disabled state.

Answer

Check the VLAN configuration on SwitchA because the interface is administratively down.

Question 4

A network administrator is troubleshooting connectivity issues between two switches. Hosts connected to Switch A cannot ping hosts on Switch B. The link between the switches shows as up/up on both ends, but interface error counters (CRC, runts) are increasing rapidly. What should the administrator do to resolve the issue?

Accepted Answer

Change the duplex setting on SwitchA's interface to auto-negotiation.. The increasing CRC and runts errors on an up/up link indicate a duplex mismatch, where one side is using full duplex and the other half duplex. Assuming SwitchB is using auto-negotiation (the default on Cisco switches), changing SwitchA's interface to auto-negotiation will allow both ends to negotiate the correct duplex setting, resolving the mismatch and stopping the errors.

Answer

Replace the faulty cable between the two switches.

Answer

Replace the SFP module on SwitchA's GigabitEthernet0/1 port.

Answer

Enable the interface with 'no shutdown' command.

Question 5

A network administrator is troubleshooting connectivity between two directly connected Cisco switches. Hosts on VLAN 10 connected to Switch A cannot ping the default gateway on Switch B. The interface on Switch A shows 'up/up' but there are excessive CRC errors and runts. The administrator checks the interface configuration on both switches. What is the most likely cause of the issue?

Accepted Answer

Mismatched duplex and speed settings between the interfaces.. The presence of excessive CRC errors and runts on an interface that is 'up/up' strongly indicates a Layer 1 or Layer 2 duplex mismatch. When one switch is set to full-duplex and the other to half-duplex (or auto-negotiation fails), the half-duplex side will detect collisions and retransmit, while the full-duplex side will not, leading to frame corruption (CRC errors) and truncated frames (runts). Configuring both interfaces with the same duplex and speed settings (e.g., full-duplex and 1000 Mbps) resolves this mismatch, restoring proper connectivity for VLAN 10 traffic to the default gateway.

Answer

Replace the faulty Ethernet cable.

Answer

Disable spanning tree on both interfaces to prevent loop prevention from blocking traffic.

Answer

Assign the interfaces to the same VLAN to ensure Layer 2 connectivity.

Question 6

A network technician is troubleshooting a connectivity issue between two directly connected switches, SW1 and SW2. Hosts on VLAN 10 connected to SW1 can ping each other but cannot ping the default gateway or any host on VLAN 10 connected to SW2. The interface on SW1 is up/up, but the interface on SW2 is up/down. What is the most likely cause of the problem?

Accepted Answer

Ensure both switches are configured for the same duplex setting, preferably by enabling autonegotiation on both interfaces.. The interface on SW2 is up/down, which typically indicates a Layer 1 issue such as a duplex mismatch. Duplex mismatch occurs when one switch is manually set to full duplex and the other to half duplex or auto-negotiation fails, causing the side expecting full duplex to report up/down due to excessive errors. Option A is incorrect because MTU mismatch would cause connectivity issues but not an up/down interface state. Option C is incorrect because a faulty cable would likely cause both interfaces to be down/down, not up/down. Option D is incorrect because late collisions are a symptom of duplex mismatch, not a separate cause; increasing collision window size is not a standard troubleshooting step. The correct solution is to ensure both switches use the same duplex setting, preferably via autonegotiation (IEEE 802.3u).

Answer

Configure the interface on SW2 to use a different MTU value.

Answer

Replace the Ethernet cable connecting SW1 and SW2.

Answer

Check for late collisions on the interface and increase the collision window size.

Question 7

Which TWO interface issues can be identified by analyzing the output of the 'show interfaces' command?

Accepted Answer

Duplex mismatch. The 'show interfaces' command displays interface statistics and operational status, including duplex and speed settings. A duplex mismatch occurs when one end of a link is set to full-duplex and the other to half-duplex, leading to collisions and CRC errors visible in the output. Speed mismatch is also detectable because the interface will show the negotiated speed or errors like 'input errors' if the speeds do not match.

Answer

Routing protocol misconfiguration

Answer

VLAN mismatch

Answer

STP topology change

Question 8

Which TWO symptoms are most likely to appear in the output of 'show interfaces' when a duplex mismatch exists between a switch port and a connected host?

Accepted Answer

Excessive collisions and CRC errors on the interface. A duplex mismatch causes collisions on the half-duplex side, resulting in excessive collisions and CRC errors (option A). On the full-duplex side, the host receives truncated frames from the half-duplex side's collisions, leading to runts and frame errors (option B). Option C is incorrect because 'Auto-negotiation failed' would appear only if negotiation itself failed, not from a mismatch after successful negotiation. Option D is wrong because a duplex mismatch typically reduces throughput and causes errors, not a high input rate. Option E is incorrect because the line protocol remains up; duplex mismatch does not bring the line protocol down.

Answer

Auto-negotiation failed message in the interface output

Answer

High input rate on the interface

Answer

Line protocol is down

Question 9

A user on VLAN 10 reports that they cannot ping the default gateway at 192.168.10.1 from their PC with IP 192.168.10.50/24. The switch interface connecting to the PC is up/up, and the PC shows a valid IP configuration. What is the most likely cause of this connectivity failure?

Accepted Answer

Configure an SVI for VLAN 10 with an IP address in the 192.168.10.0/24 subnet.. The PC and default gateway are on the same subnet (192.168.10.0/24), but the switch lacks a Layer 3 interface for VLAN 10. Without an SVI (Switch Virtual Interface) configured with an IP address in that subnet, the switch cannot route traffic to the gateway or respond to ARP requests from the PC, breaking connectivity even though the access port is up/up.

Answer

Change the switchport mode to trunk to allow VLAN 10 traffic.

Answer

Change the PC's IP address to a different subnet, such as 192.168.20.0/24.

Answer

Recreate VLAN 10 and reassign the port to it.

Question 10

A network engineer is troubleshooting connectivity issues for hosts in VLAN 10. Hosts in VLAN 10 are unable to ping the default gateway at 192.168.10.1. The engineer checks the switch configuration and notices that the SVI for VLAN 10 is configured with an IP address, but the interface is in a down/down state. What is the most likely cause of this issue?

Accepted Answer

VLAN 10 does not exist in the VLAN database.. An SVI (Switch Virtual Interface) will remain in a down/down state if the corresponding VLAN does not exist in the switch's VLAN database. Even if the SVI is configured with an IP address, the interface cannot come up because there is no Layer 2 VLAN to associate with it. This is a common cause of SVI down/down issues when the VLAN has not been created or has been deleted.

Answer

The interface is administratively shut down.

Answer

The IP address is not in the correct subnet for VLAN 10.

Answer

The switch does not have a default gateway configured.

Question 11

Which TWO statements correctly describe the configuration and verification of IPv4 and IPv6 parameters for host connectivity, including default gateway, DNS, and subnet masks?

Accepted Answer

The default gateway must be on the same subnet as the host's IP address.. Option B is correct because a host's default gateway must be on the same subnet to be reachable at Layer 2; otherwise, a circular dependency occurs. Option D is correct because the 'ipconfig /all' command displays both IPv4 and IPv6 configuration details, including IP address, subnet mask, default gateway, and DNS servers. Option A is wrong because the subnet mask determines the network and host portions of an IP address, not the DNS server address. Option C is wrong because IPv6 hosts can obtain their IP address via SLAAC, DHCPv6, or static configuration; the phrase 'can only' makes it incorrect. Option E is wrong because the default gateway must be reachable (on the same subnet) and configured with an IP address that belongs to a router interface on that subnet, not just any IP address.

Answer

The subnet mask determines the DNS server address used by the host.

Answer

IPv6 hosts can only obtain their IP address via DHCPv6.

Answer

A host can reach any remote network if its default gateway is configured with any IP address.

Question 12

Which TWO statements correctly describe the configuration and verification of IPv4 and IPv6 parameters for host connectivity?

Accepted Answer

On a Windows host, the default gateway IPv4 address must be on the same subnet as the host's IPv4 address.. Option A is correct because for a host to reach outside its subnet, the default gateway's IP must be in the same subnet; otherwise the host cannot ARP for the gateway's MAC and traffic will fail. Option D is correct because DNS server addresses can be set manually or assigned via DHCP. Option B is wrong because IPv6 gateways must be on the same local link, not any global unicast address on the internet. Option C is wrong because the subnet mask defines the network/subnet portion of an IPv4 address, not the host portion. Option E is wrong because DNS is used for name resolution; local IP communication on the same subnet works without DNS.

Answer

The IPv6 default gateway can be any global unicast address on the internet.

Answer

The subnet mask is used to define the host portion of an IPv4 address.

Answer

Configuring a DNS server is mandatory for a host to communicate with any other device on the same subnet.

Question 13

A network administrator is configuring a new Windows workstation on a small office network that uses IPv4 addressing. The workstation must be able to communicate with devices on other subnets and resolve hostnames via a company DNS server at 10.10.10.5. The administrator has already set the IP address to 10.10.10.10 and the subnet mask to 255.255.255.0. Which additional parameter must be configured to meet both requirements?

Accepted Answer

Configure a default gateway of 10.10.10.1 and a DNS server of 10.10.10.5.. To communicate with devices on other subnets, the workstation needs a default gateway (router) to forward traffic beyond its local subnet. The IP address 10.10.10.10 with subnet mask 255.255.255.0 places it in the 10.10.10.0/24 network, so a default gateway (e.g., 10.10.10.1) is required for inter-subnet routing. Additionally, to resolve hostnames, the DNS server address must be explicitly configured; the company DNS server is at 10.10.10.5. Option A correctly provides both parameters.

Answer

Configure only a DNS server of 10.10.10.5.

Answer

Change the subnet mask to 255.255.0.0 to allow communication across subnets.

Answer

Configure a default gateway of 10.10.20.1 and a DNS server of 10.10.10.5.

Question 14

A junior network engineer is configuring a new Windows 10 workstation to connect to the corporate network. The network uses a /24 subnet mask and has a default gateway of 192.168.1.1. The workstation obtains its IP address automatically from a DHCP server, but the engineer needs to manually set a static IPv4 address of 192.168.1.50 and ensure the workstation can reach the internet. Which configuration step must the engineer take to satisfy these requirements?

Accepted Answer

Set the subnet mask to 255.255.255.0 and the default gateway to 192.168.1.1. Option B is correct because a /24 subnet mask (255.255.255.0) matches the network prefix of the default gateway 192.168.1.1, ensuring the workstation can route traffic to the internet via that gateway. Option A fails because a /16 mask (255.255.0.0) does not match the corporate /24 network, causing incorrect network identification and potential routing issues. Option C fails because leaving the default gateway blank means the host cannot reach any network beyond its local subnet, so internet access is impossible. Option D fails because using the host's own IP (192.168.1.50) as the default gateway would cause the host to attempt to route traffic to itself, never reaching the actual gateway.

Answer

Set the subnet mask to 255.255.0.0 and the default gateway to 192.168.1.1

Answer

Set the subnet mask to 255.255.255.0 and leave the default gateway blank

Answer

Set the subnet mask to 255.255.255.0 and the default gateway to 192.168.1.50

Question 15

A network administrator notices that wireless clients are unable to associate with the corporate SSID 'CorpNet' on an AP that is managed by a WLC. The AP has been joined to the WLC successfully, and the WLC is reachable from the AP. The administrator checks the WLC configuration. Based on the exhibit, what is the most likely cause of the association failure?

Accepted Answer

The WLAN is mapped to the management interface.. The exhibit shows the WLAN 'CorpNet' is mapped to the management interface. While the association process may succeed, the management interface is reserved for control and management traffic (e.g., CAPWAP, SSH) and is not designed to carry client data. This misconfiguration prevents the client from obtaining network access (e.g., IP address via DHCP), which manifests as an apparent association failure. Client data must be mapped to a dynamic interface (VLAN) or the guest interface for proper operation.

Answer

The WLAN is disabled.

Answer

The WLAN is missing a pre-shared key.

Answer

CCKM is not supported by the clients.