Challenge - 5 Problems
CoAP Request-Response Master
Get all challenges correct to earn this badge!
Test your skills under time pressure!
🧠 Conceptual
intermediateCoAP Message Types Purpose
Which CoAP message type is used to confirm that a message was received successfully?
Attempts:
2 left
💡 Hint
Think about which message type acts as a reply to confirm receipt.
✗ Incorrect
The Acknowledgement (ACK) message is sent to confirm that a Confirmable (CON) message was received successfully.
💻 Command Output
intermediateCoAP Client Request Output
What is the expected output when a CoAP client sends a Confirmable GET request to a server and receives a successful response?
IOT Protocols
coap-client -m get coap://example.com/resource
Attempts:
2 left
💡 Hint
Look for the success response code for GET requests in CoAP.
✗ Incorrect
A successful GET request returns a 2.05 Content response code with the payload.
🔀 Workflow
advancedCoAP Request-Response Sequence
Arrange the steps in the correct order for a CoAP Confirmable GET request and response exchange.
Attempts:
2 left
💡 Hint
Think about the natural flow of request, processing, response, and receipt.
✗ Incorrect
The client first sends the CON request, the server processes it, then sends an ACK with the response, and finally the client receives and processes the ACK.
❓ Troubleshoot
advancedCoAP Timeout Cause
A CoAP client sends a Confirmable request but never receives an Acknowledgement. What is the most likely cause?
Attempts:
2 left
💡 Hint
Consider what happens if the server never replies to a Confirmable message.
✗ Incorrect
If the server does not receive the request or is down, the client will not get an ACK and will timeout.
✅ Best Practice
expertChoosing CoAP Message Type for Sensor Data
For a battery-powered sensor sending frequent temperature updates where reliability is not critical, which CoAP message type is best to minimize power and network usage?
Attempts:
2 left
💡 Hint
Think about saving power and network traffic when reliability is less important.
✗ Incorrect
Non-confirmable (NON) messages do not require ACKs, reducing power and network use, suitable for frequent sensor updates where some loss is acceptable.
