Practice
Solution
Step 1: Understand the role of DHCP Discover message
The Discover message is the initial broadcast sent by a client to locate available DHCP servers and request an IP address.Step 2: Analyze other options
When a client wants to renew an existing IP lease describes lease renewal, which uses the Request message, not Discover. When a client releases its IP address back to the server refers to releasing an IP, unrelated to Discover. When a DHCP server confirms the IP address assignment is about the server confirming the IP assignment, which is the Acknowledgment message.Final Answer:
Option D -> Option DQuick Check:
Discover is always the first message sent by a client seeking an IP address.
- Confusing Discover with Request or Acknowledgment messages
- Assuming Discover is used for lease renewal
- Thinking Discover is sent by the server
Solution
Step 1: Identify the role of each component
Firewalls are designed to filter network traffic based on IP addresses, ports, and protocols, enforcing security policies.Step 2: Understand Proxy and Reverse Proxy roles
Proxies forward client requests but do not primarily filter traffic at the network level; reverse proxies handle server-side requests and optimize load.Step 3: CDN role
CDNs cache content to improve performance but do not filter traffic for security.Final Answer:
Option B -> Option BQuick Check:
Firewall is the component that filters traffic based on rules [OK]
- Confusing proxy with firewall as a security filter
- Assuming reverse proxy filters traffic like a firewall
Solution
Step 1: Understand TCP reliability mechanism
TCP uses acknowledgments (ACKs) to confirm receipt of packets.Step 2: Lost packet detection
If a packet is lost, the sender does not receive an ACK for it within a timeout period.Step 3: Retransmission trigger
After timeout, the sender retransmits the lost packet.Step 4: Evaluate options
The receiver sends an acknowledgment for the last correctly received packet, triggering retransmission after timeout correctly describes the process. The sender immediately retransmits the lost packet without waiting for any signal is incorrect because retransmission waits for timeout or duplicate ACKs. The receiver sends a negative acknowledgment (NAK) to request retransmission of the lost packet is incorrect; TCP does not use NAKs. The sender continues sending new packets without retransmitting lost ones ignores retransmission, violating TCP reliability.Final Answer:
Option B -> Option BQuick Check:
TCP relies on ACK timeouts to detect loss and trigger retransmission.
- Believing TCP uses negative acknowledgments (NAKs)
- Thinking retransmission happens immediately without waiting
- Assuming sender ignores lost packets
Solution
Step 1: Understand sliding window's limitation
Sliding window controls flow based on receiver's buffer availability, not network congestion.Step 2: Differentiate from congestion control
Congestion control algorithms like AIMD adjust sending rate based on network feedback to avoid congestion.Step 3: Reject exponential increase and retransmission speed options
Sliding window does not inherently increase window exponentially; retransmission speed is unrelated to flow control.Step 4: Clarify explicit congestion notification role
Explicit congestion notification is optional and unrelated to sliding window's basic operation.Final Answer:
Option B -> Option BQuick Check:
Sliding window limits sender by receiver buffer, not network capacity.
- Assuming sliding window adapts to network congestion
- Confusing flow control with retransmission mechanisms
- Believing sliding window depends on router signals
Solution
Step 1: Understand TTL expiration
Once TTL expires, cached records are considered stale and should not be served without validation.Step 2: Behavior on authoritative server failure
The recursive resolver tries to refresh the record by querying the authoritative server.Step 3: Outcome if authoritative server is down
If unreachable, the resolver returns an error (e.g., SERVFAIL) to the client.Step 4: Why other options are incorrect
The recursive resolver will immediately return a SERVFAIL error to the client since the authoritative server is unreachable ignores retry attempt; The recursive resolver will return the expired cached record to the client to avoid resolution failure violates TTL rules by serving expired data; The recursive resolver will query the root server again to find an alternative authoritative server is incorrect because root servers do not provide alternative authoritative servers.Final Answer:
Option A -> Option AQuick Check:
Expired TTL triggers retry; failure returns error -> correct
- Assuming expired cache is always served
- Thinking root servers provide alternative authoritative servers
- Believing resolver returns error immediately without retry
