Asynchronous tasks are best described as:

Asynchronous tasks are best described as:

• A. Tasks that must run in a strict sequence.
• B. Tasks that are executed in a single thread.
• C. Tasks that can run concurrently.
• D. Tasks that only run after all other tasks finish.

Answer: (C)

Asynchronous tasks are about non-blocking work that can progress without waiting for other tasks to finish. The key idea is that a task can start, then wait for something like a file read or a network response while the system uses that waiting time to run other tasks. This overlap of progress is what we call concurrency. It doesn’t require a strict sequence, nor does it force everything to run on a single thread or only after everything else is done. You can have asynchronous code using a single-threaded event loop or a multi-threaded setup, but the common thread is that tasks don’t block the program while waiting for I/O, allowing multiple tasks to advance at the same time.

Asynchronous tasks are about non-blocking work that can progress without waiting for other tasks to finish. The key idea is that a task can start, then wait for something like a file read or a network response while the system uses that waiting time to run other tasks. This overlap of progress is what we call concurrency. It doesn’t require a strict sequence, nor does it force everything to run on a single thread or only after everything else is done. You can have asynchronous code using a single-threaded event loop or a multi-threaded setup, but the common thread is that tasks don’t block the program while waiting for I/O, allowing multiple tasks to advance at the same time.