Differentiate between synchronous and asynchronous messaging in the EPD Pilot and an example use case for each.

• A. Synchronous uses only text; asynchronous uses binary.
• B. Synchronous requires a response for each request (e.g., command-and-control); asynchronous allows independent message bursts (e.g., telemetry streams).
• C. Synchronous is unreliable; asynchronous is guaranteed delivery.
• D. Synchronous requires no response.

Answer: (B)

Synchronous vs asynchronous messaging centers on how tightly the sender and receiver interact in time. In synchronous messaging, every request expects a direct, immediate response, so the system stays tightly coupled and you can coordinate actions that depend on the result. An example is command-and-control, where a central controller sends a command and waits for a confirmation or result before proceeding. In asynchronous messaging, the sender and receiver are decoupled in time—the producer can publish messages and move on, while the consumer processes them later or at its own pace. This fits high-volume data like telemetry streams, where you emit bursts of data without needing an immediate reply for each piece. The other options miss the core distinction: encoding format (text vs binary) isn’t what separates these patterns, one claim about reliability mixes delivery guarantees with timing, and saying synchronous requires no response contradicts how synchronous communication actually works.