Practice
Solution
Step 1: Identify the role of ARP
ARP (Address Resolution Protocol) is specifically designed to map IP addresses to MAC addresses within a local network segment.Step 2: Why not DNS?
DNS resolves domain names to IP addresses, not MAC addresses.Step 3: Why not DHCP?
DHCP assigns IP addresses dynamically but does not resolve MAC addresses.Step 4: Why not routing table?
Routing tables determine the next hop IP address but do not resolve MAC addresses.Final Answer:
Option B -> Option BQuick Check:
ARP is the protocol that resolves IP to MAC addresses on local networks [OK]
- Confusing DNS with ARP
- Thinking DHCP handles MAC resolution
Solution
Step 1: Understand reverse proxy role
Reverse proxy acts as an intermediary on the server side, receiving client requests first.Step 2: After receiving the request
The reverse proxy forwards the request to the backend server for processing.Step 3: Other options
Firewall inspection happens before the reverse proxy in the network path; proxy caching is client-side; client does not connect directly to backend when reverse proxy is used.Final Answer:
Option A -> Option AQuick Check:
Reverse proxy forwards request to backend server immediately after receiving it [OK]
- Assuming firewall acts after reverse proxy
- Confusing proxy caching with reverse proxy behavior
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: Understand the semantics of 2xx status codes
2xx codes mean the request succeeded and the resource is validly returned.Step 2: Analyze implications of sending 2xx for a missing resource
Sending 2xx with a placeholder hides the fact the resource is missing, misleading clients and search engines.Step 3: Analyze options
Because 2xx codes force the client to redirect to another URL. is incorrect because 2xx does not cause redirects.
Because 2xx codes cause the client to retry the request unnecessarily. is incorrect because 2xx does not cause retries.
Because 2xx codes trigger client-side caching that prevents future requests. is incorrect because caching depends on headers, not just status codes.
Because 2xx codes indicate success, which misleads clients and search engines about the resource's existence. correctly states that 2xx indicates success, which misleads clients and search engines about the resource's existence.Final Answer:
Option A -> Option AQuick Check:
2xx means success; misusing it hides errors and breaks client expectations.
- Thinking 2xx can be used to mask missing resources
- Believing 2xx causes retries or redirects
- Confusing caching behavior with status codes
Solution
Step 1: Understand subnet change impact
IP addresses are subnet-specific; moving to a new subnet requires obtaining a new IP address.Step 2: Analyze DHCP behavior
The client must initiate a new DORA sequence to get a valid IP from the new DHCP server.Step 3: Evaluate other options
Options B, C, and D are incorrect because the old IP lease is not valid on the new subnet and lease renewal is with the original server only.Final Answer:
Option B -> Option BQuick Check:
Subnet change triggers new DHCP discovery and IP assignment.
- Assuming IP leases are portable across subnets
- Believing lease renewal works with a different DHCP server
- Thinking client can keep old IP without releasing
