When comparing CoAP and MQTT for power-constrained IoT devices, which specific architectural characteristic of CoAP makes it more suitable for integration with existing web infrastructures while operating over UDP?

It uses a RESTful request-response model that maps directly to HTTP methods.

It exclusively uses an 802.11be physical layer for long-range transmission.

It utilizes a mandatory broker to manage all resource discovery.

It requires a persistent TCP handshake to ensure packet delivery.

An analyst is inspecting packet captures from a constrained IoT environment. They observe a binary-encoded header with a 4-byte fixed size, utilizing UDP port 5683, and notice the message types 'Confirmable' and 'Non-confirmable'. Which protocol is being analyzed, and what is its primary design purpose?

CoAP; designed for low-overhead, RESTful interaction in constrained networks.

HTTP/2; designed for multiplexing multiple requests over a single TCP connection.

XMPP; designed for real-time presence and extensible XML messaging.

MQTT; designed for reliable message queuing via a central broker.

HTTP; because its text-based headers and stateless nature leading to frequent handshakes consume significant energy and bandwidth.

CoAP; because the binary header format is too complex for 8-bit microcontrollers to parse.

MQTT; because the persistent connection requires constant heartbeats that drain the battery.

UDP; because it lacks a flow control mechanism which leads to packet loss and retransmission cycles.

MQTT; it ensures the broker and client are still connected by requiring a PINGREQ/PINGRESP exchange if no other messages are sent.

HTTP/1.1; it maintains a persistent session to allow the server to push raw HTML data to the sensor.

CoAP; it provides a way to verify that the UDP port remains open through a three-way handshake.

REST; it defines the maximum time a resource can be cached by the client before being considered stale.

A Chunked Transfer Encoding in HTTP

A Quality of Service Level 2 Handshake in MQTT

MQTT; it allows new subscribers to receive a status update immediately without waiting for the next publishing interval.

REST; it ensures that the state of a resource is always synchronized using a stateless JSON payload.

CoAP; it enables the server to buffer UDP packets to prevent data loss during congestion.

HTTP; it allows the server to cache web pages on the client side using ETags.