Practice
Solution
Step 1: Understand tunneling
Tunneling encapsulates the entire IPv6 packet inside an IPv4 packet to traverse IPv4 infrastructure.Step 2: Analyze options
The IPv6 packet is encapsulated inside an IPv4 header, which is then routed over the IPv4 network correctly describes encapsulation with an IPv4 header. The IPv6 header is replaced by an IPv4 header, and the packet is routed as IPv4 incorrectly states header replacement, which loses IPv6 info. The IPv6 packet is fragmented into IPv4 packets and reassembled at the destination is incorrect; fragmentation does not convert protocols. The IPv6 packet is converted into an IPv4 packet using NAT64 before transmission describes NAT64, a different technique.Final Answer:
Option D -> Option DQuick Check:
Tunneling wraps IPv6 packets inside IPv4 headers for transport.
- Confusing tunneling with header replacement
- Mixing up NAT64 with tunneling
- Assuming fragmentation converts protocols
Solution
Step 1: Understand IP Hash purpose
IP Hash uses the client's IP address to consistently route requests to the same backend server, enabling session persistence (sticky sessions).Step 2: Why not Round Robin or Least Connections?
Round Robin distributes requests evenly without regard to client identity, so it does not guarantee session persistence. Least Connections balances based on current load but also does not ensure the same client hits the same server.Step 3: Match scenarios to algorithms
When you need to ensure session persistence by routing requests from the same client IP to the same server correctly identifies the scenario where IP Hash is preferred: session persistence. Options A and C describe scenarios better suited for Least Connections or Round Robin. When you want to distribute requests strictly in a cyclic order regardless of client identity describes Round Robin behavior.Final Answer:
Option A -> Option AQuick Check:
IP Hash -> session stickiness; Round Robin -> cyclic distribution; Least Connections -> load-aware balancing.
- Confusing Least Connections with session persistence
- Assuming Round Robin can maintain client affinity
- Believing IP Hash balances load evenly regardless of client IP distribution
Solution
Step 1: Understand port forwarding (DNAT)
Port forwarding rewrites destination IP and port of incoming packets to internal server's IP and port.Step 2: Trace reply path
The server replies to the router's internal IP, which rewrites the source IP back to its public IP before sending to the external client.Step 3: Analyze options
The router changes the destination IP and port to the internal server's IP and port, forwards the packet, and rewrites the source IP of the reply back to the router's public IP correctly describes both forward and reply translation. The router changes the destination IP and port to the internal server's IP and port, then forwards the packet; the server replies directly to the client is incorrect because the server cannot reply directly to the client without NAT rewriting. The router only changes the destination IP but leaves the port unchanged; the internal server receives the packet and replies to the router misses port translation. The router forwards the packet without any translation; the internal server replies directly to the external client ignores NAT translation entirely.Final Answer:
Option A -> Option AQuick Check:
Port forwarding requires bidirectional NAT translation [OK]
- Assuming server replies directly to external client
- Forgetting port translation in forwarding
- Ignoring reply path NAT rewriting
Solution
Step 1: Analyze communication direction requirements
WebSocket supports full-duplex communication, allowing simultaneous two-way data flow, unlike SSE and Long Polling which are unidirectional or half-duplex.Step 2: Consider latency and connection persistence
WebSocket maintains a persistent connection with low latency, ideal for frequent bidirectional exchanges.Step 3: Evaluate other options
When the client only needs to receive unidirectional real-time updates from the server with minimal overhead describes SSE, which is unidirectional from server to client. When the server needs to push occasional updates but the client cannot maintain persistent connections is inaccurate because SSE requires persistent connections. When the client wants to reduce server resource usage by opening a new HTTP request for each update describes naive Long Polling, which is resource-heavy.Final Answer:
Option A -> Option AQuick Check:
Full-duplex + low latency + frequent bidirectional data -> WebSocket
- Confusing SSE as bidirectional
- Assuming Long Polling is efficient for frequent updates
- Believing WebSocket is only for server-to-client updates
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
