Question
In Java, which comparison about ConcurrentSkipListMap is accurate?
- It provides sorted-map behavior that ConcurrentHashMap does not, though ordered operations cost more than plain hash lookup.
- There is no practical difference in behavior, performance, or API design when ConcurrentSkipListMap is involved.
- The oldest option related to ConcurrentSkipListMap is always the right production choice regardless of context.
- Differences around ConcurrentSkipListMap are mostly cosmetic, so correctness and maintainability do not change.
Hint
Focus on the behavior or tradeoff, not just the keyword.
Answer and rationale
Correct answer: A. It provides sorted-map behavior that ConcurrentHashMap does not, though ordered operations cost more than plain hash lookup.
It provides sorted-map behavior that ConcurrentHashMap does not, though ordered operations cost more than plain hash lookup. This is the comparison that usually separates memorization from understanding.
Track: Java