Free Implementing and Administering Cisco Solutions (200-301 CCNA) v1.1 Practice Questions

DNS lets applications use names instead of forcing users and software to work directly with IP addresses. A client can ask for the address associated with a hostname, and DNS returns the resource records needed to reach that service. DNS can also map one name to multiple IP addresses, which supports simple distribution, redundancy, or service design depending on the record type and client behavior. It does not encrypt WAN traffic by default, and it does not secure IP addresses merely by hiding them behind fully qualified domain names. DNS is hierarchical, not flat, which is why the root, top-level domains, authoritative zones, and host records can scale globally. Cisco CCNA 200-301 v1.1 covers DNS under IP Services because name resolution is required for many network operations, including management access, web services, and application connectivity. The two valid roles here are enabling applications to identify resources by name and allowing a hostname to be associated with more than one IP address.

Answer the displayed drag-and-drop mapping is the technically correct selection. DHCP snooping builds a trusted binding table from legitimate DHCP exchanges. Trusted ports face valid DHCP servers, untrusted ports face clients, and the binding database becomes the source of truth for features such as Dynamic ARP Inspection and IP Source Guard. This aligns with Cisco CCNA 200-301 v1.1 because the exam blueprint requires engineers to recognize operational behaviour from configuration symptoms and topology requirements. Ordinary MAC learning does not validate DHCP messages, and trunking or STP alone cannot prevent a rogue DHCP server from handing out false gateways. Treat the distractors carefully: most are real Cisco terms, but they solve a different problem or operate at a different layer. The selected answer is the one that would be used by an engineer on the device or in the design to produce the outcome stated in the question.

Weighted Random Early Detection is a congestion-avoidance mechanism. It starts dropping selected packets before an output queue becomes completely full, which helps avoid tail drop and TCP global synchronization. WRED can weight the drop behavior by IP precedence or DSCP so lower-priority traffic is more likely to be dropped before higher-priority traffic. That makes options A and D correct. WRED does not guarantee delivery of high-priority packets; it only changes drop probabilities. It also does not perform deep flow identification with high granularity, and it is not a protocol-discovery feature. In QoS design, classification and marking identify traffic, congestion management schedules traffic, and congestion avoidance drops early to prevent queue collapse. CCNA 200-301 v1.1 IP Services includes QoS behavior at a conceptual level, and WRED is best remembered as selective early drop based on traffic marking. Reference: Cisco QoS congestion avoidance and WRED behavior.

The verified answer is A and

D.  

This drag-and-drop question tests whether the protocol normally uses TCP or UDP as its transport service. TCP is selected when the application requires connection setup, acknowledgments, sequencing, and retransmission. Protocols such as HTTP, HTTPS, FTP, SSH, Telnet, and SMTP commonly rely on TCP because reliable delivery matters more than minimal overhead. UDP is selected when the application benefits from low overhead, simple request/response behavior, or real-time delivery where late retransmission is not useful. DNS queries, DHCP, TFTP, SNMP polling, NTP, voice media, and many streaming functions commonly use UDP. Some protocols can use both in special cases, but CCNA questions normally expect the standard default transport. Cisco CCNA v1.1 Network Fundamentals includes application protocols and transport-layer behavior. The correct mapping should therefore follow function: reliable session-based applications go to TCP, while lightweight discovery, timing, addressing, and real-time-style exchanges usually go to UDP.

DHCP dynamically leases IP configuration to clients, and the server can exclude specific addresses from the assignable pool. Exclusions are important because some addresses in the subnet may be reserved for routers, servers, printers, infrastructure interfaces, or static assignments. DHCP leasing means the client receives an address for a defined lease time and must renew it before expiration. Cisco CCNA 200-301 v1.1 IP Services includes DHCP because engineers must understand address pools, default-router options, DNS options, exclusions, and relay behavior. The server, not the client, maintains the pool of assignable addresses. DHCP does not assign addresses forever without renewal. A client can receive DNS server information, but the statement that it can request up to four DNS servers is not the core tested role here. The two correct operational roles are that the DHCP server can exclude addresses from a pool and lease client IP addresses dynamically. Those are A and

D.