What happens when a sub-process is configured to run asynchronously?

When a sub-process is configured to run asynchronously, it means that the parent process does not wait for the sub-process to complete before moving on to the next activities. Instead, the sub-process starts and allows the parent process to continue execution without any delay. This is particularly useful in scenarios where tasks can be handled independently and do not require immediate feedback from the sub-process. The asynchronous behavior allows for better utilization of resources and improves the overall efficiency of the process.

In this context, the other options describe different behaviors: waiting for completion implies a synchronous process, requiring user input indicates a need for acknowledgement that would also delay the parent process, and running in synchronous mode directly contradicts the nature of asynchronous execution. In summary, choosing to run a sub-process asynchronously frees the parent process to continue executing subsequent steps immediately after initiating the sub-process.