Practice
Solution
Step 1: Understand PATCH semantics
PATCH is used for partial updates, modifying only specified fields.Step 2: Differentiate from PUT
PUT replaces the entire resource, while PATCH updates parts.Step 3: Analyze options
The server modifies only the specified email field without affecting other user data correctly states partial modification; others describe full replacement or resource creation/deletion.Final Answer:
Option A -> Option AQuick Check:
PATCH modifies only the targeted fields without affecting the rest.
- Confusing PATCH with PUT and thinking it replaces the whole resource
- Assuming PATCH creates new resources
- Believing PATCH deletes and reinserts fields
Solution
Step 1: Understand the network requirements for fast convergence
Large networks with frequent topology changes require routing algorithms that quickly adapt to changes to prevent downtime and routing loops.Step 2: Compare Distance Vector and Link State routing characteristics
Distance Vector routing uses periodic updates and can suffer from slow convergence and count-to-infinity problems. Link State routing floods link state advertisements immediately upon topology changes and recalculates routes using Dijkstra's algorithm, leading to faster convergence.Step 3: Analyze the options
Distance Vector routing because it requires less memory and simpler computations is incorrect because although Distance Vector requires less memory and simpler computations, it converges slower. Link State routing because it uses periodic full routing table exchanges is incorrect because Link State routing does not use periodic full routing table exchanges but floods link state changes immediately. Distance Vector routing because it avoids flooding the network with updates is incorrect because Distance Vector routing does not avoid flooding; it sends periodic updates to neighbors. Link State routing because it quickly propagates topology changes and converges faster is correct because Link State routing quickly propagates topology changes and converges faster.Final Answer:
Option D -> Option DQuick Check:
Link State routing is preferred in large, dynamic networks for fast convergence.
- Assuming Distance Vector is always simpler and better for large networks
- Confusing periodic updates with flooding
- Believing Link State exchanges full routing tables periodically
Solution
Step 1: Understand routing requirements
Routing decisions depend on logical addressing (IP addresses) handled at the Network Layer.Step 2: Role of Transport Layer
Transport Layer manages end-to-end communication using ports, not IP addresses, so it lacks necessary info for routing.Step 3: Why other options are incorrect
Transport Layer speed is not the main limitation; encryption is unrelated to routing; physical connections are handled by lower layers.Final Answer:
Option A -> Option AQuick Check:
Transport Layer lacks IP address info for routing [OK]
- Assuming Transport Layer handles routing because it manages connections
- Confusing encryption with routing
- Believing Transport Layer manages physical connections
Solution
Step 1: Recall idempotency of PUT
PUT is idempotent; repeated identical requests should produce the same result without error.Step 2: Analyze server behavior
Rejecting the second identical PUT with a conflict error violates idempotency.Step 3: Evaluate options
D correctly identifies the server's incorrect behavior and the proper design.
B is false because PUT is idempotent.
C is wrong because POST is not idempotent.
A is incorrect; deleting before PUT is unnecessary and may cause data loss.Final Answer:
Option B -> Option BQuick Check:
Idempotent methods like PUT must accept repeated identical requests gracefully.
- Thinking PUT is non-idempotent and should reject duplicates
- Believing POST is better for idempotent updates
- Assuming resource deletion is needed before PUT
Solution
Step 1: Understand RTO adaptation to RTT variance
TCP's RTO algorithm uses both RTT estimate and variance to adapt timeout dynamically.Step 2: Analyze handling of large RTT variations
Increasing variance estimate prevents premature retransmissions caused by transient delays, trading off some delay for stability.Step 3: Evaluate options
Increase the RTO variance estimate to avoid premature retransmissions, even if it delays recovery correctly describes the adaptive behavior. Ignore RTT variations and keep RTO fixed to prevent oscillations ignores adaptation, causing inefficiency. Reset the RTO to a minimal value after each retransmission to speed up recovery risks spurious retransmissions. Disable retransmissions temporarily until RTT stabilizes is impractical and breaks reliability.Final Answer:
Option A -> Option AQuick Check:
Adaptive RTO balances responsiveness and stability under RTT fluctuations.
- Fixing RTO despite RTT changes
- Resetting RTO too aggressively after retransmissions
- Disabling retransmissions during network instability
