What is a typical use case that illustrates the need for synchronous messaging?

• A. Telemetry streams that can burst independently.
• B. Command-and-control interactions where a response is required for each request.
• C. Broadcasting a beacon to all devices without response.
• D. Asynchronous logging with no immediate acknowledgment.

Answer: (B)

Synchronous messaging is a request-response pattern where the sender waits for the recipient to process the message and return a result before continuing. This is essential when you need immediate confirmation or data from the other side for every action, such as issuing a command and requiring success/failure, status, or output before moving on. In command-and-control interactions, you often must know the exact outcome of each command to coordinate the next steps reliably, handle errors, and maintain consistent state.

Other options illustrate asynchronous flows: telemetry streams may burst without waiting for a reply, broadcasting a beacon doesn’t require a response, and asynchronous logging proceeds without immediate acknowledgment. These are not about waiting for a response, which is what makes them unsuitable examples of synchronous messaging.