CCNA Practice Exam 58 — 20 Questions

Question 1

You are troubleshooting a wireless client connectivity issue on the Cisco WLC at 192.168.1.100. The client reports it can see the SSID 'CorpNet' and successfully associates, but cannot obtain an IP address or reach network resources. The WLAN is already configured with WPA3 security, and the SSID should remain hidden. Identify and correct the configuration issue.

Accepted Answer

The WLAN is mapped to the management interface. Use 'config wlan interface 1 CorpNet_VLAN' to assign the correct interface.. The WLAN is incorrectly mapped to the management interface, which places client traffic in the management VLAN instead of the correct CorpNet_VLAN. As a result, clients cannot obtain IP addresses or communicate beyond the WLC. Reassigning the WLAN to the CorpNet_VLAN interface with 'config wlan interface 1 CorpNet_VLAN' resolves the issue by placing client data in the proper VLAN.

Answer

The SSID is not hidden. Use 'config wlan disable-broadcast-ssid 1 enable' to hide the SSID.

Answer

WPA3 is not enabled on the WLAN. Use 'config wlan security wpa akm 6 enable' to enable WPA3.

Answer

The WLAN is disabled. Use 'config wlan enable 1' to enable the WLAN.

Question 2

You are troubleshooting a wireless client association failure on a Cisco WLC. The client is unable to connect to the corporate SSID 'CorpNet' and reports an authentication error. Review the WLC configuration and fix the issue so that the client can associate and obtain an IP address from VLAN 100. The WLC management IP is 192.168.1.10/24.

Accepted Answer

Change the WLAN security to WPA2, enable SSID broadcast, and configure the WLAN interface to use VLAN 100 with a DHCP scope on that VLAN.. The client authentication and DHCP issues are caused by: (1) WPA3 being configured while the client only supports WPA2, (2) SSID broadcast disabled, preventing client discovery, and (3) the WLAN's client VLAN (100) lacking a DHCP server or scope. The management interface VLAN (1) does not interfere with client DHCP. To resolve, change security to WPA2, enable SSID broadcast, and ensure the WLAN is associated with the correct VLAN (100) and a DHCP scope exists on that VLAN.

Answer

Change the WLAN security to WPA3 only, enable SSID broadcast, and change the management interface IP to 192.168.100.10/24.

Answer

Keep WPA3, disable SSID broadcast for security, and configure the WLAN interface to use VLAN 100 with a DHCP scope on VLAN 1.

Answer

Change the WLAN security to WPA2, keep SSID broadcast disabled, and configure the WLAN interface to use VLAN 1.

Question 3

You are troubleshooting a wireless client association failure on a Cisco WLC. A client reports it can see the SSID 'GuestNet' but fails to connect, while another client using the same SSID connects fine. You must check the WLC configuration, identify the cause, and fix it so that both clients can associate successfully.

Accepted Answer

Enable WPA3 Transition Mode and set PMF to Optional.. The client that cannot associate is likely a legacy client that does not support WPA3. The WLAN 'GuestNet' has WPA3 enabled with 'PMF Required', which forces all clients to support WPA3 and PMF. To fix this, enable WPA3 Transition Mode (which allows both WPA2 and WPA3 clients) and set PMF to Optional. This will allow the older client to associate using WPA2 while newer clients can use WPA3.

Answer

Change the WLAN security to WPA2-PSK only and disable PMF.

Answer

Disable PMF on the WLAN and keep WPA3 enabled.

Answer

Change the WLAN to use WPA2-PSK with PMF Required.

Question 4

You are connected to the console of switch SW1. A user on VLAN 10 reports they cannot reach the internet (203.0.113.1). The switch is configured as a Layer 3 switch with SVIs. Identify and correct the misconfiguration that prevents the user's default gateway from functioning. The user's PC has IP address 192.168.10.50/24 and uses 192.168.10.1 as its default gateway.

Accepted Answer

The SVI for VLAN 10 has 'no ip proxy-arp' configured, and there is no default route on the switch.. The switch's SVI for VLAN 10 has the correct IP address (192.168.10.1) and will always respond to ARP requests for that address regardless of the proxy‑arp setting. The real problem is the absence of a default route, so the switch cannot forward traffic destined for the Internet (203.0.113.1). Option A correctly points to the missing default route as the root cause; the 'no ip proxy-arp' line is present but irrelevant to the SVI's own ARP behavior. The solution is to configure a default route toward the next‑hop router (198.51.100.1).

Answer

The SVI for VLAN 10 has the wrong IP address configured; it should be 192.168.10.254 instead of 192.168.10.1.

Answer

The switch has a default route pointing to 203.0.113.1, but the SVI for VLAN 10 is missing the 'ip helper-address' command.

Answer

The VLAN 10 interface is administratively down, and the switch needs to be reloaded to apply the configuration.

Question 5

You are troubleshooting a client connectivity issue on PC1, which is connected to switch SW1. PC1 reports that it cannot access the internet, but it can ping its default gateway (192.168.1.1). The network uses VLAN 10 for the client subnet. Examine the following show outputs: On PC1, ipconfig shows IP 192.168.1.10, default gateway 192.168.1.1, DNS server 192.168.1.1. On SW1, show running-config includes 'interface Vlan10' with IP 192.168.1.1 255.255.255.0, but no 'ip dns server' and no 'ip name-server' commands. SW1's show ip route displays a default route via 203.0.113.1. Identify the root cause. Configure the necessary fix on the appropriate device to restore full connectivity.

Accepted Answer

Configure 'ip dns server' and 'ip name-server 8.8.8.8' on SW1.. PC1 is configured with DNS server 192.168.1.1, which is the switch SW1. However, SW1 lacks DNS forwarding capability. To enable DNS relay on the switch, both the 'ip dns server' command (to activate the DNS forwarder) and 'ip name-server 8.8.8.8' (to point to an upstream resolver) are required. Option A provides the necessary configuration to restore DNS resolution and internet connectivity.

Answer

Configure 'ip default-gateway 192.168.1.1' on SW1.

Answer

Configure 'ip route 0.0.0.0 0.0.0.0 203.0.113.1' on SW1.

Answer

Configure 'ip domain-lookup' on SW1.

Question 6

You are troubleshooting a connectivity issue for a remote worker who reports being unable to access the internet. The worker's PC is connected to switch S1, which is connected to router R1. You have console access to R1. The router's interface G0/0 is configured with IP 192.168.1.1/24, and the DHCP pool 'LAN' currently has network 192.168.1.0 255.255.255.0 and default-router 192.168.1.254. The PC has obtained an IP address of 192.168.1.100 from DHCP and a subnet mask of 255.255.255.0, but cannot ping 8.8.8.8. Identify the fault and configure R1 to restore internet access for the PC.

Accepted Answer

Change the default-router in the DHCP pool 'LAN' to 192.168.1.1. The PC received a valid IP address from DHCP, proving the DHCP server is reachable and the network statement is correct. However, the pool’s default-router is set to 192.168.1.254, while the actual interface IP (the real gateway) is 192.168.1.1. The PC therefore uses an incorrect default gateway, blocking internet access. Changing the default-router to 192.168.1.1 fixes the gateway mismatch. Option B is wrong because the network statement already matches the subnet. Option C is unnecessary since no helper address is needed for a DHCP server on the same subnet. Option D would change the router’s IP to 192.168.1.254, creating further misalignment and breaking connectivity.

Answer

Change the network statement in the DHCP pool 'LAN' to 192.168.1.0 255.255.255.0

Answer

Add the command 'ip helper-address 192.168.1.254' on interface G0/0

Answer

Change the IP address of interface G0/0 to 192.168.1.254/24

Question 7

You are troubleshooting connectivity for a wireless client connected to the home network shown below. The client has obtained an APIPA address (169.254.x.x), indicating DHCP failure. Verify the DHCP server configuration on R1 and correct the issue so that the client receives a valid IP address from the 192.168.1.0/24 subnet.

Accepted Answer

Enable the DHCP service globally using the 'service dhcp' command on R1.. The client obtained an APIPA address (169.254.x.x) because DHCP was not assigning addresses. The DHCP pool is correctly configured, but the global DHCP service must be enabled with the 'service dhcp' command on R1. The excluded-address range (192.168.1.1–192.168.1.10) uses only a small fraction of the /24 subnet, so it is not the issue. Enabling 'service dhcp' allows the router to process DHCP requests and assign addresses from the pool.

Answer

Remove the 'ip dhcp excluded-address 192.168.1.1 192.168.1.10' command because it excludes too many addresses.

Answer

Change the DHCP pool network to 192.168.1.0/24 and add the default-router 192.168.1.1 command.

Answer

Configure the 'ip helper-address' command on the client's VLAN interface to forward DHCP requests to the server.

Question 8

You are troubleshooting a PC (PC-A) connected to switch SW1, which is connected to router R1. PC-A has an APIPA address (169.254.23.45) and cannot reach the internet (203.0.113.1). You confirm that R1 has a correctly configured DHCP pool for the 192.168.10.0/24 subnet, but the DHCP service is not enabled. The network uses VLAN 10 with subnet 192.168.10.0/24. Verify and correct the configuration on PC-A, SW1, and R1 to restore full connectivity.

Accepted Answer

Enable the DHCP service on R1 with the 'service dhcp' command.. The APIPA address (169.254.x.x) indicates that PC-A failed to obtain a DHCP lease. The correct solution is to enable the DHCP service on R1 with 'service dhcp', which is not running despite the configured pool. Option B is incorrect because setting a default gateway on PC-A with a static IP would still require a valid address in the subnet; the APIPA address cannot communicate with 192.168.10.1. Option C is wrong because the PC-A interface on SW1 is correctly assigned to VLAN 10. Option D is unnecessary since R1 is directly connected to the same subnet, so 'ip helper-address' is only used to forward DHCP broadcasts across router boundaries.

Answer

Configure a default gateway on PC-A with the IP address 192.168.10.1.

Answer

Change the VLAN on SW1's interface connected to PC-A from VLAN 10 to VLAN 1.

Answer

Add the 'ip helper-address' command on R1's interface connected to SW1.

Question 9

You are connected to R1 via the console. The network administrator reports that PC1 (connected to R1's GigabitEthernet0/1) cannot reach the internet. Troubleshoot the issue step by step. The current configuration and show outputs are provided.

Accepted Answer

routing or NAT issue beyond the local network. The issue is that PC1 cannot reach the internet despite having correct IP, gateway, and DNS. PC1 can ping the default gateway and even the next-hop router (203.0.113.2), but fails to ping 8.8.8.8. This indicates that the problem is beyond the local network — likely a routing or NAT issue on the ISP side. However, the task requires troubleshooting client connectivity; the provided outputs show no misconfiguration on PC1 or R1. The fault is external (ISP not routing or no NAT), but the candidate must verify that client configuration is correct and then escalate or check the ISP link. For the PBQ, the candidate should confirm that PC1's IP, subnet mask, gateway, and DNS are correct, and that R1 has a default route and can reach the next hop. No configuration changes are needed on R1 or PC1; the problem is outside the scope of the local network.

Answer

PC1 has an incorrect default gateway configured.

Answer

R1 is missing a default route to the ISP.

Answer

PC1 has a DNS resolution issue.

Question 10

You are troubleshooting a PC connected to switch SW1. The PC cannot access the internet. SW1 is connected to router R1 via port G0/1. R1 provides default gateway and DHCP services. Analyze the provided show output and fix the connectivity issue so that the PC can ping 8.8.8.8. === Show output from R1 ===

R1# show ip interface brief
Interface             IP-Address      OK? Method Status                Protocol
GigabitEthernet0/0    unassigned      YES manual administratively down down
GigabitEthernet0/1    10.0.0.1        YES NVRAM  up                    up

=== Show output from PC ===

C:\> ipconfig
Ethernet adapter Ethernet0:
   Connection-specific DNS Suffix  . :
   IPv4 Address. . . . . . . . . . : 169.254.123.45
   Subnet Mask . . . . . . . . . . : 255.255.0.0
   Default Gateway . . . . . . . . :

=== Show output from SW1 ===

SW1# show vlan brief
VLAN Name                             Status    Ports
---- -------------------------------- --------- -------------------------------
1    default                          active    Gi0/1, Gi0/2, Gi0/3

Accepted Answer

Configure R1's interface G0/0 with IP address 192.168.1.1/24 and ensure the interface is not administratively down.. The PC's APIPA address (169.254.x.x) indicates DHCP failure. The router's DHCP pool is correctly configured and has a lease, but the show output reveals that R1's interface G0/0 is administratively down and has no IP address. Without a working IP on G0/0, the router cannot serve DHCP or route traffic for VLAN 1, even though both the PC and the router are in the same VLAN. Option A fixes the root cause by assigning the correct subnet IP and bringing the interface up. Option B is incorrect because moving the PC to a different VLAN or creating subinterfaces does nothing to enable the router's physical interface where DHCP and routing must run. Option C is wrong because DHCP snooping or trust configurations are irrelevant when the router's own interface is down/unaddressed. Option D is a workaround that only masks the problem; the scenario requires a working DHCP service, and a static IP would not restore the intended design.

Answer

Change the VLAN on SW1's port G0/2 to VLAN 10 and configure R1's subinterface G0/0.10 with IP 192.168.1.1/24.

Answer

Enable DHCP snooping on SW1 and configure the port G0/2 as a trusted port.

Answer

Configure a static IP address of 192.168.1.10/24 on the PC with default gateway 192.168.1.1.

Question 11

You are troubleshooting connectivity between R1 and R2. R1's GigabitEthernet0/0 interface is configured with a static IP of 10.0.0.1/30 but cannot ping its neighbor R2 at 10.0.0.2/30. R1 is using a 1000BASE-T SFP module to connect to a 1000BASE-LX/LH SFP on R2, but the link is down. Diagnose and resolve the issue by adjusting interface speed and duplex settings, and ensure the correct SFP is used for the 2 km fiber run.

Accepted Answer

Replace the 1000BASE-T SFP with a 1000BASE-LX/LH SFP, then on R1 configure 'no negotiation auto', 'speed 1000', and 'duplex full'.. The link is down because auto-negotiation is enabled on R1's SFP port (which uses a 1000BASE-T SFP) while R2's port uses a 1000BASE-LX/LH SFP. Auto-negotiation must be disabled on both sides for fiber SFPs. Additionally, the 1000BASE-T SFP is for copper twisted-pair and cannot connect to a fiber SFP; it must be replaced with a 1000BASE-LX/LH SFP to match the 2 km distance. Commands to fix: on R1, 'no negotiation auto' disables auto-negotiation; 'speed 1000' and 'duplex full' set the correct parameters; then the SFP must be physically replaced with a 1000BASE-LX/LH module.

Answer

Keep the 1000BASE-T SFP and configure 'no negotiation auto', 'speed 1000', and 'duplex full' on R1.

Answer

Replace the 1000BASE-T SFP with a 1000BASE-LX/LH SFP, then configure 'speed 1000' and 'duplex full' on R1 without disabling auto-negotiation.

Answer

Replace the 1000BASE-T SFP with a 1000BASE-LX/LH SFP, then configure 'no negotiation auto' on R1 without setting speed and duplex.

Question 12

You are connected to R1 via the console. R1 and R2 are connected via a fiber link using SFPs. The link is not coming up. Configure the correct SFP type on R1's interface GigabitEthernet0/0 to support the required 2 km distance, and fix any auto-negotiation or speed/duplex misconfiguration so that the link becomes operational.

Accepted Answer

Replace SFP with 1000BASE-LX, configure 'no negotiation auto' on GigabitEthernet0/0, and remove 'speed 1000' and 'duplex full'.. The current SFP is 1000BASE-SX (850 nm), rated for only 550 m, which is insufficient for a 2 km link. It must be replaced with a 1000BASE-LX SFP that supports up to 10 km. The interface currently has 'speed 1000', 'duplex full', and 'negotiation auto'. On fiber SFPs, auto-negotiation is not supported and the speed and duplex are fixed at 1000 Mbps full duplex; therefore, 'no negotiation auto' is required, and any manually configured speed/duplex that violates the SFP's capabilities will prevent the link from coming up. Option A correctly uses 1000BASE-LX, disables auto-negotiation, and removes the redundant speed/duplex commands (the defaults are sufficient). Option D incorrectly sets 'speed 100', which is incompatible with the 1000BASE-LX SFP, causing the link to fail. Option B uses the wrong SFP type (1000BASE-SX). Option C uses the correct SFP but leaves 'negotiation auto', which is unsupported on fiber SFPs and will keep the link down.

Answer

Replace SFP with 1000BASE-SX, configure 'negotiation auto' on GigabitEthernet0/0, and keep 'speed 1000' and 'duplex full'.

Answer

Replace SFP with 1000BASE-LX, configure 'negotiation auto' on GigabitEthernet0/0, and keep 'speed 1000' and 'duplex full'.

Answer

Replace SFP with 1000BASE-LX, configure 'no negotiation auto' on GigabitEthernet0/0, and configure 'speed 100' and 'duplex full'.

Question 13

You are connected to R1. The network has three departments: Sales (VLAN 10, 192.168.1.0/24), Engineering (VLAN 20, 192.168.2.0/24), and Management (VLAN 99, 192.168.99.0/24). A single switch SW1 connects to R1 via trunk interface G0/0. Subinterfaces for VLANs 10, 20, and 99 are already configured on R1 with correct encapsulation and IP addresses. However, inter-VLAN communication is failing. Troubleshoot and fix the configuration issue on R1 to enable routing between all VLANs.

Accepted Answer

Enable 'ip routing' globally on R1.. The router has correctly configured subinterfaces with 802.1Q encapsulation and IP addresses for VLANs 10, 20, and 99. However, 'ip routing' is disabled globally, so the router cannot forward packets between subinterfaces. Additionally, the native VLAN on the trunk is VLAN 1, but no subinterface for VLAN 1 is configured, and the native VLAN mismatch could cause issues; however, the main problem is the lack of IP routing. Enable 'ip routing' globally and optionally configure a subinterface for the native VLAN if needed. The solution requires only 'ip routing' to enable inter-VLAN routing.

Answer

Configure a subinterface for VLAN 1 and assign it an IP address.

Answer

Change the encapsulation on the subinterfaces from dot1Q to ISL.

Answer

Add a static route on R1 pointing to each VLAN subnet.

Question 14

You are connected to R1. The network consists of R1, a router, and SW1, a Layer 2 switch. VLANs 10 (192.168.10.0/24) and 20 (192.168.20.0/24) are configured on SW1 with hosts in each VLAN. R1 must perform inter-VLAN routing using a router-on-a-stick configuration on interface G0/0. Currently, hosts in VLAN 10 cannot ping hosts in VLAN 20. Configure R1 and identify and resolve the issue.

Accepted Answer

Enable IP routing on R1 with the 'ip routing' global configuration command.. The problem is that R1 is missing the 'ip routing' command, which is required to enable IP routing on a router. Without it, R1 cannot forward packets between the subinterfaces. Additionally, the trunk between R1 and SW1 may not be operational because R1's physical interface G0/0 has no IP address and is not set to trunk mode (though subinterfaces handle encapsulation). The solution is to enable IP routing globally and ensure the physical interface is up (no shutdown).

Answer

Configure the physical interface G0/0 with an IP address and enable trunking with 'switchport mode trunk'.

Answer

Ensure the trunk between R1 and SW1 is configured with 'switchport trunk allowed vlan 10,20' on SW1.

Answer

Add the 'no shutdown' command on R1's subinterfaces G0/0.10 and G0/0.20.

Question 15

You are connected to R1 via console. R1 is directly connected to R2 over a 1000BASE-T link that is failing to come up. Configure interface GigabitEthernet0/0 on R1 with the correct speed and duplex settings to match R2's configuration, and then verify the link is operational. Additionally, determine the appropriate SFP type for a new 40 km fiber link between R1 and R2.

Accepted Answer

Configure interface GigabitEthernet0/0 with 'speed 1000' and 'duplex full'. For the new fiber link, use a 1000BASE-ZX SFP.. The link is down because R1 is set to auto-negotiate speed and duplex while R2 is hardcoded to 1000 Mbps full duplex. This mismatch causes the link to fail. To fix, configure R1's GigabitEthernet0/0 with 'speed 1000' and 'duplex full'. For the new 40 km fiber link, a 1000BASE-ZX SFP is required as it supports distances up to 70 km. (1000BASE-LX supports only up to 10 km and is insufficient for 40 km.) Verify with 'show interfaces GigabitEthernet0/0' to see the link state change to up/up.

Answer

Configure interface GigabitEthernet0/0 with 'speed auto' and 'duplex auto'. For the new fiber link, use a 1000BASE-SX SFP.

Answer

Configure interface GigabitEthernet0/0 with 'speed 1000' and 'duplex half'. For the new fiber link, use a 1000BASE-LX SFP.

Answer

Configure interface GigabitEthernet0/0 with 'speed 100' and 'duplex full'. For the new fiber link, use a 1000BASE-EX SFP.

Question 16

You are connected to R1. The link between R1's GigabitEthernet0/0 and R2's GigabitEthernet0/0 should operate at 1 Gbps full duplex, but the interface is showing errors and only negotiating at 100 Mbps half duplex. Diagnose and fix the fault, then verify the link is stable at the correct speed and duplex.

Accepted Answer

Remove the manual speed and duplex settings on R1's GigabitEthernet0/0 with 'no speed' and 'no duplex' to allow auto-negotiation.. The interface was manually configured with 'duplex half' and 'speed 100', which forced the link to 100 Mbps half duplex, causing CRC errors due to duplex mismatch. The correct fix is to remove these manual settings and allow auto-negotiation, or explicitly set both sides to 'speed 1000' and 'duplex full'. Since the remote side (R2) is set to auto (default), the simplest correction is to use 'no duplex' and 'no speed' on R1 to re-enable auto-negotiation. After the commands are applied, the interface should show 'Full-duplex, 1000Mb/s' and CRC errors should stop incrementing.

Answer

Change the duplex setting to 'full' and speed to '1000' on R1's GigabitEthernet0/0.

Answer

Replace the cable between R1 and R2 with a crossover cable.

Answer

Configure R2's GigabitEthernet0/0 with 'speed 100' and 'duplex half' to match R1's settings.

Question 17

You are connected to R1. Configure inter-VLAN routing on R1 using router-on-a-stick so that hosts in VLAN 10 (192.168.10.0/24) and VLAN 20 (192.168.20.0/24) can communicate. The switch SW1 is already configured with VLANs and trunking, but R1's current configuration prevents traffic. Identify and fix the issues.

Accepted Answer

Enable the physical interface with the 'no shutdown' command on R1.. The issue was that the physical interface GigabitEthernet0/0 on R1 was administratively down, causing all subinterfaces for VLANs 10 and 20 to be in a down state. Enabling it with 'no shutdown' brings the trunk up, allowing inter-VLAN routing because the switch already has trunking configured. The other options are incorrect because they suggest steps that are either already in place (IP routing) or not needed (changing encapsulation or moving no shutdown to subinterfaces).

Answer

Change the encapsulation on the subinterfaces to use dot1Q with native VLAN 10 and 20 respectively.

Answer

Enable IP routing globally with the 'ip routing' command on R1.

Answer

Remove the 'no shutdown' from the subinterfaces and apply it only to the physical interface.

Question 18

You are connected to R1. The network consists of R1, SW1, and two VLANs (10 and 20). SW1 has hosts in VLAN 10 and VLAN 20 connected to its access ports. Configure R1 for router-on-a-stick inter-VLAN routing using subinterfaces on G0/0. The physical interface G0/0 is administratively up (no shutdown). The current configuration is incomplete and has errors preventing communication between the VLANs. Fix the configuration so that hosts in VLAN 10 (192.168.10.0/24) and VLAN 20 (192.168.20.0/24) can ping each other through R1.

Accepted Answer

Enable IP routing with the 'ip routing' global configuration command.. The primary fault is that IP routing is disabled globally on R1 (missing 'ip routing' command), so even though subinterfaces are correctly configured, the router cannot route between VLANs. The physical interface G0/0 is already administratively up, so issuing 'no shutdown' would not fix the problem. Thus, enabling 'ip routing' resolves the inter-VLAN communication issue. The other options either incorrectly swap encapsulation or address a native VLAN scenario not indicated in the exhibit.

Answer

Change the encapsulation on subinterface G0/0.10 to dot1Q 20 and on G0/0.20 to dot1Q 10.

Answer

Add the 'no shutdown' command on the physical interface G0/0.

Answer

Configure the native VLAN on the trunk to match the subinterface for VLAN 1.

Question 19

You are connected to R1. Configure router-on-a-stick inter-VLAN routing so that hosts in VLAN 10 and VLAN 20 can communicate through R1. The switch (not shown) is already configured with the correct VLANs and trunk. Troubleshoot and fix any issues in the current R1 configuration.

Accepted Answer

Enable IP routing globally and bring up the main interface GigabitEthernet0/0 with 'no shutdown'.. The R1 configuration has two subinterfaces (G0/0.10 and G0/0.20) with correct VLAN encapsulation and IP addresses, but inter-VLAN routing fails because the main interface G0/0 is not configured as a trunk (no 'no shutdown' and no 'ip routing' globally). Enable IP routing globally with 'ip routing' and ensure GigabitEthernet0/0 is administratively up with 'no shutdown'. The subinterfaces will then route between VLANs.

Answer

Change the encapsulation on the subinterfaces to 'encapsulation dot1Q 10 native' and 'encapsulation dot1Q 20 native'.

Answer

Remove the subinterfaces and configure IP addresses directly on GigabitEthernet0/0.

Answer

Add 'ip routing' on each subinterface individually.

Question 20

You are connected to a multilayer switch SW1 via console. SW1 has an IP phone and an access point connected to interfaces GigabitEthernet0/1 and GigabitEthernet0/2 respectively. Configure the access ports so that the IP phone receives a voice VLAN (VLAN 110) and PoE priority critical, and the access point receives PoE priority high. Verify your configuration using show interfaces switchport and show power inline.

Accepted Answer

interface GigabitEthernet0/1
 switchport mode access
 switchport access vlan 10
 switchport voice vlan 110
 power inline priority critical
!
interface GigabitEthernet0/2
 switchport mode access
 power inline priority high. The IP phone requires a voice VLAN configured with the switchport voice vlan command. PoE priority is set per interface using power inline priority. For the phone, the priority is critical; for the AP, it is high. Verification with show interfaces switchport confirms voice VLAN, and show power inline shows priority settings.

Answer

interface GigabitEthernet0/1
 switchport mode trunk
 switchport trunk allowed vlan 10,110
 power inline priority critical
!
interface GigabitEthernet0/2
 switchport mode access
 power inline priority high

Answer

interface GigabitEthernet0/1
 switchport mode access
 switchport access vlan 110
 switchport voice vlan 10
 power inline priority critical
!
interface GigabitEthernet0/2
 switchport mode access
 power inline priority high

Answer

interface GigabitEthernet0/1
 switchport mode access
 switchport access vlan 10
 switchport voice vlan 110
 power inline priority high
!
interface GigabitEthernet0/2
 switchport mode access
 power inline priority critical

CCNA Practice Exam 58 — 20 Questions

Exhibit

CCNA Practice Exam 58 — 20 Questions

Exhibit