Which statement about asynchronous processes is true?

Asynchronous processes are designed to allow users to continue working without waiting for a task to complete. This means that when a user initiates an asynchronous process, such as sending a large dataset to a server or processing a batch of records, they do not have to pause their activities and can instead perform other actions within the application. The completion of the asynchronous process happens in the background, resulting in a more efficient user experience.

In contrast, options that mention blocking the user or returning data only at the end of the entire process do not accurately reflect the nature of asynchronous operations. Asynchronous processes are defined by their ability to operate independently of the immediate user interface interactions, making it possible for tasks to run simultaneously while the user engages with other elements of the application. Additionally, stating that asynchronous processes are only applicable to UI integrations is misleading, as these processes can be utilized in various integration contexts, not limited to just the user interface.