Practice
Solution
Step 1: Understand ARP request nature
ARP requests are broadcast to all devices on the local subnet because the sender does not know the MAC address of the target.Step 2: ARP reply is unicast
The target device responds with a unicast ARP reply containing its MAC address.Step 3: Why not unicast request?
Unicast ARP requests cannot be sent without knowing the MAC address, which is the problem ARP solves.Step 4: DHCP is unrelated
DHCP is for IP address assignment, not MAC resolution.Step 5: Routing table does not store MAC addresses
Routing tables map IP prefixes to next hops, not MAC addresses.Final Answer:
Option A -> Option AQuick Check:
ARP requests are broadcast; replies are unicast [OK]
- Assuming ARP requests are unicast
- Confusing DHCP with ARP
- Thinking routing tables store MAC addresses
Solution
Step 1: Understand lease expiration behavior
When a lease expires, the IP address is not immediately available; there is usually a grace period before reassignment to avoid conflicts.Step 2: Analyze other options
Options B, C, and D are correct statements about DHCP leasing behavior.Final Answer:
Option A -> Option AQuick Check:
Immediate reassignment after expiration is incorrect; DHCP uses timers to prevent conflicts.
- Assuming IPs are instantly reusable after lease expiry
- Confusing lease renewal with release
- Believing leases do not prevent conflicts
Solution
Step 1: Understand RTO purpose
RTO determines when the sender retransmits unacknowledged segments, ideally matching network delay.Step 2: Analyze fixed vs adaptive RTO
Fixed RTO cannot adapt to changing RTTs, causing retransmissions either too early (wasting bandwidth) or too late (increasing latency).Step 3: Evaluate options
Because fixed RTO values prevent the sender from using sequence numbers effectively is incorrect; sequence number usage is unaffected by RTO. Because fixed RTO values increase the TCP header size, reducing throughput is false; RTO does not affect header size. Because fixed RTO values cause the receiver to drop out-of-order packets more frequently is unrelated to RTO. Because a fixed RTO cannot adjust to varying network delays, leading to either premature retransmissions or long delays correctly identifies the main drawback.Final Answer:
Option D -> Option DQuick Check:
Adaptive RTO improves efficiency by matching network conditions.
- Believing fixed RTO affects TCP header size
- Confusing RTO with receiver packet handling
- Assuming RTO impacts sequence number usage
Solution
Step 1: Understand SSE connection model
SSE maintains a single persistent HTTP connection over which events are streamed.Step 2: Analyze resource usage
Because SSE uses one persistent connection, it avoids the overhead of repeatedly opening new connections.Step 3: Evaluate options
SSE requires a new HTTP connection for each event, increasing overhead compared to WebSockets is false; SSE uses a single persistent connection. SSE uses fewer server resources than WebSockets because it only supports unidirectional communication is true. SSE maintains a single persistent HTTP connection, reducing latency compared to HTTP Long Polling is true. SSE cannot be used over HTTPS, limiting its security compared to WebSockets is a common misconception and is false; SSE works over HTTPS.Final Answer:
Option B -> Option BQuick Check:
SSE works over HTTPS; it is not limited in security compared to WebSockets
- Assuming SSE opens a new HTTP request for every event
- Believing SSE is bidirectional like WebSocket
- Thinking SSE cannot be secured with HTTPS
Solution
Step 1: Understand header stacking impact
Stacking all headers into one large header increases packet overhead, reducing effective throughput.Step 2: Why other options are incorrect
Visibility of headers does not inherently improve security; encryption is separate. No impact on performance is false. Reduced latency is unlikely due to larger packet size.Step 3: How to address the issue
Optimizing header sizes and applying header compression reduces overhead and improves efficiency.Final Answer:
Option D -> Option DQuick Check:
Large headers increase overhead and reduce throughput [OK]
- Assuming large headers improve security automatically
- Ignoring performance impact of large headers
- Believing latency always decreases with header stacking
