Modern HTTP Knowledge Check 3
Modern HTTP Knowledge Check 3
animation
http
protocols
InlineKnowledgeCheck({
containerId: "kc-http-modern-3",
question: "A cellular IoT device wakes from deep sleep every 15 minutes to send a sensor reading. In the chapter's model, using HTTP/3 with 0-RTT resumption instead of HTTP/2, approximately what percentage reduction in connection-setup radio time is expected?",
options: [
{"text": "5-10% - minimal improvement from reduced handshakes", "feedback": "Incorrect — too low: dropping k from 2.5 to 1.0 cuts setup time by 60%."},
{"text": "About 60% — setup radio time drops from 24 s to 9.6 s per day", "feedback": "Correct. This is connection-setup energy; whole-device savings are smaller and depend on radio and sleep current."},
{"text": "80-90% - nearly eliminates connection overhead", "feedback": "Incorrect — 0-RTT still needs one RTT for the response, so it cannot remove all setup time."},
{"text": "No difference - both protocols require the same handshake", "feedback": "Incorrect. Eligible QUIC 0-RTT resumption can send early data without waiting for a fresh handshake, whereas the fresh TCP/TLS path waits for setup. Early data needs replay-safe use."}
],
correctIndex: 1,
explanation: "The model’s 24 s/day versus 9.6 s/day is a 60% reduction in connection-setup radio time relative to HTTP/2. No whole-device power percentage follows without measured payload, radio tail, sleep, and resumed-session behavior.",
difficulty: "advanced"
})