Cisco 200-301 Exam Dumps, Practice Test Questions

Congestion-window control protects the network against excessive traffic, whereas the receiving host advertises its own available buffer capacity using a separate receive window.

Selective acknowledgment improves identification of received and missing data after loss, but it does not convey how much outstanding data the receiver can buffer.

Retransmission recovers lost segments; by itself it does not limit the sender to the receive capacity explicitly advertised in ACKs.

UDP has no inherent reliable ordered byte stream and is not the conventional transport for the specified HTTP/1.1 or HTTP/2 session.

SCTP can provide reliable message transport but is not the standard transport of the HTTP/1.1 or HTTP/2 client-server connection stated.

QUIC typically carries HTTP/3 and uses UDP. The question explicitly excludes HTTP/3 and identifies the conventional HTTP/2 reliable byte-stream connection.

DNS supports TCP, but the question specifies a small normal stub query using UDP; TCP 53 is not mandatory for every initial ordinary lookup.

UDP 67 is the DHCPv4 server port, not the normal resolver destination for DNS queries.

UDP port 5353 is associated with multicast DNS; it is not the specified standard unicast recursive-resolver query on UDP 53.

TCP includes sequence and acknowledgment numbers and control flags in addition to its ports; the missing fields rule out the normal TCP header format.

ICMPv6 provides message type and code information, not the source/destination UDP port pair and UDP datagram-length field described.

SCTP uses source/destination ports with a verification tag and checksum, but not the four-field UDP header with the specified length field.

Connection establishment normally occurs at the beginning of the TCP session; retransmission of a lost segment does not require a fresh SYN handshake per byte.

The receive window provides flow control, not a declaration that missing data has arrived; the lost sequence range still needs recovery.

An established TCP connection does not silently become UDP, and UDP itself does not provide TCP sequence-based reliable retransmission.

The UDP header contains ports, length and checksum, not a built-in ordered sequence or TCP-style retransmission mechanism.

TCP SACK is a TCP connection feature and is not automatically generated for unrelated UDP datagrams.

The Ethernet FCS detects corrupted frames on a link; it does not track or reorder application UDP datagrams across an IP path.

The third /26 begins at .128, above the host address.

The first /26 ends at .63 and cannot contain .77.

A /27 beginning at .64 includes .77, but it uses a 27-bit prefix rather than the configured /26.

The .191 address broadcasts the next /27 block, not .128/27.

The .160 address starts the following /27 network.

The .158 address is the last ordinary usable host, not broadcast.

This is the first usable host address, not the last.

This is usable but is not the highest available host address.

This is the directed broadcast address for the /28.

This is the second usable host rather than the first.

A conventional /26 reserves its all-zero host address as the network identifier.

The final address in this /26 is its directed broadcast.

One of the two reserved conventional /27 addresses remains incorrectly counted.

That is the conventional usable-host count of a /26, not a /27.

This counts the network identifier and directed broadcast as assignable hosts.