In MDC3, which statement best distinguishes synchronous and asynchronous communication?

• A. Synchronous relies on decoupled messaging; asynchronous waits for a response.
• B. Synchronous uses immediate blocking calls; asynchronous uses queues.
• C. There is no difference between the two.
• D. Synchronous waits for a response; asynchronous uses decoupled messaging (queues/buses); MDC3 uses both as appropriate.

Answer: (D)

Distinguishing synchronous and asynchronous communication comes down to blocking and how tightly the components are coupled in time. In synchronous communication, the caller blocks and waits for the response from the callee, so the flow cannot proceed until that reply arrives. In asynchronous communication, the sender dispatches a message into a decoupled channel (like a queue or bus) and continues without waiting, leaving the processing to occur later and often decoupling producer and consumer in time.

In MDC3, you recognize that both patterns have their place: use synchronous when you need an immediate result and tight coordination, and use asynchronous with decoupled messaging when you want resilience, throughput, and loose coupling. Therefore, the statement that best distinguishes the two is that synchronous waits for a response, while asynchronous uses decoupled messaging, and MDC3 uses both approaches as appropriate.