Practice
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: Identify the key requirement -- minimal delay with acceptable occasional loss
Live video streaming prioritizes speed over perfect reliability.Step 2: Analyze TCP characteristics
TCP guarantees delivery and order but introduces delay due to acknowledgments and retransmissions.Step 3: Analyze UDP characteristics
UDP is connectionless and does not wait for acknowledgments, enabling faster transmission at the cost of possible packet loss.Step 4: Evaluate options
UDP, because it provides faster transmission without waiting for acknowledgments correctly matches the scenario needs. TCP options prioritize reliability over speed. UDP does not establish a connection before sending data, so that option is incorrect.Final Answer:
Option C -> Option CQuick Check:
UDP is preferred for real-time applications where speed matters more than reliability.
- Assuming TCP is always better because it guarantees delivery
- Believing UDP establishes a connection like TCP
- Confusing congestion control with speed priority
Solution
Step 1: Verify additive increase meaning
Congestion window increases by a fixed increment per RTT, which is correct.Step 2: Confirm multiplicative decrease behavior
On loss detection, TCP halves the congestion window, consistent with multiplicative decrease.Step 3: Assess AIMD guarantees
AIMD does not guarantee zero packet loss; it aims to reduce loss by controlling sending rate.Step 4: Understand AIMD's balance goal
AIMD is designed to balance throughput and network stability, which is true.Final Answer:
Option A -> Option AQuick Check:
AIMD reduces but does not eliminate packet loss.
- Believing AIMD eliminates all packet loss
- Misunderstanding additive increase as exponential growth
- Confusing multiplicative decrease with complete stop
Solution
Step 1: Calculate hosts per subnet for candidate masks
/22 mask -> 32 - 22 = 10 host bits -> 2^10 = 1024 addresses - 2 = 1022 usable hostsStep 2: Check /24 mask
/24 -> 8 host bits -> 254 usable hosts, insufficient for 1000 hostsStep 3: Check /20 mask
/20 -> 12 host bits -> 4094 usable hosts, more than needed but wastes addressesStep 4: Check /30 mask
/30 -> 2 host bits -> 2 usable hosts, far too smallStep 5: Choose best fit
/22 provides just enough hosts with minimal waste, balancing efficiency and requirements.Final Answer:
Option A -> Option AQuick Check:
Subnet mask must provide ≥1000 hosts; /22 is minimal mask meeting this [OK]
- Choosing default masks without considering host requirements
- Picking too large subnets causing address waste
- Selecting very small subnets ignoring host count needs
Solution
Step 1: Identify layer responsibilities relevant to encryption and compression
Encryption and compression are data transformations related to how data is presented and formatted for applications, which fits the Application Layer's role in TCP/IP (combining OSI's Application, Presentation, and Session layers).Step 2: Why not other layers?
Transport Layer manages segmentation and reliability, not data formatting. Internet Layer handles routing, not data content. Network Interface Layer deals with physical transmission, not data processing.Final Answer:
Option D -> Option DQuick Check:
Application Layer is the correct place for encryption/compression to maintain compatibility [OK]
- Placing encryption at Transport Layer (confusing with TLS)
- Thinking Internet Layer handles data content
- Assuming Network Interface Layer manages data transformations
