Cisco CCNA 200-301 v2.0: Network Infrastructure and Connectivity

Try 10 focused Cisco CCNA 200-301 v2.0 questions on Network Infrastructure and Connectivity, with explanations, then continue with IT Mastery.

Open the matching IT Mastery practice page for timed mocks, topic drills, progress tracking, explanations, and full practice.

Try Cisco CCNA 200-301 v2.0 on Web View full Cisco CCNA 200-301 v2.0 practice page

Topic snapshot

FieldDetail
Exam routeCisco CCNA 200-301 v2.0
Topic areaNetwork Infrastructure and Connectivity
Blueprint weight25%
Page purposeFocused sample questions before returning to mixed practice

How to use this topic drill

Use this page to isolate Network Infrastructure and Connectivity for Cisco CCNA 200-301 v2.0. Work through the 10 questions first, then review the explanations and return to mixed practice in IT Mastery.

PassWhat to doWhat to record
First attemptAnswer without checking the explanation first.The fact, rule, calculation, or judgment point that controlled your answer.
ReviewRead the explanation even when you were correct.Why the best answer is stronger than the closest distractor.
RepairRepeat only missed or uncertain items after a short break.The pattern behind misses, not the answer letter.
TransferReturn to mixed practice once the topic feels stable.Whether the same skill holds up when the topic is no longer obvious.

Blueprint context: 25% of the practice outline. A focused topic score can overstate readiness if you recognize the pattern too quickly, so use it as repair work before timed mixed sets.

Sample questions

These questions are original IT Mastery practice items aligned to this topic area. They are designed for self-assessment and are not official exam questions.

Question 1

Topic: Network Infrastructure and Connectivity

A warehouse barcode scanner cannot connect to the Inventory WLAN after the WLAN security profile was updated. Other scanners using the same AP are connected and passing traffic.

Exhibit:

ClueValue
Scanner RSSI-46 dBm
AP channel/noiseChannel 6, normal noise floor
DHCP lease on scannerNone assigned
WLAN securityWPA2-Personal AES/CCMP
Scanner saved profileWPA2-Personal TKIP

Which root cause is best supported by these facts?

Options:

  • A. Wireless encryption mismatch

  • B. DHCP scope exhaustion

  • C. Incorrect AP channel selection

  • D. Weak wireless signal

Best answer: A

Explanation: The key distinction is whether the client is failing at the wireless association/security stage or after joining the WLAN. Here, the scanner sees the SSID with strong signal strength, and the AP channel/noise information does not indicate an RF problem. The decisive clue is the security mismatch: the WLAN requires WPA2-Personal with AES/CCMP, but the scanner profile is saved for WPA2-Personal with TKIP. Because the client cannot complete the required wireless security negotiation, it never reaches the point where DHCP can assign an address. A missing DHCP lease is therefore a symptom, not the root cause.

  • Weak signal is not supported because -46 dBm is a strong received signal for a nearby WLAN client.
  • Channel selection is not supported because the exhibit shows normal noise and other clients on the AP are passing traffic.
  • DHCP exhaustion is premature because the scanner has not successfully joined the secured WLAN.

Question 2

Topic: Network Infrastructure and Connectivity

R1 must use modified EUI-64 to build its IPv6 address on G0/0. Review the output and determine the address that should be derived.

Exhibit:

R1# show running-config interface g0/0
interface GigabitEthernet0/0
 ipv6 address 2001:DB8:10:20::/64 eui-64
 no shutdown

R1# show interfaces g0/0 | include address
  Hardware is iGbE, address is 001a.2b3c.4d5e

Which IPv6 address should R1 derive for G0/0?

Options:

  • A. 2001:DB8:10:20:001A:2BFF:FE3C:4D5E

  • B. 2001:DB8:10:20:021A:2B3C:4D5E:FFFF

  • C. 2001:DB8:10:20:021A:2BFF:FE3C:4D5E

  • D. 2001:DB8:10:20:001A:2B3C:4D5E:0000

Best answer: C

Explanation: Modified EUI-64 builds a 64-bit IPv6 interface identifier from a 48-bit MAC address. The MAC 001a.2b3c.4d5e is split into 001A:2B and 3C:4D5E, FFFE is inserted in the middle, and the universal/local bit in the first octet is inverted. Because the first octet is 00, flipping that bit changes it to 02. The resulting interface identifier is 021A:2BFF:FE3C:4D5E, which is combined with the supplied /64 prefix 2001:DB8:10:20::/64. The key distinction is that EUI-64 is not just padding the MAC; it both inserts FFFE and modifies the first octet.

  • Missing bit flip fails because 001A keeps the original first octet instead of changing 00 to 02.
  • Simple padding fails because modified EUI-64 does not append zeros to the 48-bit MAC.
  • Wrong insertion value fails because the inserted middle value is FFFE, not FFFF.

Question 3

Topic: Network Infrastructure and Connectivity

A small office has three APs that must support older 2.4 GHz-only clients. The AP coverage cells overlap, and users report slow throughput during busy periods. You need a channel plan that reduces wireless interference while keeping client compatibility. Which configuration choice best meets the goal?

Options:

  • A. Use 20 MHz channels 1, 6, and 11

  • B. Place all APs on channel 6

  • C. Use 20 MHz channels 1, 2, and 3

  • D. Use 40 MHz channels in 2.4 GHz

Best answer: A

Explanation: In the 2.4 GHz band, channel selection strongly affects interference and client performance because most channels overlap. For APs with overlapping coverage, using non-overlapping 20 MHz channels reduces adjacent-channel interference and lets clients share airtime more efficiently. In typical 2.4 GHz deployments, channels 1, 6, and 11 are used because their frequency ranges do not overlap when using 20 MHz channel width.

Putting nearby APs on overlapping channels causes them to interfere with each other, increasing retries and reducing throughput. Wider channels in 2.4 GHz also consume more spectrum and usually worsen contention in dense areas.

  • Adjacent channels such as 1, 2, and 3 overlap heavily and increase interference.
  • Same-channel reuse on channel 6 can create co-channel contention between nearby APs.
  • Wider 2.4 GHz channels reduce the number of usable channels and can hurt performance in overlapping cells.

Question 4

Topic: Network Infrastructure and Connectivity

A technician is configuring the management SVI on an IOS XE switch. The management subnet is 172.16.18.64/27, and the router already uses 172.16.18.65 as the default gateway. Which SVI address configuration meets the requirement?

Options:

  • A. ip address 172.16.18.95 255.255.255.224

  • B. ip address 172.16.18.63 255.255.255.224

  • C. ip address 172.16.18.64 255.255.255.224

  • D. ip address 172.16.18.66 255.255.255.224

Best answer: D

Explanation: The mask 255.255.255.224 is /27, which creates block sizes of 32 addresses in the last octet. The subnet that starts at 172.16.18.64 runs through 172.16.18.95. The subnet ID is .64, the broadcast address is .95, and usable host addresses are .65 through .94. Because .65 is already assigned to the router gateway, the SVI needs another usable address in that range. The address .66 is in the correct subnet and is not reserved.

  • Previous subnet fails because .63 is outside the 172.16.18.64/27 subnet.
  • Subnet ID fails because .64 identifies the subnet and cannot be assigned to a host.
  • Broadcast address fails because .95 is the directed broadcast address for this /27 subnet.

Question 5

Topic: Network Infrastructure and Connectivity

A MacBook user reports no Internet access. The Wi-Fi menu shows the client is connected to the Corp-Staff SSID with strong signal, and the user was not prompted again for the wireless password. In macOS Network settings, Wi-Fi shows IP address 169.254.83.10, mask 255.255.0.0, router blank, and DNS blank. Other clients on the same SSID can browse. Which configuration decision is most appropriate?

Options:

  • A. Add only public DNS servers on the MacBook

  • B. Change the SSID security passphrase on the AP

  • C. Set Wi-Fi IPv4 to DHCP and renew the lease

  • D. Troubleshoot the distribution router default route

Best answer: C

Explanation: On macOS, an address in 169.254.0.0/16 is a self-assigned link-local IPv4 address. The client has associated to Wi-Fi, but it does not have a usable DHCP-assigned IP address, default gateway, or DNS settings. Because other clients on the same SSID work, the symptom is most consistent with this MacBook’s IP configuration or DHCP lease state, not wireless security or upstream network reachability. Renewing DHCP or correcting the Wi-Fi TCP/IP setting targets the failing layer directly.

Wireless security problems usually prevent association or authentication, while upstream routing problems would typically affect multiple clients on the SSID.

  • Wireless security change is not supported because the MacBook is already connected to the SSID.
  • DNS-only fix is incomplete because the client also lacks a valid IP address and default gateway.
  • Router troubleshooting is unlikely because other clients on the same SSID can browse successfully.

Question 6

Topic: Network Infrastructure and Connectivity

A warehouse IP camera connected to switch port Gi1/0/18 repeatedly loses connectivity. The same camera works normally when connected with a 3-meter patch cable at the switch. The installed horizontal cable run to the camera is documented as 145 meters of Cat6. The port shows up/up, autonegotiated 1000/full, increasing CRC/input errors, and intermittent DHCP renewals.

What is the best corrective action?

Options:

  • A. Force the switch port to 1000/full duplex

  • B. Change the access VLAN on Gi1/0/18

  • C. Configure a static IP address on the camera

  • D. Shorten the copper run or add an intermediate device

Best answer: D

Explanation: Twisted-pair Ethernet links such as 1000BASE-T are designed for a maximum channel length of about 100 meters. A 145-meter Cat6 run can still show up/up, but the signal margin may be poor enough to create CRC/input errors, link instability, and intermittent upper-layer symptoms such as DHCP renewal failures. Because the camera works with a short patch cable at the same switch, the endpoint and switchport configuration are less likely to be the root problem.

The durable fix is to bring the copper segment within supported distance, place an intermediate switch/extender where appropriate, or use fiber for the longer run.

  • VLAN change is not supported because the same device works at the switch and the main clue is physical-layer errors.
  • Static IP may mask DHCP symptoms but does not fix CRC/input errors caused by signal degradation.
  • Forced duplex is not indicated because the port already negotiated 1000/full, and forcing settings can create new negotiation issues.

Question 7

Topic: Network Infrastructure and Connectivity

A user reports very slow file transfers through access port Gi1/0/12 on SW1. The link does not flap. Based on the interface counters, what should be checked first?

SW1# show interfaces gi1/0/12
GigabitEthernet1/0/12 is up, line protocol is up
  Hardware is Gigabit Ethernet, address is 001b.0c7a.120c
  Half-duplex, 100Mb/s, media type is 10/100/1000BaseTX
  5 minute input rate 42000 bits/sec, 12 packets/sec
  5 minute output rate 38000 bits/sec, 10 packets/sec
     0 input errors, 0 CRC, 0 frame
     1842 output errors, 1765 collisions, 1592 late collisions

Options:

  • A. Copper cabling for excessive CRC errors

  • B. Duplex settings on both ends of the link

  • C. The workstation default gateway configuration

  • D. The switchport VLAN assignment

Best answer: B

Explanation: Late collisions are a strong clue to check duplex first, especially when the interface is up and input CRC/frame errors are not increasing. On modern switched Ethernet, a full-duplex link should not see collisions. If one side operates full duplex and the other side operates half duplex, the half-duplex side may report collisions and late collisions, while users experience poor throughput even though the link remains up. The next check should compare both ends for hardcoded duplex, autonegotiation status, and speed/duplex agreement. Cabling is more likely when CRC, frame, or input errors dominate the evidence.

  • CRC cabling check is tempting, but the exhibit shows zero CRC and frame errors.
  • Default gateway would affect Layer 3 reachability, not create late collisions on the switch interface.
  • VLAN assignment could break connectivity, but it does not explain collision and late-collision counters.

Question 8

Topic: Network Infrastructure and Connectivity

Users in a conference room next to the break room report intermittent wireless drops around lunchtime. Wired clients are unaffected, and users on the 5 GHz SSID remain connected. What is the best interpretation of the evidence?

Exhibit:

AP-12 radio summary
Band: 2.4 GHz    Channel: 6
Noise floor: -62 dBm during 11:55-12:20
Typical noise floor: -92 dBm
Interference: high, non-802.11
Client authentication: success
DHCP renewals: success
Neighbor AP RSSI on channels 1/11: below -80 dBm

Options:

  • A. The SSID has an incorrect security key

  • B. A nearby non-Wi-Fi device is interfering with 2.4 GHz

  • C. A DHCP scope is exhausted for wireless clients

  • D. Neighbor APs are causing strong co-channel interference

Best answer: B

Explanation: The evidence points to RF interference, not an IP addressing or authentication problem. The 2.4 GHz radio shows a much worse noise floor during a specific time window, and the interference is labeled non-802.11. Because 5 GHz clients remain connected and DHCP renewals and authentication are successful, the failure is most likely happening at the wireless RF layer. A common real-world source near a break room is a microwave oven or another non-Wi-Fi device that emits energy in the 2.4 GHz band.

Weak neighboring AP signals on channels 1 and 11 make AP-to-AP interference less likely in this scenario.

  • DHCP exhaustion fails because the exhibit shows DHCP renewals are successful.
  • Wrong security key fails because client authentication succeeds.
  • Co-channel interference is not supported because neighbor AP RSSI is weak and the interference is non-802.11.

Question 9

Topic: Network Infrastructure and Connectivity

A laptop on SW1 access port Fa0/10 in VLAN 20 receives a DHCP address but cannot reach networks outside VLAN 20. Other VLAN 20 hosts using a static default gateway can reach other networks.

Exhibit:

SW1 Fa0/10: access vlan 20, up/up
R1 Gi0/0.20: 192.168.20.1/24, up/up

Laptop DHCP assignment:
IPv4 address:    192.168.20.57
Subnet mask:     255.255.255.0
Default gateway: 192.168.10.1
DHCP server:     192.168.20.1

R1 DHCP pool VLAN20:
 network 192.168.20.0 255.255.255.0
 default-router 192.168.10.1

Which corrective action best addresses the root cause?

Options:

  • A. Set default-router 192.168.20.1 in the VLAN 20 DHCP pool.

  • B. Add ip helper-address to R1 Gi0/0.20.

  • C. Change the VLAN 20 DHCP pool network to 192.168.10.0/24.

  • D. Move SW1 Fa0/10 to VLAN 10.

Best answer: A

Explanation: The DHCP assignment shows that address allocation is working: the client received a valid 192.168.20.0/24 address from the router. The failure is the DHCP option for the default gateway. A host in 192.168.20.0/24 should use an address in that same subnet, here R1 Gi0/0.20 at 192.168.20.1. Because the pool advertises 192.168.10.1, the client installs an unreachable or incorrect gateway for off-subnet traffic. Updating the default-router option in the VLAN 20 pool fixes the assignment for new or renewed leases.

  • Relay not needed fails because the client already received a DHCP lease from 192.168.20.1.
  • Wrong VLAN move fails because Fa0/10 is already in the intended VLAN 20.
  • Wrong scope change fails because the assigned 192.168.20.0/24 address matches VLAN 20; only the gateway option is wrong.

Question 10

Topic: Network Infrastructure and Connectivity

A user PC in VLAN 20 cannot ping its default gateway. Other VLAN 20 hosts work, and you must restore this PC without changing the VLAN or SVI design.

Current facts:

DeviceIPv4 addressMaskDefault gateway
PC192.168.20.130255.255.255.128192.168.20.1
SVI VLAN 20192.168.20.1255.255.255.128N/A

Which configuration decision is most appropriate?

Options:

  • A. Change the VLAN 20 SVI mask to 255.255.255.0.

  • B. Change the PC gateway to 192.168.20.129.

  • C. Change the PC address to 192.168.20.100/25.

  • D. Change only the PC mask to 255.255.255.0.

Best answer: C

Explanation: The mask 255.255.255.128 is /25, which splits 192.168.20.0/24 into two subnets: 192.168.20.0–127 and 192.168.20.128–255. The SVI default gateway 192.168.20.1 is in the first /25, but the PC address 192.168.20.130 is in the second /25. Because the PC and its default gateway are not in the same IPv4 subnet, the PC’s addressing is the most likely cause of the reachability failure. Keeping the SVI design unchanged means assigning the PC a valid host address from 192.168.20.0/25.

  • Gateway 192.168.20.129 fails because no gateway with that address is provided in the VLAN 20 facts.
  • Changing only the PC mask creates a mismatch with the SVI subnet and does not follow the stated design.
  • Changing the SVI mask affects the gateway scope even though the constraint says not to change the SVI design.

Continue with full practice

Use the Cisco CCNA 200-301 v2.0 Practice Test page for the full IT Mastery practice bank, mixed-topic practice, timed mock exams, explanations, and web/mobile app access.

Try Cisco CCNA 200-301 v2.0 on Web View Cisco CCNA 200-301 v2.0 Practice Test

Free review resource

Read the Cisco CCNA 200-301 v2.0 Cheat Sheet on Tech Exam Lexicon, then return to IT Mastery for timed practice.

Revised on Monday, May 25, 2026