200-301 Practice Questions

The verified answer is the displayed drag-and-drop mapping. QoS congestion management controls how packets are queued and scheduled when an interface is congested. Terms such as FIFO, priority queuing, weighted fair queuing, class-based WFQ, and low-latency queuing describe different ways to decide which packets leave first. Cisco CCNA 200-301 v1.1 places this skill in IP Services, where the exam expects a working understanding of how the feature behaves on real Cisco networks, not just a memorized command. Congestion avoidance, classification, and marking are related QoS functions, but they are not the same as queue scheduling during congestion. In production, this distinction matters because a misapplied command or design choice usually creates an outage, a security gap, or unnecessary troubleshooting noise. The correct choice matches the control-plane, data-plane, wireless, security, or services behaviour described in the scenario and should be preferred over options that merely sound related.

A password manager reduces password risk in two practical ways. First, it helps users create and store strong, unique passwords instead of reusing simple passwords across services. Reuse is deadly: when one site is compromised, attackers try the same credentials elsewhere. Second, many password managers reduce exposure to phishing or keylogging because they can autofill only on matching legitimate sites and avoid repeated manual typing. They do not automatically supply a second authentication factor by themselves, and they are not a substitute for endpoint protection. The claim about an internal firewall protecting the repository is not the standard security benefit being tested. Cisco CCNA 200-301 v1.1 includes user-awareness and basic security practices because weak credentials remain a common entry point into networks. A password manager is not magic; its value is disciplined credential generation, storage, and safer use. The two valid choices are that it protects against keystroke logging risks in practical use cases and encourages stronger passwords.

A Layer 2 switch forwards frames within a VLAN and makes forwarding decisions based on MAC addresses. It learns source MAC addresses from ingress frames, records the associated port in the MAC address table, and forwards known destination frames out the matching port. If the destination is unknown, it floods within the VLAN. A Layer 2 switch does not select the best WAN route between networks; that is a router or Layer 3 switch function. It also does not normally move packets between different VLANs unless Layer 3 routing is involved. The existing answer that included a central point for association and authentication servers is not a Layer 2 switch function; that wording better resembles wireless or authentication infrastructure. Cisco CCNA 200-301 v1.1 Network Access expects a clean separation of switching and routing duties. The two valid Layer 2 switch functions are moving frames within a VLAN and forwarding based on MAC address.

The design goal is to add coverage cells without creating unnecessary contention. Adjacent Wi-Fi cells should use nonoverlapping channels so clients in neighboring coverage areas do not compete on the same RF channel. In the 2.4-GHz band, that usually means channels 1, 6, and 11 in many regulatory domains. The 5-GHz band provides far more channel capacity than 2.4 GHz and is preferred where client capability and design requirements support it. The source answer that selected same-channel adjacent APs is wrong: placing neighboring APs on the same channel increases co-channel contention, not throughput. A repeater AP is not the standard answer for overlapping channel design, and autonomous AP mode is not required simply to select 5-GHz channels. Cisco CCNA 200-301 v1.1 wireless fundamentals expects candidates to understand channel planning, cell overlap, and RF capacity. The correct recommendations are to use the larger 5-GHz channel set where appropriate and configure overlapping cells on nonoverlapping channels.

This drag-and-drop item is a subnetting exercise. For each IPv4 network, first identify the block size from the subnet mask, then calculate the network address, first usable host, last usable host, and broadcast address. Cisco CCNA 200-301 v1.1 expects candidates to work these ranges without relying on a calculator because routing, VLAN addressing, DHCP pools, and ACL wildcard logic all depend on the same arithmetic. A usable host range never includes the subnet ID or the broadcast address. For example, a /29 has eight total addresses and six usable hosts, while a /30 has four total addresses and two usable hosts. The correct matching is the one where each subnet is paired with only the valid host addresses inside that exact block. If an address falls on the boundary of the subnet or at the final broadcast value, it is not assignable to an interface. The reliable method is binary block sizing, not visual similarity between numbers.

A frame that fails the Ethernet Frame Check Sequence is counted as a CRC error and also contributes to input errors. The FCS field is the Ethernet trailer’s error-detection value; the receiver recalculates the value and compares it with the frame’s received FCS. If the values do not match, the frame is considered corrupted and is discarded. Cisco interface counters commonly report that condition under CRC, while the broader input errors counter includes CRC and other receive-side problems such as runts, giants, frame errors, overrun, ignored, and no-buffer conditions. Runts and giants are size-related counters, not the direct result of the FCS failure described in the question. The frame counter is not the best paired answer here. In CCNA 200-301 v1.1 Network Fundamentals, this maps to Ethernet operation and interface troubleshooting. The verified answers are D and E: CRC and input errors. Reference: Cisco interface counter interpretation and Ethernet FCS behavior.