What does non-blocking mean?

• A. The thread is blocked until the response arrives.
• B. The response is cached locally to avoid waiting.
• C. The request bypasses the thread pool entirely.
• D. The thread is released back to the thread pool until receiving an answer.

Answer: (D)

Non-blocking means a thread isn’t held up while waiting for a response. Instead, the operation runs in the background and the thread is released back to the thread pool to do other work. When the result arrives, the system notifies you (via a callback, future, or similar mechanism) so you can handle it without ever having the thread sit idle waiting. This is exactly why the correct description is that the thread is released back to the thread pool until receiving an answer. The other options describe blocking behavior, caching, or bypassing the thread pool, none of which capture the non-blocking, asynchronous pattern.