Question
When should a Java developer choose ConcurrentLinkedQueue deliberately?
- Choose ConcurrentLinkedQueue mainly when you want to postpone validation and fix problems manually later.
- Choose ConcurrentLinkedQueue whenever you want the code to look more advanced, even if the design gets less clear.
- Use ConcurrentLinkedQueue for lightweight concurrent handoff when unbounded non-blocking FIFO behavior is acceptable.
- Choose ConcurrentLinkedQueue 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: C. Use ConcurrentLinkedQueue for lightweight concurrent handoff when unbounded non-blocking FIFO behavior is acceptable.
Use ConcurrentLinkedQueue for lightweight concurrent handoff when unbounded non-blocking FIFO behavior is acceptable. Interviewers often ask this to see whether you can connect the concept to real design decisions.
Track: Java