Question
When should a Java developer choose Thread Lifecycle and Creation deliberately?
- Use executors instead of creating raw threads manually for most server-side or scalable application work.
- Choose Thread Lifecycle and Creation mainly when you want to postpone validation and fix problems manually later.
- Choose Thread Lifecycle and Creation whenever you want the code to look more advanced, even if the design gets less clear.
- Choose Thread Lifecycle and Creation only to avoid modeling domain rules explicitly in Java code.
Hint
Think about the production scenario where the choice genuinely improves the code.
Answer and rationale
Correct answer: A. Use executors instead of creating raw threads manually for most server-side or scalable application work.
Use executors instead of creating raw threads manually for most server-side or scalable application work. Interviewers often ask this to see whether you can connect the concept to real design decisions.
Track: Java