What characterizes synchronous tasks?

What characterizes synchronous tasks?

• A. They execute concurrently.
• B. They run on separate threads.
• C. They happen one after the other, blocking until completion.
• D. They are always asynchronous.

Answer: (C)

Synchronous tasks are defined by blocking the caller’s thread until each task finishes, so they happen one after the other. When you invoke a synchronous operation, execution waits for that operation to complete before moving on to the next step, preventing overlap between tasks. This is different from asynchronous patterns, where work can be scheduled to run in the background and the program continues, handling results later. It’s also not mandatory that synchronous tasks run on separate threads—the key is the blocking behavior from the caller’s perspective, not the threading model. Likewise, they are not inherently concurrent or always asynchronous; the defining trait is that each task completes before the next begins.

Synchronous tasks are defined by blocking the caller’s thread until each task finishes, so they happen one after the other. When you invoke a synchronous operation, execution waits for that operation to complete before moving on to the next step, preventing overlap between tasks.

This is different from asynchronous patterns, where work can be scheduled to run in the background and the program continues, handling results later. It’s also not mandatory that synchronous tasks run on separate threads—the key is the blocking behavior from the caller’s perspective, not the threading model. Likewise, they are not inherently concurrent or always asynchronous; the defining trait is that each task completes before the next begins.