Practice
Solution
Step 1: Understand the role of TCP sequence numbers in packet ordering
TCP sequence numbers uniquely identify bytes in the data stream, allowing the receiver to reorder packets that arrive out of order.Step 2: Analyze each option
When the receiver needs to reorder out-of-sequence packets before delivering data to the application is correct because reordering depends on sequence numbers. When the sender wants to detect duplicate acknowledgments to trigger fast retransmission relates to ACKs, not sequence numbers directly. When the receiver uses it to calculate the retransmission timeout (RTO) is incorrect because RTO calculation uses RTT estimates, not sequence numbers. When the sender uses it to encrypt the data payload for security is unrelated to sequence numbers.Final Answer:
Option A -> Option AQuick Check:
Sequence numbers enable ordering, not encryption or RTO calculation.
- Confusing sequence numbers with ACK numbers
- Thinking sequence numbers affect RTO calculation
- Assuming sequence numbers relate to encryption
Solution
Step 1: Identify the key requirement -- minimal delay with acceptable occasional loss
Live video streaming prioritizes speed over perfect reliability.Step 2: Analyze TCP characteristics
TCP guarantees delivery and order but introduces delay due to acknowledgments and retransmissions.Step 3: Analyze UDP characteristics
UDP is connectionless and does not wait for acknowledgments, enabling faster transmission at the cost of possible packet loss.Step 4: Evaluate options
UDP, because it provides faster transmission without waiting for acknowledgments correctly matches the scenario needs. TCP options prioritize reliability over speed. UDP does not establish a connection before sending data, so that option is incorrect.Final Answer:
Option C -> Option CQuick Check:
UDP is preferred for real-time applications where speed matters more than reliability.
- Assuming TCP is always better because it guarantees delivery
- Believing UDP establishes a connection like TCP
- Confusing congestion control with speed priority
Solution
Step 1: Understand DHCP overhead
Each new client connection triggers the DORA sequence, which adds network traffic.Step 2: Analyze impact of high churn
Frequent IP requests can overload the DHCP server and increase broadcast traffic, causing congestion.Step 3: Evaluate other options
Because DHCP cannot assign IP addresses dynamically in such environments is false; DHCP is designed for dynamic assignment. Because DHCP servers do not support IP address leasing is incorrect; DHCP supports leasing. Because clients must manually configure IP addresses in such cases is unrelated to DHCP limitations.Final Answer:
Option A -> Option AQuick Check:
High churn leads to excessive DHCP message overhead.
- Believing DHCP cannot assign dynamically in such cases
- Confusing DHCP leasing with static assignment
- Assuming manual configuration is required when DHCP is unsuitable
Solution
Step 1: Recall IPv6 header structure
IPv6 headers have fixed length and no checksum field.Step 2: Analyze options
IPv6 headers have a fixed length of 40 bytes, simplifying processing is correct; IPv6 headers are fixed at 40 bytes. IPv6 headers include a checksum field to ensure header integrity is incorrect; IPv6 does not have a checksum field. IPv6 removes the header checksum present in IPv4 to reduce processing overhead is correct; checksum was removed to speed up processing. IPv6 headers support extension headers to add optional information is correct; extension headers provide optional info.Final Answer:
Option B -> Option BQuick Check:
IPv6 relies on upper-layer checksums, not header checksum.
- Assuming IPv6 headers have checksums like IPv4
- Confusing extension headers with fixed header fields
Solution
Step 1: Identify handshake latency cause
The handshake requires at least one full round-trip time (RTT) before data can be sent, introducing delay.Step 2: Analyze options
Because it requires multiple round-trip times before data transfer, causing delay in time-sensitive applications correctly states the latency due to multiple RTTs, which can be problematic for real-time or low-latency applications. Because it encrypts all packets during handshake, increasing processing time is incorrect; encryption is separate from handshake. Because it uses UDP packets which are slower than TCP packets is false; handshake uses TCP packets, not UDP. Because it requires the server to send data before the client can send any is incorrect; the client sends data after handshake completes.Final Answer:
Option A -> Option AQuick Check:
Handshake latency = multiple RTTs before data flow.
- Confusing handshake with encryption overhead
- Thinking handshake uses UDP packets
- Believing server sends data first
