Practice
Solution
Step 1: Understand DNS hierarchy
The DNS system is hierarchical: root servers are at the top, followed by TLD servers, then authoritative servers.Step 2: Role of root DNS servers
Root servers do not resolve domain names directly but direct queries to the correct TLD server based on the domain extension (e.g., .com, .org).Step 3: Why other options are incorrect
Local resolvers and recursive servers initiate queries but do not direct to TLD servers; authoritative servers provide final answers for domains.Final Answer:
Option B -> Option BQuick Check:
Root DNS servers direct queries to TLD servers -> correct
- Confusing recursive DNS servers with root servers
- Assuming local resolver directs to TLD servers
- Thinking authoritative servers handle query routing
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: Identify PDU names per OSI layer
Application Layer and Presentation Layer use 'Data', Transport Layer uses 'Segment', Network Layer uses 'Packet', Data Link Layer uses 'Frame', Physical Layer uses 'Bits'.Step 2: Follow encapsulation order
Data is segmented, then packets are created, frames are formed, and finally bits are transmitted.Final Answer:
Option C -> Option CQuick Check:
Correct encapsulation order matches OSI layering [OK]
- Confusing order of PDUs
- Mixing up Segment and Packet roles
- Reversing encapsulation direction
Solution
Step 1: Proxy server capabilities
Proxy servers act as intermediaries forwarding client requests but typically do not filter traffic at the IP/port level.Step 2: Firewall capabilities
Firewalls filter traffic based on IP addresses, ports, and protocols, providing network-level security.Step 3: Evaluate other options
Proxy servers can cache content (contradicts C), do not block all incoming traffic by default (contradicts D), but may introduce latency due to encryption overhead in some cases.Final Answer:
Option C -> Option CQuick Check:
Proxy servers may introduce latency due to encryption overhead, unlike firewalls [OK]
- Assuming proxies filter traffic like firewalls
- Confusing caching capabilities of proxies
Solution
Step 1: Understand HTTPS performance characteristics
Encryption adds overhead, but it is not always a fixed doubling of latency.Step 2: Analyze options
A: Correct that HTTP/2 requires TLS and can improve performance.
B: Correct understanding that handshake cost is amortized over session.
C: Correct that hardware and session resumption reduce CPU impact.
D: Incorrect misconception that HTTPS always doubles latency.Final Answer:
Option C -> Option CQuick Check:
HTTPS overhead is often overestimated; it depends on connection length and optimizations.
- Assuming HTTPS always causes large latency increase
- Ignoring session resumption benefits
- Believing HTTP/2 can be used without TLS
