Practice
Solution
Step 1: Understand lease expiration behavior
When a lease expires, the IP address is not immediately available; there is usually a grace period before reassignment to avoid conflicts.Step 2: Analyze other options
Options B, C, and D are correct statements about DHCP leasing behavior.Final Answer:
Option A -> Option AQuick Check:
Immediate reassignment after expiration is incorrect; DHCP uses timers to prevent conflicts.
- Assuming IPs are instantly reusable after lease expiry
- Confusing lease renewal with release
- Believing leases do not prevent conflicts
Solution
Step 1: Recall idempotency definition
An idempotent method produces the same result no matter how many times it is repeated.Step 2: Analyze POST properties
POST is not idempotent; repeated identical POSTs can create multiple resources or side effects.Step 3: Evaluate options
Because POST is not idempotent, repeated identical requests may cause unintended side effects correctly identifies the non-idempotent nature of POST. Others are factually incorrect.Final Answer:
Option D -> Option DQuick Check:
POST is not idempotent, so using it for idempotent operations risks unintended consequences.
- Thinking POST is cached by default (it is not)
- Believing POST cannot carry a body (it can)
- Assuming POST deletes resources before updating
Solution
Step 1: Understand advanced ARP spoofing mitigation
Dynamic ARP Inspection (DAI) is a security feature on switches that intercepts ARP packets and verifies them against a trusted binding database.Step 2: Why not disabling ARP?
ARP is essential for IP-to-MAC resolution; disabling it breaks local communication.Step 3: DHCP snooping is complementary but not sufficient
DHCP snooping helps build trusted bindings but does not directly inspect ARP packets.Step 4: Increasing ARP cache timeout worsens spoofing risk
Longer cache times mean stale or poisoned entries persist longer.Final Answer:
Option A -> Option AQuick Check:
DAI validates ARP packets to prevent spoofing effectively [OK]
- Thinking ARP can be disabled safely
- Confusing DHCP snooping with ARP inspection
- Believing longer ARP cache timeout improves security
Solution
Step 1: Analyze the scenario
Large receiver window means flow control is not limiting sender; packet loss indicates network congestion.Step 2: Identify correct sender adjustment
Sender should reduce congestion window per AIMD to reduce congestion and improve throughput.Step 3: Reject decreasing receiver window
Sender cannot control receiver's advertised window; it's a receiver-side parameter.Step 4: Reject ignoring congestion or increasing timeout
Ignoring congestion worsens loss; increasing timeout delays recovery, not throughput improvement.Final Answer:
Option D -> Option DQuick Check:
Congestion control adjusts sending rate; flow control limits receiver buffer usage.
- Confusing flow control with congestion control adjustments
- Thinking sender can reduce receiver window
- Believing retransmission timeout tuning solves congestion
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
