Question
Which statement about ExecutorService, Future, and CompletableFuture is the strongest interview answer?
- ExecutorService, Future, and CompletableFuture is mostly a naming style choice and has little effect on runtime or design.
- ExecutorService, Future, and CompletableFuture exists mainly to reduce the number of Java files in a project.
- ExecutorService, Future, and CompletableFuture matters only for frontend frameworks, not for core Java applications.
- ExecutorService manages worker threads, Future represents pending results, and CompletableFuture composes asynchronous stages.
Hint
Start with the core rule behind ExecutorService, Future, and CompletableFuture.
Answer and rationale
Correct answer: D. ExecutorService manages worker threads, Future represents pending results, and CompletableFuture composes asynchronous stages.
ExecutorService manages worker threads, Future represents pending results, and CompletableFuture composes asynchronous stages. This is the base concept interviewers commonly test first.
Track: Java