Modern HTTP Knowledge Check 7
Modern HTTP Knowledge Check 7
animation
http
protocols
InlineKnowledgeCheck({
containerId: "kc-http-modern-7",
question: "A startup is building an agricultural IoT system with soil moisture sensors. The sensors have 16KB RAM, connect via LoRaWAN to a gateway (512KB RAM), which then communicates with their AWS cloud backend. Which protocol combination is MOST appropriate?",
options: [
{"text": "Sensors use HTTP/2 to gateway, gateway uses HTTP/3 to cloud", "feedback": "Incorrect — 16 KB RAM is too small for a TLS + HTTP/2 stack, and LoRaWAN frames are only ~11–242 bytes."},
{"text": "Sensors send compact LoRaWAN payloads to the application server; the gateway uses HTTP/2 to cloud (CoAP needs a SCHC/IP adaptation)", "feedback": "Correct. Native LoRaWAN carries application payloads, not ordinary UDP/CoAP packets. CoAP/UDP can be adapted with SCHC when both ends support the RFC 9011 profile. The gateway’s HTTP/2 choice is independent and must match the cloud endpoint."},
{"text": "All devices use HTTP/3 for consistency", "feedback": "Incorrect — QUIC needs ≥1200-byte packets and ~64 KB RAM; LoRaWAN frames are ~11–242 bytes."},
{"text": "Sensors use HTTP/1.1 to gateway, gateway uses HTTP/2 to cloud", "feedback": "Incorrect — HTTP/1.1 text headers alone (hundreds of bytes) exceed a LoRaWAN frame."}
],
correctIndex: 1,
explanation: "LoRaWAN normally carries compact application payloads. CoAP/UDP needs an explicit IP adaptation such as SCHC (RFC 9011) at both ends; it does not run natively over LoRaWAN. The gateway can translate that payload into HTTP/2 for the supported cloud API.",
difficulty: "intermediate"
})