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 SNAT purpose
SNAT modifies the source IP of outgoing packets, typically to allow multiple internal hosts to share a public IP for internet access.Step 2: Analyze options
When internal hosts initiate outbound connections to the internet, hiding their private IPs behind a public IP correctly describes SNAT's role in outbound connections. When external users need to access a specific internal server via a public IP and port describes DNAT or port forwarding. When translating destination IP addresses for incoming packets to reach internal hosts is DNAT's function. When mapping multiple public IPs to a single internal IP without port translation is not typical SNAT behavior.Final Answer:
Option A -> Option AQuick Check:
SNAT = source IP translation for outbound traffic [OK]
- Confusing SNAT with DNAT
- Assuming SNAT handles inbound connections
- Believing SNAT can map multiple public IPs to one internal IP without ports
Solution
Step 1: Understand reverse proxy caching
Reverse proxies may cache some content but do not always cache all content; caching is selective based on configuration.Step 2: Other statements
Reverse proxies hide backend details (A), perform SSL termination (C), and load balance requests (D) -- all correct.Final Answer:
Option A -> Option AQuick Check:
Reverse proxies do not always cache all content [OK]
- Assuming reverse proxies cache everything
- Confusing reverse proxy with CDN caching behavior
Solution
Step 1: Understand resource usage
Link State routing stores the entire network topology, requiring more memory and CPU for Dijkstra's algorithm.Step 2: Analyze scalability and convergence
Link State converges faster and avoids routing loops better, making it more scalable despite higher resource use.Step 3: Evaluate options
Distance Vector routing scales better in large networks because it floods link state advertisements less frequently is false because Distance Vector does not flood link state advertisements at all. Distance Vector routing has lower convergence time but higher memory usage compared to Link State is false because Distance Vector generally has slower convergence and lower memory usage. Link State routing uses less bandwidth overall because it only sends updates when topology changes is misleading; Link State floods updates on topology changes, which can be bandwidth intensive.Final Answer:
Option C -> Option CQuick Check:
Link State trades higher resource use for better scalability and convergence.
- Assuming Distance Vector floods updates like Link State
- Confusing convergence time and memory usage
- Believing Link State sends fewer updates overall
Solution
Step 1: Review TCP termination steps
Termination involves a four-step exchange: FIN from initiator, ACK from receiver, FIN from receiver, ACK from initiator.Step 2: Analyze each statement
Connection termination requires four steps involving FIN and ACK packets from both sides is correct describing the four-step process. Either side can initiate termination by sending a FIN packet is correct; either side can initiate. After termination, both sides enter a TIME_WAIT state to ensure all packets are received is correct; TIME_WAIT ensures delayed packets are handled. The connection closes immediately after the first FIN packet is sent is incorrect because connection does not close immediately after first FIN; it requires the full handshake.Final Answer:
Option A -> Option AQuick Check:
Termination is a multi-step process, not instantaneous.
- Assuming connection closes right after first FIN
- Thinking only server can initiate termination
- Ignoring TIME_WAIT state
